On Wednesday, September 23, 2020 at 11:13:10 PM UTC+2, TonyM wrote:
> However, without customisations
> Count: `<$count filter="[prefix[$:/state]]"/>` works
> Count: `<$count filter="[prefix[$:/state]]"</$count>` does not
>
There is a typo: you need to close the first widget element: `<$count
filter="[prefix[$:/state]]"></$count>`
> So I think this observation still stands.
> Since customise will generate </$count> It will not work
>
Not really. The string </$count> is like the _endString parameter for the
standard TW parser. So it doesn't need to be created.
I do not know how to identify others without exhaustive testing or reading
> (understanding) widget definition code.
>
see above typo.
As written with the _srcName parameter, there should be almost no limit in
> using any widget. ... except may be the <$button widget, if you want more
> than 1 parameter from the line.
>
>
> - *Can I ask?,* I have not test yet but is their any reason this would
> be limited to widgets?, because html could also make use of the content
> being applied to an attribute?
>
> Do you have any examples, that would need it. .. There is no special
reason.
>
> - Perhaps too much to ask if there were a way to pass SOME content
> into the src and other as usual treated as content.
> - In a dreamy state you could imagine any key=value pair in the
> "content" being translated to attribute=value with every thing else
> placed
> in the body.
>
> The problem is, that there is no way for the algorithm to know, if it is
content, or if it is key:value as parameter.
Wouldn't it be better to use the "real" widget call instead of making
"custom markup" more complex. I think, if we have parameters in the first
line, we loose the "readablility" advantage.
> Here is another experiment that has WORKED!
> \customize tick=style _element="style"
>
> ´style .mystyle { border: 1px solid green; border-style: dotted; }
>
> ;.mystyle Content
> ;Perhaps also;
>
> ´style {{myStyleSheet}}
> so one could have a
>
Yea, but that is not best practice. It will hide a <style> element, which
shouldn't be used except for examples... <style> will always win and if a
user wants to do some CSS customisation, those elements are very hard to
find.
But anyway. It's interesting..
-mario
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywikidev/67294a6c-6a58-44db-b5c5-168661c6ad09o%40googlegroups.com.
