Re: How to organize tasks about Worg within Worg documents

2024-05-12 Thread Adam Porter
On 5/12/24 07:18, Ihor Radchenko wrote: I looked into this further, and found exporters/taskjuggler/ox-taskjuggler.org that has whole "TODO" subtrees hidden with :noexport: tag. Such half-ready subtrees are not really ready for normal viewing and are mostly a material for WORG hackers to work

Re: How to organize tasks about Worg within Worg documents

2024-05-12 Thread Ihor Radchenko
Adam Porter writes: >> 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. >> >>

Re: How to organize tasks about Worg within Worg documents

2024-04-01 Thread Adam Porter
On 4/1/24 06:34, Ihor Radchenko wrote: 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.

Re: How to organize tasks about Worg within Worg documents

2024-04-01 Thread Ihor Radchenko
Adam Porter 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

Re: How to organize tasks about Worg within Worg documents

2024-03-31 Thread Adam Porter
On 3/30/24 05:47, Ihor Radchenko wrote: Adam Porter writes: Using a normal heading for a task would "commandeer" the structure of the document, which I think is a real problem. Not really. If some section is incomplete, marking it "TODO" means that it should be completed. And the details

Re: How to organize tasks about Worg within Worg documents (was: Re: [Worg] CSS improvements)

2024-03-30 Thread Ihor Radchenko
Adam Porter writes: > Using a normal heading for a task would "commandeer" the structure of > the document, which I think is a real problem. Not really. If some section is incomplete, marking it "TODO" means that it should be completed. And the details might be listed in the logbook notes, for

Re: How to organize tasks about Worg within Worg documents

2024-03-29 Thread Adam Porter
Hi Tom, On 3/29/24 18:30, Thomas S. Dye wrote: Here's another potential solution that I find useful. d. Keeping tasks under a heading held back from export. I have a capture template that saves tasks about the document under a * Tasks :no-export: heading.  To keep the agenda sane, I don't add

Re: How to organize tasks about Worg within Worg documents (was: Re: [Worg] CSS improvements)

2024-03-29 Thread Thomas S. Dye
Aloha all, Adam Porter writes: On 3/29/24 04:48, Ihor Radchenko wrote: Also, we may consider re-using inlinetask style for TODO: entries. Rather than #+begin_center TODO: Even better, find a volunteer to maintain this information! #+end_center We can do

How to organize tasks about Worg within Worg documents (was: Re: [Worg] CSS improvements)

2024-03-29 Thread Adam Porter
On 3/29/24 04:48, Ihor Radchenko wrote: Also, we may consider re-using inlinetask style for TODO: entries. Rather than #+begin_center TODO: Even better, find a volunteer to maintain this information! #+end_center We can do TODO Even better, ... That is a lot of