Mat et all Please excuse my long winded reply howevery i belive it contains some very powerfull oportunities.
Mario needs to confirm this but as I understand the pragma demonstrates the mechanisium and customisation however the defaults can be used once installed. Especialy my proposed defacto standard for author styles could be used without learning about the pragmas. How ever if someone wants to build additional wikitext shortcuts or html constructs for their own writting or to provide tools for refactoring external content using the pragmas add substantial features and customation. Pragmas within text help in transferability with the plugin and perhaps the core eventualy the only requirement along with tiddlers self contained pragma. If you are an author or designer and develop a suite of customised markup or wikitext escape sequences that you want to publish you will need to document and package with the instructions and dependancies just as you may a macro or plugin. I think code clarity can be developed such as using import pragma to rule in a set of custom pragma. In a recent post Eric provided a CSS solution to customised bullets, subsequently i asked how to stop an inline style tag from impact other tiddlers on screen, the answer is to qualify every class. I realise now that with this new solution we can define the custom styles inline since they can be applied with the tick in the body, and they may only be reflected in applied ticks. This reduces css bleeding into other tiddlers on screen unless they use tick. From this i can forsee the invisible display of pragma and styles hidden on screen that applys to all displayed tiddlers using the defined excapes. I can imagin alternate styling and pragma definitions being used without tiddler changes. I imagin designers may write a set of pragma and styles that map to different writting or layouts, such as newpaper, magazine, govt documents, scientific papers, (even using additional markup like katex). This why i see value in a de facto perhaps even de jure additional markup pragmas and styles. They would be focused around the kind of elements on page eg block quote, asside, footnote references, bullets, article, section, multiple columns, header, footer, code, warnings and cautions etc... keep in mind that the css content attribute allows unicode icons to be introduced as well. I can forsee someone building a set of pragma and styles that resemble say the dummies and idiots guide books. If your text used the de facto markup pragmas and styles an import pragma would imediatly lay it out similar to a dummies guide. With all this in mind i think we can come up with a defacto extended markup by starting with identifying evey kind of element not already in wikitext you may choose to use in text and provide a MVP. We can also support interactive and print ready cases like the details widget transforming to an open text box for print. It may be easy to build a layout set that makes text look like say wikimedia output. In fact i am not sure but it may be possible to generate output that is infact a reparsing of wikitext into another markup you can copy as text and paste. further inspired Tony On Wednesday, 9 September 2020 at 06:52:59 UTC+10 Mat wrote: > Interesting developments. > > \customize is the perfect name for this pragma! > > A critical question (which kind of brings back things I stated in the very > beginning of this thread/discussion): Who should use this? > As noted, there's a distinction between tiddlyfiddling/coding vs. > notetakeing/authoring. But even for the former, those are very complex > pragmas and if one is even supposed to add multiple of them... hmmm. Maybe > the whole construct should be a stamp? (But, there's already four from > this!) > > <:-) > -- 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/738f4f0c-0841-489b-a114-f6b6018874b4n%40googlegroups.com.
