On Monday, September 21, 2020 at 7:42:38 PM UTC+2, @TiddlyTweeter wrote: BUT are we seeing a version of Advanced Yoga (bloke was able to twist his > leg behind his head)? >
Probably yes. ... > My concern is it will confuse adding macros. Let's see. > With TW5 Jeremy invented the widgets. Widgets are more complicated to use than macros. ... BUT they are more powerful, since they expose all parameters, that can be used. On the other hand, the learning curve is much steeper with widgets. eg: Let's have a closer look at the <<list-links filter:"[tag[HelloThere]]">> macro call. .. It's simple and does a decent job. Right? The usecase above is the most common. But in reality the macro has a lot more parameters: filter, type, subtype, class and emptyMessage <https://tiddlywiki.com/#list-links%20Macro:%5B%5Blist-links%20Macro%5D%5D%20%5B%5Blist-links%20Macro%20(Examples)%5D%5D> . So if you want to use all params it looks like this: <<list-links filter:"[tag[HelloThere]]" type:"ol" subtype:"li" class:"test" emtpyMessage:"Nothing found!">> Which is already more complicated. ... But still much easier as the real code. \define list-links(filter,type:"ul",subtype:"li",class:"",emptyMessage) \whitespace trim <$type$ class="$class$"> <$list filter="$filter$" emptyMessage=<<__emptyMessage__>>> <$subtype$> <$link to={{!!title}}> <$transclude field="caption"> <$view field="title"/> </$transclude> </$link> </$subtype$> </$list> </$type$> \end --------------- The problem now is, that if you _have_ to use a macro like this, it already has the potential to confuse readers. <<list-links filter:"[tag[HelloThere]]" type:"ol" class:"iNeedIt" emtpyMessage:"Nothing found!">> With custom-markup plugin we can reduce this to: \importcustom [[customOrderedList]] °orderedList [tag[slide]] So the only thing the user has to see is the above 2 lines. ... And if the "names" are chosen in the right way it shouldn't need more explanation. --------------------- The content of "customOrderedList" is a bit tricky but that's not, what the user has to see: \customize degree="orderedList" _element="$macrocall" $name="list-links" type="ol" class="iNeedIt" emptyMessage="Nothing found!" _srcName=filter ---------------------- With definitions like this, it's possible to create new wikitext commands, that would be much more complicated to read. .... Well -- you could clone the "list-links" macro and change it in the way you need it. ... BUT then you also have to maintain it. ... And users are really hesitant to change the core. May be custom-markup is a way to go. We will see! > The issue is you will have to find a way to document BOTH major layout > change AND the indefinable scope of macros (not all though) elegantly. > I'm concerned its getting too complicated. BUT let us see. > That's right. -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/0fd888be-3180-4003-a45d-0916ea7c0c88o%40googlegroups.com.
