Mario,
Thanks for your responses. I built a macro for "active todo items" for the
checkbox idea and more; below;
It is clear the processing of pragmas is a black box I cant see in. So
thanks for being patient with my suggestions.
- The following does work as a pure macro, it is simply to give an
outline of how I though we may accommodate macros
- I understand if it is technically impossible or difficult, no need to
explain why if so.
*I use the below macro as follows*
In this example below the macro is called thus
<<☐ """This is a todo line""">>
<<☐ "This is another line">>
I expect it is too late in the rendering process; but it seems common sense
(does not mean it is) that some pragma could read as such;
°☐ "This is a todo line"
parsed to
<<☐ "This is a todo line">>
and thus call the macro
In this case I am accepting if I wanted to pass other parameters to the
macro the first, the content needs to be quoted.
Eg
°☐ "This is a todo line" color:"blue"
In this case I am using the customise simply as a shortcut. Which is easier
to read. An editor toolbar would wrap lines with prefix "°☐ "suffix ""
The pragma would wrap it with prefix "<<symbol " suffix ">>"
This is not finished, I plan to reduce line spacing between items, allow
text and possibly more, to be edited inline.
Regards
Tony
*The macro(s) just for completeness*
\define done-check(tiddlername)
\whitespace trim
<$set name=tiddlername value="""$tiddlername$"""
emptyValue=<<currentTiddler>> >
<$list filter="[<tiddlername>!done[yes]!done[cancel]]">
<$button tooltip="click to indicate done" class="tc-btn-invisible">
<$action-setfield $tiddler=<<tiddlername>> done="yes"/>
☐ $(content)$
</$button>
</$list>
<$list filter="[<tiddlername>has[title]done[yes]]">
<$button tooltip="click to cancel or reset" class="tc-btn-invisible">
<$action-setfield $tiddler=<<tiddlername>> done="cancel"/>
☑ $(content)$
</$button>
</$list>
<$list filter="[<tiddlername>has[title]done[cancel]]">
<$button tooltip="click to reset" class="tc-btn-invisible">
<$action-setfield $tiddler=<<tiddlername>> done="no"/>
☒ $(content)$
</$button>
</$list>
</$set>
\end
\define ☐(content)
\whitespace trim
<$set name=todo-tiddler value="""$:/todo/$(currentTiddler)$/$content$""">
<$set name=content value="""$content$""">
<$tiddler tiddler=<<todo-tiddler>> >
<$button tooltip="This is marked as a todo item, click to change status">
<$macrocall $name=done-check/>
</$button>
<$list filter="[all[current]has[text]]">
{{||$:/core/ui/Buttons/edit}}
</$list>
</$tiddler>
</$set></$set>
\end
On Sunday, 20 September 2020 at 21:58:37 UTC+10 PMario wrote:
> On Sunday, September 20, 2020 at 6:02:43 AM UTC+2, TonyM wrote:
>>
>> Mario, Et al.
>>
>> More review and research into the extensibility on top of Version 0.4.1
>>
>> I just did this in a tiddler
>> \customize degree="button" _element="$button" mode="block"
>> \customize tick="kbd" _element="kbd"
>>
>> °button Content
>>
>
> As I wrote. Don't try to work with the button-widget in an other way as I
> suggested in the last reply. It won't work out.
>
>
>>
>> ´kbd This is > [[A List]] > of items
>> another
>>
>> However I am confused the content button has the kbd result wrapped onto
>> the same line but the word "other" seems to me to be more than one line
>> below.
>>
>
> IMO that's a *bug* in the plugin... because of _element="$button" ...
> _element="div" works as expected. I'll have to have a closer look.
>
>
>>
>> This continues to be a stumbling block, I am trying to commit to memory
>> how to make use of the two cases \n and \n\n when customising.
>>
>> 1. Such as customising something so it occurs until the end of line
>> only, or until a blank line "\n\n" only
>> 2. once I master this I need to work out how to have the result
>> generated on the current line, and in other cases to end with a blank line
>> 3. Then I want to find how to apply things inline, like in a middle
>> of a sentence.
>> 4. I am also well aware of the endString, but here I am looking for
>> the line based customisations without having to specify an endString.
>>
>> Perhaps its the 24 hour break I had, or Sunday laziness, but it could
>> also be a lack of clarity either in the solution or in the documentation.
>>
>
> No seems to be a bug. ...
>
> -m
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywikidev/63b2ced1-2663-4b81-b671-24d69ec81260n%40googlegroups.com.
