On Wednesday, September 23, 2020 at 10:49:18 AM UTC+2, TonyM wrote:
This example not only shows that the customise pragma can be used to store
> a canned filter for reuse, but also shows how the first in a nested list
> can be concealed behind a helpful name like system-shadows
> \customize tick=system-shadows _element="$list" filter=
> "[all[shadows]is[system]]"
>
> ´system-shadows <$list filter="[all[current]has[caption]] +[!is[blank]]"
> >{{!!title}} {{!!caption}}<br></$list>
>
Very interesting! .. If you use the template=xx parameter in the pragma and
move the second list into the template, it could look like this.
´system-shadows-plus-caption
Similar to my examples in the last post, but without the _srcName parameter
> I am confident with* Mario's nesting method* a simple line could define a
> set of nested lists with the content of the line equal to each final record.
> If named well the variable set for each nested level will make the wiki
> text look like some 4th Generation reporting languages.
>
Yea, I think using the right naming is essential to create "wikitext" that
is selfexplaining.
> 'customers `country `state {{{ [all[current]size[large]] }}} Automatic end
> string for each on \n?
> But in this example I think the last filter here, on the line, needs to be
> in a list because otherwise it generates unnecessary line breaks
>
This is approaching simpler than SQL
>
>
> - Of course if somehow we can pass the filter to each nested level,
> not only would canned filters be used.
>
> That's possible with the _srcName config. ... For 1 parameter
> - However if one has structured data in a wiki it would be simple to
> create the set of canned filters for handling the structured content in
> the
> wiki.
> - For users of a wiki (rather than owner designers) it may be
> simple to provide them the info they need to generate any list or report
> - Especially with some useful templates.
>
> In the following case we use a list template
> \customize tick=all-tiddlers _element="$list" filter=
> "[is[tiddler]!is[system]]" template="$:/core/ui/ListItemTemplate"
>
> ´all-tiddlers This does nothing so can describe it
> This is another case where passing the template value may be helpful
>
;) See last post.
> I am working on a better way to name templates/transclusions so the above
> could read
> \customize tick=all-customers _element="$list" filter=
> "[is[tiddler]!is[system]object-type[customer]!archive[yes]]" template=
> "(customer-record)"
>
> ´all-customers List all customer-records
>
>
> By the way, If the List widget was to contain two new parameters before
> and after, that could provide header and footer content, Only if there were
> content, this would expand further, allowing content and or table headers.
> I miss foreachtiddler still :(
>
You can use a $macrocall widget here. IMO it should be simple. The default
_srcName is src . So the macro will bet a "src" parameter, which can be
used in the macro. src can be passed to the list-widget and the macro body
can contain "before" and "after" elements.
IMO it's not needed in the list-widget.
Thx for sharing
-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 tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywikidev/42912d3b-ea6b-4cba-801b-d22edefc8b1ao%40googlegroups.com.
