emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Ihor Radchenko <yantar92@gmail.com>, Bastien Guerry <bzg@gnu.org>,
	emacs-orgmode@gnu.org
Subject: Re: [BUG] worg-setup.org is outdated
Date: Tue, 03 Jan 2023 07:03:21 +1100	[thread overview]
Message-ID: <86pmbwd797.fsf@gmail.com> (raw)
In-Reply-To: <877cy5md6s.fsf@localhost>


Ihor Radchenko <yantar92@posteo.net> writes:

> Tim Cross <theophilusx@gmail.com> writes:
>
>> First step is to get a working local copy so that I have something to
>> work with. AFter that and a bit of exploring, I should have a better
>> understanding and idea how to go forward. 
>
> Hi Tim,
>
> May I know if you got a chance to continue working on this?
> Let us know if you need any help from us.

Hi Ihor,

sorry, no real progress.

I did get a working local copy and started looking into what needed to
be done to improve things. Unfortunately, the more I understood, the
more it became obvious that simple tweaking was unlikely to consistently
improve the situation. Each little improvement I made just caused or
exposed other issues and it quickly spiralled down.

Unfortunately, other commitments then took over and I've been too busy
to focus on org stuff for some months now. Even participation in the ML
has been challenging.

A significant re-design of the worg styling is required in order to get
a presentation which both looks good and which works with respect to
accessibility requirements. I don't believe the current styles are
workable. Someone with greater CSS fu than me might do better, but from
what I could tell, the basic underlying premise for the existing styles
is flawed. I suspect it would be possible to 'fix' things, but it would
be a major style re-working. 

I would still like to get back to this, but right now, don't know where
things are likely to be in the short term. There are some job related
things which will be eitehr completed or stepped up to the next stage by
mid Feb and I may have a clearer picture by then. For now though, I have
limited resources to dedicate to org. 


  reply	other threads:[~2023-01-02 20:15 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 21:51 [accessibility] worg obscures text Samuel Wales
2022-06-12 19:35 ` Rudolf Adamkovič
2022-06-13  0:22 ` Tim Cross
2022-06-13  0:34   ` Ihor Radchenko
2022-06-13  2:16     ` Tim Cross
2022-06-13  5:30       ` [BUG] worg-setup.org is outdated (was: [accessibility] worg obscures text) Ihor Radchenko
2022-06-13  5:44         ` Tim Cross
2022-06-13  6:14           ` Timothy
2022-06-13 14:21           ` [BUG] worg-setup.org is outdated Bastien Guerry
2022-06-13 14:21         ` Bastien Guerry
2022-06-13 22:32           ` Tim Cross
2022-06-14  0:57             ` Ihor Radchenko
2022-06-14  1:08               ` Tim Cross
2022-06-14  1:37                 ` Ihor Radchenko
2022-06-14  1:51                   ` Tim Cross
2022-06-14  2:18                     ` Ihor Radchenko
2022-06-14  2:46                       ` Tim Cross
2022-06-14  2:59                         ` Ihor Radchenko
2023-01-02 10:40                 ` Ihor Radchenko
2023-01-02 20:03                   ` Tim Cross [this message]
2023-01-03 11:01                     ` Ihor Radchenko
2023-01-04 10:21                     ` [TASK] Enhance Worg HTML styling (was: [BUG] worg-setup.org is outdated) Bastien Guerry
2023-01-04 10:50                       ` Alain.Cochard
2023-01-04 22:43                         ` Tim Cross
2023-01-05 14:07                           ` Alain.Cochard
2023-01-05 15:41                             ` Tim Cross
2023-01-05 20:18                               ` [TASK] Enhance Worg HTML styling Leo Butler
2023-01-06  1:23                                 ` Tim Cross
2022-06-13  5:37       ` [accessibility] worg obscures text Max Nikulin
2022-06-16  3:22 ` Tim Cross
2022-06-16 23:30   ` Samuel Wales

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86pmbwd797.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \
    --cc=yantar92@posteo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).