Mario, Perhaps there is something I do not understand but I am suggesting a specific symbol lets say ¤ as a working symbol
- Perhaps I can state it in different words? Consider this \customise sym=elementname _element=elementname ¤elementname that will internally parse this as if there existed a ¤elementname.classname and allowing class names You can see the customise is repetitive, but currently it must be explicit What I am suggesting is there is so much value in using customise just to take a named element name and allow a classname(s) to be applied and close it. <elementname> line or content </elementname> So I am asking if it would be possible to to convert any line beginning with a fixed special character to result in a open and close element of the immediate text. Arguably auto close on \n\n Why; - HTML elements, open and closed arbitrary or not, could be collapsed to ¤elementname.classname - Arbitrary html sections allow the author to mark-up their content according to logical names <abstract>This tiddler is about ....</abstract> - Then with a small set of css or macros and view templates we can alter the display, or search all tiddlers for such content - This works well *already* but I was wondering if we can replace this with ¤elementname.classname ? - Macros can either interrogate the rendered html or between ¤elementname and \n\n to extract the contents. For many users this would be a compelling use of the customise pragma but they would not need to define such customise parameters at all. Regards Tony On Tuesday, 6 October 2020 02:58:47 UTC+11, PMario wrote: > > On Monday, October 5, 2020 at 2:54:08 PM UTC+2, TonyM wrote: > > This makes me ask if one of out special characters could simply default to >> the element that follows the special character >> >> eg >> 'aside Content is an aside >> >> >> - That is nominate one of the special character to just automatically >> treat what follows as this does \customise tick=aside _element=aside >> >> This would be possible if we would check against an HTML list of "names". > which is already done, eg: _element="article" will have a look at: > https://github.com/Jermolene/TiddlyWiki5/blob/9716c326952c16f63345a135e73cf36670dca0d8/core/modules/config.js#L37 > > But we would probably need to update this list, since "Details" isn't > listed there. > > >> >> - So in fact we do not need to define any \customise tick=elementname >> _element=elementname >> >> We do for "names" that are not html tags. > > >> >> - This should be achievable programaticaly so any element name can be >> used including arbitrary html elements. >> >> including "arbitrary" tags is not possible, since this would limit the > names to html elements only. .. That's not what we want. > > -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/b97c2e46-e726-4c99-b2dc-bd0a5bebe512o%40googlegroups.com.
