Hi Tobias I agree -- and widgets tend to be more easily found and re-used, and better documented. On numerous occasions I know I have seen/used a snippet of wikitext to solve a similar problem, but can't lay my hands on the snippet.
Too many widgets will, however, bloat the codebase. It's a matter of designing a few 'clever' widgets which are generally useful. In this regard, I believe many of the existing widgets need redesigning and consolidating. The redesign of my button widgets ended up with only three widgets (and I am working on reducing this to only two.) The major constraint -- backward compatibility :-( regards On Friday, 11 December 2015 12:32:25 UTC+2, Tobias Beer wrote: > > > I know we can (try to) achieve complex wikitext constructs to make ends > meet with (sometimes a plethora of helper-)macros, but ... Those wikitext > macros are quite horrible to both develop and maintain. > > > *QUESTION* > > To force a child widget being a reveal into either block or inline mode, > do I simply set *isBlock: true / false*? > The handling of the 'mode=' attribute of the $transclude widget may suggest some ideas regards -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/e557cea9-5802-45d8-b22e-c37418fe6578%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
