Hi Tony
> Html is still quite usable in tw5 but as you know actions need to be mediated
> through widgets and I understand why. However there is a rich source of
> content and methods in html5 we cant make use of because of this. I do ask
> myself if a few widgets, kind of widget primitives, co
Tony!
On Sunday, August 4, 2019 at 5:18:44 PM UTC+4:30, TonyM wrote:
>
> Mohammad,
>
> Give this example of yours I currently use another pattern for something
> similar. So I thought It a good time to share.
>
> \define display(template)
> <$set name=template value="$template$" emptyValue=
> "$
Mohammad,
Give this example of yours I currently use another pattern for something
similar. So I thought It a good time to share.
\define display(template)
<$set name=template value="$template$" emptyValue=
"$:/plugins/kookma/timelines/templates/gilan" variable=null>
<$transclude tiddler=<> mod
Jeremy,
Tiddlywiki is rich and wonderful now. It took me time to jump to tw5 from twc.
This history help explains to me a little of why this transition was difficult
for me and where I perceive limitations.
Given the context of this thread, perhaps I can express a hard to express idea.
Html i
Thanks Tony! That's quite true!
Also,
This if-then-else gives a huge flexibility! One example
<$list
filter="[<__template__>match[default]then[$:/plugins/kookma/timelines/templates/gilan]else[$template$]]"
variable=templateTiddler>
<$tiddler tiddler=<> >
<$transclude tiddler=<> mode=block/>
Mohammad
So with that clarification, I would suggest the methods in the case example I
gave addresses many.
Most branching is about selective display and nesting.
Are you looking for something else?
Regards tony
--
You received this message because you are subscribed to the Google Groups
"T
Thank you all for these descriptive replies!
By the way branching here means decision making and executing part of code
based on that! Sخ $list with emptyMessage has a simple branching logic!
--Mohammad
On Sunday, August 4, 2019 at 1:57:48 PM UTC+4:30, Jeremy Ruston wrote:
>
> Hi Tony
>
> Your
Hi Tony
Your description is very nicely put.
The curious thing for me about both the filter language and wikitext is that
they both evolved from very simple initial conditions:
* The filter language evolved from the idea a simple list should be a valid
filter, evaluating to the titles in the l
Mohammad,
Can you clarify what you mean by branching?
Despite my investigating replacements for common structures in procedural
programing languages, Tiddlywiki is not actually procedural. Even when you
trigger a "batch" operation control is returned only once it is completed
and everything vi
This is great!
Still we have not real branching with then-else
but we have
if NonEmpty
return then part
else
return else part
end
And we need a construct like you proposed!
--Mohammad
On Sunday, August 4, 2019 at 10:47:34 AM UTC+4:30, TonyM wrote:
>
> Mohammad
>
> This structure will return t
Observation
~[[false]]
or else false
Is equivalent to else[false] in some circumstances, but it can be placed
within a single run.
Retards
Tony
On Sunday, 4 August 2019 00:06:14 UTC+10, Mohammad wrote:
>
> While there were alot of request for simple conditional operations, it
> seems the new
Mohammad
This structure will return true only if the input is true, any other value
including empty will return false
<$set name=input value="true">
<$list filter="[match[true]else[false]]" variable=returned>
<$set>
Thus inside the list you can test
<$list filter="[match[true]]">
12 matches
Mail list logo
