Folks, A Few quick points.
I am not sure we need be so fussed if the character is not normaly available on the keyboard, we can access it many ways including EditorToolbars and even shortcodes, and this means it is much less likely to clash. I have not tested it but I abhor the @@ syntax for single lines or inline styles as it dominated too much, but it may be suitable and already work for applying css to a block of multiple lines, in which case it is better it be visible. One idea was to allow for named html tags like »div.classname This is text (Autocloses div at EOL) So the <dot> paragraph would become »p.classname Multiple lines can use the existing; @@.classname 1 2 3 @@ I think we may need to extend these ideas to inline css as well how can we trigger .classname inline ⇨.classname blah blah⇦ text continues Finally, I have not confused the sh-t or out you all; I am wondering about using custom classes, and content to inject functionality eg *.check Items details *.check Item2 details Would present check boxes to toggle if the items complete, ether only current session or indefinitely. This currently is confused by the fact CSS "is rendered at the last moment". Regards Tony On Sunday, 30 August 2020 22:30:17 UTC+10, Mat wrote: > > @PMario and @Tony > > I'm really looking forward to your plugin. Some questions: > > As PMario notes, the "indicator" characters are problematic especially the > » which doesn't even exist on many keyboards, including mine. So then... > how is that simpler than using e.g @@.class ? > > I take it that the style defs are customizable but would it be possible to > make the indicator character customizable? This would solve everything > since the user knows his own habits and keyboard. Even "Joe the Finger", > whos hacker career totally tanked after the accident (but he did get ever > so popuplar among the ladies), even he will be able to use your plugin > comfortably then. > > Maybe one could make a user modifiable dictionary like so > > » : <classnames> > i : <classnames> > ii : <classnames> > asdf : <classnames> > > (or even style definitinos directly instead of the classnames) > > Also, @Tony did briefly mention a dot classname syntax, i.e: > > .class My text/n > > without any other prefixing indicator. I didn't quite understand why this > is not possible, could someone explain? > > > <space><space>\n will be recognized as a hard linebreak with a second >> plugin. > > > When manipulating text in filters, can <space><space> be retained or do I > remember right that filters often trim space chars? > > <:-) > -- 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/a53762ce-4d43-4b52-99b8-35500f6a8b86o%40googlegroups.com.
