From: Ihor Radchenko <yantar92@posteo.net>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to organize tasks about Worg within Worg documents
Date: Mon, 01 Apr 2024 11:34:27 +0000 [thread overview]
Message-ID: <87cyr98gfw.fsf@localhost> (raw)
In-Reply-To: <ce5ad24f-43cf-458e-868c-eaa808dc7a4a@alphapapa.net>
Adam Porter <adam@alphapapa.net> writes:
>> May we have some kind of css-based toggle that will enable "developer
>> mode", revealing all the todo keywords, inlinetasks, and notes? Then, we
>> hide the "unfinished" parts from users by default, but let them see what
>> can be contributed?
>
> I like the idea of a visual toggle very much, so I'm certainly in favor
> of that.
>
> I'm not sure that we must have a constraint on the way TODOs are
> written, but having some limitations on or conventions about it might
> make such a visual toggle easier to implement (as well as other tools
> one might use to collect and visualize tasks across the project).
What we may do is the following:
1. Make sure that we stick to the recommended todo keywords, so that
todo keywords have a known-in-advance class in html export.
2. Put notes into LOGBOOK drawers (set `org-log-into-drawer' in WORG
dirlocals)
3. Change `org-html-format-drawer-function' during publishing to mark
the LOGBOOK drawers with a distinct class.
4. Enable org-inlinetask library during publishing.
Then, the CSS switch will involve toggling visibility of (1) todo
keyword classes; (2) inlinetask class; (3) LOGBOOK drawer class.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-04-01 11:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 14:35 [Worg] CSS improvements Adam Porter
2024-03-23 14:49 ` Ihor Radchenko
2024-03-24 6:14 ` Adam Porter
2024-03-24 8:56 ` Ihor Radchenko
2024-03-24 9:28 ` Dr. Arne Babenhauserheide
2024-03-25 14:09 ` Adam Porter
2024-03-26 14:48 ` Ihor Radchenko
2024-03-27 3:20 ` Adam Porter
2024-03-28 11:44 ` Ihor Radchenko
2024-03-28 12:41 ` Adam Porter
2024-03-28 13:18 ` Ihor Radchenko
2024-03-28 17:53 ` Adam Porter
2024-03-29 9:48 ` Ihor Radchenko
2024-03-29 22:38 ` How to organize tasks about Worg within Worg documents (was: Re: [Worg] CSS improvements) Adam Porter
2024-03-29 23:30 ` Thomas S. Dye
2024-03-30 2:27 ` How to organize tasks about Worg within Worg documents Adam Porter
2024-03-30 10:47 ` How to organize tasks about Worg within Worg documents (was: Re: [Worg] CSS improvements) Ihor Radchenko
2024-03-31 15:43 ` How to organize tasks about Worg within Worg documents Adam Porter
2024-04-01 11:34 ` Ihor Radchenko [this message]
2024-04-01 18:02 ` Adam Porter
2024-03-26 22:12 ` [Worg] CSS improvements David Rogers
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=87cyr98gfw.fsf@localhost \
--to=yantar92@posteo.net \
--cc=adam@alphapapa.net \
--cc=emacs-orgmode@gnu.org \
/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).