In what seems to be related I have played with building an additional macro that given a named tiddler and html tag can extract blocks of text in a named and also arbitrary html tag, the idea is to be able to extract the content of such tags and perform other actions on it.
- This way a class and css can be applied to such “blocks” defined by those arbitrary tags, starting with “display: none;” to hide it.
- We could extend this to include widgets to extract its content, or raw body text.
A general solution available as macros and widgets would have broad applicability whist satisfying the OT.
There are some devil in the details but I think a powerful extension of design and innovation would be forthcoming. Complications include.
- Nested tags/widgets
- ignoring and/or extracting the parameters in the opening tag.
- Being able to treat the content using a “custom render” inside a tag/widget block “in line” inside the rendering of the text, rather than via methods such as above/below the text in a view template.
- This would be like allowing custom “blocks” within the text body to be rendered by custom renderers by design.
Here is a simple example
something
<quicklist class="quicklist">
Item one
Item two
another item only separated by new line
each could become a tags with a checkbox etc...
</quicklist>
something else
- In this case just the text inside the quicklist tags will be handled differently to the normal render, perhaps like raised here