[Feature Request] Sub Tasks

[TXS380]

I now that this extension is meant as a simple task editor but I still really miss the option to define subtasks. Like right now my editor often looks like:

• Main task1 - Sub task1
• Main task1 - Sub task2
• Main task1 - Sub task3
• Main task2 - Sub task1 ... While this works it adds a lot of redundancy and is not really comfortable to read and navigate. Would it be possible to add something as simple as indentation to simple task editor? Like:
• Main task1
  • subTask1
  • subTask2 ... I think this would really boost the overall usability and usefulness of the editor.

[moughxyz]

This is something we'd want to do with a dedicated outline editor, which can allow for infinite nesting.

[TXS380]

Alright, is this outline editor going to offers similar features like checkboxes? Do you have a roadmap or some rough idea when you are going to release the outline editor?

[kovdan01]

@mobitar Hello, is there some progress on adding this functionality? I like your app and appreciate your work, but suffer without this feature :( Could you please tell when this feature is expected to be implemented? Thank you in advance!

[moughxyz]

No updates here I'm afraid. Don't want to make any promises either. Just something we're keeping in mind.

[saizai]

Was going to request this.

Two small changes would help significantly:

• allow nesting
• allow more than one newline in an entry (currently, it allows exactly one (!) newline, which is just plain weird).

A few larger changes would help more:

• allow reordering items within any nesting level, by "burger" / long press handle
• allow marking items as having a due date/datetime, by which they can be sorted, and a configuration of CSS for the item based on time remaining — e.g.:
  • {maxremaining: -1, css: ".taskitem {color: red: font-weight: bold; order: -1}"} (i.e. womp womp — overdue and not completed, because a completed item would have nil remaining)
  • {minremaining: 60*60*24, maxremaining: 60*60*24*7, css: ".taskitem {font-style: italic; order: 4}"} (i.e. kinda urgent — due within the next week but not today)
  • {minremaining: 60*60*24*30, css: ".taskitem {opacity: 0.7; order: 10;}"} (i.e. not urgent — due over a month from now)
  • I'm not aware of any way to do the quantity trigger in CSS; attr is only supported for content currently; order requires a numeric, not a string; and calc isn't supported in selectors, only in values. Alas.
  • Note: ordering, however, can be done with CSS order, if you want to override the default ordering. Just set the container to display: flex; or display: grid;. However, note that this isn't accessible to screen readers; JavaScript should monitor the order and actually re-sort the DOM accordingly, so that it works for blind users too.
• allow marking items as having recurrence, either
  • after X [hours / minutes/ days / weeks / months / years] from when it was last marked completed (or the manually set due date as a one time override, if that exists and is later)
  • every X [h/mi/d/w/mo/y] from last manually set due date
  • crontab style, every (X,*,*/X) tuple of [min/hr/dom/mo/dow] (or again, one time manual override if set & later)
• allow marking items as having user/style-configurable tags (eg "priorities"), with global/style & pad-specific configurable CSS for item & tag (e.g. "low-priority" ones are dimmed, "needs research" are in blue, w/e), and numeric weights (priorities) for each by which they can be sorted
  • note that this can be done 100% using CSS selectors, including as modifiers of the time based styling above (using e.g. CSS combining selectors, like :not(.completed).recurring.my_project — where some of those classes are reserved and set by the editor, and some are tags, or pad labels). No special logic required — just stick the tag in the item as a class, append a div of tag spans, and allow an option for entry of the matching CSS.
• allow it to be combined with an inline-formatting editor, like Markdown Minimalist