Mat, Thanks for more input, that is what I call collaboration
> Of course, it expects the user to do some (very basic) html coding in the > wikitext - which is fine by me and anyone who masters html, but... > No expectations here. If you want to use reveal widgets or list widgets as long as you know the name of the field or state tiddler that is generated by your button you can use standard methods and ignore the css approach. To me it is simpler to learn than the two button and multiple reveal methods that are documented today. > > ...or, actually, can wikitext elements have css IDs? > Yes they often do already, but they are not named *buttonname*-true *buttonname*-false Perhaps we should alter a class name instead or as well. There is however a lack of good documentation telling you what classes apply to what tiddlywiki objects, even although the information is contained in tiddlywiki. Perhaps invent some of my own. > One thing to note - at least I think this is how it works - is that if > using it for a reveal widget; content isn´t evaluated in revealwidget > closed state whereas I believe merely hiding it with display:none does > evaluate it. (...right?) > I think you are right, lets check, however as suggested, use the reveal widget with the toggle, if this is what you are after. > > >> Note: *Using variable=nul in a list widget* >> > > That's an interesting use of the variable. Still, I'm not sure why it > would be needed in the macro. (Makes me wonder if I also have such > "personal touches" that slip along with my public stuff? Hard for one self > to tell. ) > To be sure it is called nul because it is not needed in the macro, but we want original <<currentTiddler>> to be available so we use the variable. I would love to see more sharing of code practices that make sense, I think this one does. > > > >> On reflection I can see that something similar could be done for a range >> of items beyond a toggle/reveal combination, I am thinking of check boxes, >> Detail reveals, multiple values select dropdowns etc... What interests me >> is finding a simple way to have interactive documents in which you make >> choices and different information reveals itself. >> > > In deed interesting. > > Some more notes to consider before you publish: > > - Inform that buttonname must obey field name rules. (slugify need > <https://github.com/Jermolene/TiddlyWiki5/issues/3379> keeps popping > up) > > Agreed field naming and HTML ID naming rules. > > - Must enclose $buttonname$ in triple quotes in some places or <__$$__> > > Of course you are correct but not doing so will allow button names that are not slugifield from being used and thus breaking. I will look through to see the consequences. > > - Nit pick > > <https://www.google.com/url?q=https%3A%2F%2Fwikidiff.com%2Flabel%2Flable&sa=D&sntz=1&usg=AFQjCNHxSInnITk7uqKGwkxaILiIJBbsmQ> > > Not a nit > > <:-) > -- 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/9628c44b-43b9-4593-b4ee-611bef65d897%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
