Mario, View on top of V4.1
- I think you could delegate the historical methods to a link rather than have them complicate the documentation from the beginning. How to style a Paragraph <https://wikilabs.github.io/editions/tick-text/#How%20to%20style%20a%20Paragraph> Misusing standard wikitext to indent a paragraph <https://wikilabs.github.io/editions/tick-text/#Misusing%20standard%20wikitext%20to%20indent%20a%20paragraph> . - Will there be some smart defaults for each special Characters out of the box, so unless they are inadequate they serve a purpose right away? - angel is already somewhat defined - If so a list of special Characters and their default functionality up front and an explanation of the buttons would be enough to get started. Including the name used in the customise pragma eg degree, perhaps the official character names would also help some. - Perhaps for shortcuts you could suggest in the doco the user may select alternatives that map to a similar character on their keyboard layout eg alt-' for tick alt-. for its shift > value for angle etc... - "markup for advanced users", yet to be written could be "use focused" (initially) rather than technically the current solution eg - Introducing html tags into you own markup - Using classes to rapidly style your content with css - Using the end string or \n or \n\n to terminate your custom markup - It may also provide one or more "libraries" of css that can be activated. In future you could add effective ones, developed in the community (like mine :) - When ever a solution enables the accumulation of techniques and methods it improves over time. - Perhaps in https://wikilabs.github.io/editions/tick-text/#Custom%20Markup%20Definition explain why the parameters begin with an underscore, this helps understanding and remembering the fact. *Wiki text integrations* By the way, this is so cool, and possibly replaces the need for custom macros in many cases. meaning once you know how to use is not need to write the macro solution when you can use a custom wikitext marker - This area will take sometime to explore; here is a quick test of mine, how would we go about forcing a line feed or using a template? \customize tick="listtagging" _element="$list" filter= "[tag<currentTiddler>]" ´listtagging \customize tick="listtagging" _element="$list" filter= "[tag<currentTiddler>]" template="$:/core/ui/ListItemTemplate2" ´listtagging This works with a break after the link widget in the template \customize tick="listprefixed" _element="$list" filter= "[all[]prefix<currentTiddler>]" template="$:/core/ui/ListItemTemplate2" ´listprefixed Questions - Do you want a continued search for appropriate uni-code characters or are you happy with the available ones? - As in the examples above *Wiki text integrations* how do I make these useful options global? - I am confident I will want to push examples like ´listprefixed into view templates and macros so I must test these. Do you foresee any problems? My Review continues; Tony On Friday, 18 September 2020 07:02:49 UTC+10, PMario wrote: > > Hi > > New Version 0.4.1 https://wikilabs.github.io/editions/tick-text/ with > more docs! > > @Mat, there should be enough Basic, Advanced and Reference material now, > to test it! > > No new functions > > have fun! > 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/cbc2a48c-2a9f-4966-80fc-db256ac22223o%40googlegroups.com.
