Power List Features: Difference between revisions

Zains (talk | contribs)
No edit summary
Zains (talk | contribs)
No edit summary
Line 44: Line 44:
== View the status of your tasks ==
== View the status of your tasks ==
You can also view the current status of your Power List and its tasks on the ECH with the [[Power List View Status|view status]] feature.
You can also view the current status of your Power List and its tasks on the ECH with the [[Power List View Status|view status]] feature.
{{Infobox Feature
| name = Custom Todos
| version = [[Release 3.5.0|3.5.0]]
| tier = Standard, Premium and Enterprise
}}
[[File:Screenshot 2026-06-17 at 14.57.14.png|thumb|Example: Input - ECH custom Todo]]
[[File:App-custom-todo.png|thumb|Example: Output - App custom Todo]]
= Custom Todos =
Todo task labels support special prefixes and variables that control how tasks are rendered in the UI.
== Prefixes ==
Prefixes are detected by examining the '''first character''' of the label after trimming leading whitespace.
=== ''.'' (Dot) – Inline/Child Tasks ===
Prefix a task label with <code>.</code> to make it an '''inline child''' of the preceding non-dot task. Child tasks are displayed in a grid row alongside their parent, creating a compact horizontal layout.
'''Behaviour:'''
* The <code>.</code> prefix is stripped from the displayed label
* The task is grouped with the previous non-dot task as a child
* Displayed in a shared grid row (parent + children side by side)
* Checkbox is still shown (can be checked/unchecked)
* If a dot-prefixed task appears without a preceding parent, it is treated as a regular individual task
'''Example:'''
<syntaxhighlight>
Monday Breakfast
.Lunch
.Dinner
</syntaxhighlight>
=== <code>|</code> (Pipe) – Label-Only (No Checkbox) ===
Prefix a task label with <code>|</code> to render it as '''plain text without a checkbox'''. Useful for section headers, notes, or informational text within a todo list.
'''Behaviour:'''
* The <code>|</code> prefix is stripped from the displayed label
* No checkbox is rendered
* The item does not count toward the completed/total counter
'''Example:'''
<syntaxhighlight>
|Important Notes
Attend all morning sessions
|Evening Activities
</syntaxhighlight>
== Date Variables ==
Task labels support the <code><nowiki>{{EventDate}}</nowiki></code> variable, which is replaced with the event's start date displayed as day and month numbers (e.g., ''16/06'').
=== Basic Usage ===
{| class="wikitable"
! Variable
! Replaced With
|-
| <code><nowiki>{{EventDate}}</nowiki></code>
| Event start date (e.g., ''16/06'')
|}
=== Offsets ===
You can add or subtract days from the event date using <code>+</code> or <code>-</code>:
{| class="wikitable"
! Variable
! Replaced With
|-
| <code><nowiki>{{EventDate+1}}</nowiki></code>
| Event start date + 1 day
|-
| <code><nowiki>{{EventDate-1}}</nowiki></code>
| Event start date − 1 day
|-
| <code><nowiki>{{EventDate+3}}</nowiki></code>
| Event start date + 3 days
|-
| <code><nowiki>{{EventDate-2}}</nowiki></code>
| Event start date − 2 days
|}
Whitespace inside the braces is tolerated:
* <code><nowiki>{{ EventDate + 1 }}</nowiki></code> → same as <code><nowiki>{{EventDate+1}}</nowiki></code>
* <code><nowiki>{{EventDate- 2}}</nowiki></code> → same as <code><nowiki>{{EventDate-2}}</nowiki></code>
Unknown variables (anything other than ''EventDate'') are left as-is.
'''Example:'''
<syntaxhighlight>
{{EventDate}} Check-in at hotel
{{EventDate+1}} Follow-up meeting
</syntaxhighlight>
== Combining Prefixes and Variables ==
Prefixes and date variables can be used together:
<syntaxhighlight>
|Schedule for {{EventDate}}
Morning briefing
. Afternoon workshop
. Evening networking
</syntaxhighlight>
[[Category:3.5.0]]
[[Category:3.5.0]]