An way to classify the tasks #95

davi-jorge-art commented 2026年06月11日 12:33:29 +02:00

An way to classify each task ( "important" , "at home" , ...) . As tags are to notes and I haven't found a use for # maybe it will be an option : we put the hashtag after a task , appear the selection as for the tags (thank you a lot for #84 ) and a filter on the task view...More useful than the "note" "filter"

An way to classify each task ( "important" , "at home" , ...) . As tags are to notes and I haven't found a use for # maybe it will be an option : we put the hashtag after a task , appear the selection as for the tags (thank you a lot for https://codeberg.org/ArkHost/HelixNotes/issues/84 ) and a filter on the task view...More useful than the "note" "filter"

Stephane-30 commented 2026年06月11日 22:36:38 +02:00

Inline tasks is a great feature. I used it extensively in AmpleNote. My view on the implementation is to separate inline task completely from standard markdown checkboxes. They may look similar but serve very different purposes. I have lots of lists in my notes - for example many notes with gear lists for various projects. They are exclusively to check if gear is in my boxes.
To my knowledge there is no standard for (timed) tasks in Markdown, so the developer should be free to implement task in the most appropriate way for the app.

Inline tasks is a great feature. I used it extensively in AmpleNote. My view on the implementation is to separate inline task completely from standard markdown checkboxes. They may look similar but serve very different purposes. I have lots of lists in my notes - for example many notes with gear lists for various projects. They are exclusively to check if gear is in my boxes. To my knowledge there is no standard for (timed) tasks in Markdown, so the developer should be free to implement task in the most appropriate way for the app.

ArkHost commented 2026年06月28日 16:20:00 +02:00

Hello,

This has been addressed and enhanced in the last versions.

Closing this issue.

Hello, This has been addressed and enhanced in the last versions. Closing this issue.