Here's an example. Unfortunately, there doesn't seem to be a way to force a default state for radio buttons. So the state will be whatever it was the last time the TW was opened. This is how it is with the TW "preview" mode as well, so I guess we should be used to it ... You could just put it in "blank" mode before closing.
I seem to recall that in the TWC there were "hooks" where you could put code that got executed when the page was first opened. Perhaps someone will know how to do the same thing here, so that the value of the stored state could be changed on boot-up. HTH Mark On Thursday, June 30, 2016 at 6:36:45 AM UTC-7, David Gifford wrote: > > Hi Mark > > Thanks for the radio idea. I think I would have to see an example that is > more substantial than the one at tiddlywiki.com in order to implement the > idea though. To answer your question: I usually use zoomin story view, so > having on preview mode that changes every tiddler's view mode would be > better. Also, default upon opening the file needs to be #4 (blank) to keep > from slowing the file down. But default after the first use is not > necessary. > > Dave > > On Thursday, June 30, 2016 at 8:20:10 AM UTC-5, Mark S. wrote: >> >> I'm sure someone will have a great solution for you. Off hand, I'm >> thinking that a radio button would give you your 4 conditions. Your viewer >> could then have 4 reveal widgets depending on the status of the radio >> button. Not sure if the radio button widget has a default (it's not in the >> docs -- the HTML radio button does). But would a default matter after the >> first use anyways? Or did you want a different setting for each tiddler you >> are viewing (unlike the "preview" mode which changes every tiddler's view >> mode). >> >> Mark >> >> On Thursday, June 30, 2016 at 5:23:50 AM UTC-7, David Gifford wrote: >>> >>> Hi guys >>> >>> I have a really cool idea, but it might be just a bit beyond me. I am >>> going to tinker today, but I figure you guys will have better ideas about >>> how best to do this. >>> >>> I currently tend to use a tiddler titled $:/.Children, and tagged >>> "$:/tags/ViewTemplate" . This tiddler lists links to the titles of all the >>> tiddlers with backlinks to the current tiddler. The list appears at the >>> bottom of the tiddler, below the text. >>> >>> I would like to be able to toggle between viewing four such "children" >>> in the open tiddlers: >>> >>> 1) $:/.Linksviewer: Lists only the title links for all backlinks. >>> 2) $:/.Printviewer: Shows the text field for all backlinks, separated by >>> a <hr>, >>> 3) $:/FullViewer: Same as #2 but also including a link to each of those >>> tiddlers [[(open)|title]], and >>> 4) Blank: none of the three previous are tagged "$:/tags/ViewTemplate", >>> and nothing shows below the text field. This would be default. >>> >>> Rationale: >>> >>> a) My notetaking for this TW would be adding individual observations, >>> quotes, etc and adding links (rather than tags) to related topics and >>> sources. The tiddlers would have datetimestamps to save me from naming the >>> tiddlers. Then I create topic tiddlers from the empty links in the note >>> tiddlers (and from the "Missing" tab). I have found this to be the fastest >>> way to add notes and connect them. I also tend to move from the top down by >>> creating table of contents tiddlers for broader subjects. >>> b) Different types of tiddlers need different types of displays of >>> related tiddlers. But viewers 2 and 3 would slow down TiddlyWiki if they >>> were default. At least, that has been my experience. Jeremy once told me it >>> is because it is a complex list filter being applied to the tiddlers. So I >>> am thinking that 1, 2, and 3 can be viewers that let you see this content >>> when needed, and turned off most of the time when speed is of the essence. >>> Maybe my reasoning is wrong, I don't know. >>> >>> I know how to create the 3 list filters. >>> >>> What I don't know how to do is create buttons to put in the sidemenu >>> that add the "$:/tags/ViewTemplate" tag to one viewer and remove that tag >>> from the other two. I was originally thinking of 4 buttons, but maybe a >>> dropdown list would be better? Also I don't know how to make #4 the default >>> when opening the TW. >>> >>> Anyway, this is a little beyond my ability and I was wondering if a few >>> of you might lend me a hand / suggestions. I will share the results freely >>> with everyone when I am done with it. >>> >>> Dave >>> >> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/e53afa7f-a504-4a4c-ad2c-42d45c89c7aa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Project_Dave1.json
Description: application/json
