Tony, Jeremy, thanks for replying. Jeremy Ruston wrote: > > > * It’s not backwards compatible. Right now there are lots of `<$button>` > widgets without any attributes that use action widgets to do their stuff >
How does the addition of temporarily creating the state tid make it not backwards compatible? I can see one problem; if the user already uses specifically $:/state/<title> ...but this has the same solution as my next reply: * The proposed algorithm for autogenerating the state tiddler title isn’t > robust enough to permit, say, two hide/show constructions within a single > tiddler > The qualify macro? (I was actually considering this aspect but reasoned that we do accept this problem with e.g the tag macro.) > An alternative approach might be to devise a macro <<accordian>> that > takes the text of the button and the title of a tiddler containing the > content. Then one could use the target tiddler title as part of the state > tiddler title, making it possible to have multiple accordions within a > single tiddler as long as they each target a different tiddler. > Hm... I've used these constructs and they're not particularly good. It solves the state tiddler title issue elegantly for but it is iffy to split out text into separate tiddlers and you loose the content view when you're editing. OK, the excision tool would simplify, and if you use preview edit (which I don't)... but still. AND you can't put the button and the content in different places. <:-) -- 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/4e365d68-44d3-42f7-a41d-4f871994fe4e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
