Use/Allow ☐ and ✓ for ToDo lists

[blausand]

[Enhancement] Would be great if OpenTasks would also allow for using the fancy Unicode Symbols ☐ and ✓ instead of the simplistic but beautiful and intuitive [ ] and [X] for ToDo lists.

[dmfs]

We can certainly accept both, that's not a problem. The question is, which ones do we use when we write task back to the database?

[blausand]

Am 05.09.2016 um 10:22 schrieb Marten Gajda:

We can certainly accept both, that's not a problem. The question is, which ones do we use when we write task back to the database?

Hi Marten, thanks for your reaction

If OpenTasks is Unicode-savvy enough, i'd suggest that it "upstyles" from [ ] and [X] to ☐ and ✓, as the former are easier to type.

The first case that could lead into trouble, is when $user wants to extend an existing ToDo list outside opentasks:

• $user would have to copy&paste the symbol
• OR find the unicode special characters ☐ http://www.fileformat.info/info/unicode/char/2610/index.htm and ✓ http://www.fileformat.info/info/unicode/char/2713/browsertest.htm on their keyboard (Impossible at least in Windows)
• OR the other client should also be able to upstyle
• OR the other client should also feature task lists from it's UI
• OR openTasks upstyles also "partially upstyled" ToDo lists.

Just 2ct of thoughts, blausand

[dmfs]

Initially I picked [X] and [ ] not only because they are readable, but also because they are understood by some markdown implementations. I don't known if that actually matters, but I expect that iCalendar will support rich text eventually and Markdown is certainly a good candidate for this.

Upstyling mixed lists (with ASCII and Unicode check boxes) shouldn't be a problem. However, we'll probably make this an option, so users can choose if they want to go with ASCII or Unicode check boxes.

[blausand]

Am 06.09.2016 um 14:47 schrieb Marten Gajda:

Initially I picked |[X]| and |[ ]| not only because they are readable, but also because they are understood by some markdown implementations. I don't known if that actually matters, but I expect that iCalendar will support rich text eventually and Markdown is certainly a good candidate for this.

Upstyling mixed lists (with ASCII and Unicode check boxes) shouldn't be a problem. However, we'll probably make this an option, so users can choose if they want to go with ASCII or Unicode check boxes.

Ah, that makes my thinking it over again. MD has no good stand for me after i experienced popular / preinstalled office / text editors don't support it. BUT you are absolutely right, it should be something that works out of the box. Therefore, i tend to adding ToDo list parsing to other clients* and keep the data field in content plain ASCII text.

BEGIN:VCALENDAR PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN VERSION:2.0 BEGIN:VTODO CREATED:20160906T130907Z LAST-MODIFIED:20160906T131035Z DTSTAMP:20160906T131035Z UID:37f6128f-67c7-4cf0-ab3e-78e6a3582364 SUMMARY:Support for ToDo lists in iCalendar DESCRIPTION:[ ] ask Lightning devs to add UI support for ToDo lists\n X-MOZ-GENERATION:1 END:VTODO END:VCALENDAR

[mkae]

I sync my tasks with my iMac and its tasklist application is able to display even the list of items since its a simple string.

I fear that Unicode might break this... But, needs to be tested.