Hi Mat, > Why is this a problem? >
Because it will suggest you actually made edits to it, and you really didn't. You simply wanted to use the ui, rather than change something about the tiddler. > Whichever tiddler that stores it will be modified, no? (...or are perhaps > tiddlers prefixed $:/state/ treated differently in this? I can't find info > in the docs.) > Yes, and that is what states are for: they store states. And yes, they are treated differently. For one, they are system tiddlers and secondly, my wiki is set up to never save any of that. I don't expect, in fact, I don't want my wiki to load "exactly as I left it". I don't expect that from other applications and I won't start expecting to see the popup I didn't close last time. > I'm thinking that if something can easily be made with html+css then this > is preferred before widgets beause the former is more browser native, no? > There is no intrinsic benefit to "browser native". TiddlyWiki builds on a browser's framework, yes.. well actually, it implements the same stuff a browser does: so both speak the same language. Other than that, we do have "native TiddlyWiki". If we just needed "browser stuff", TiddlyWiki wouldn't be what it is. Yes, if you can do things just using classes and hover states, that's fine. But here we are talking about a persisted state, one that you expect to stay after you clicked... at least for a given life-time, e.g. the tiddler / window / etc being still open. In TWC we did that doing dom manipulation ..in the later days with jQuery. These methods are, for the most part, a thing of the past. Most things are tiddlers now. But sure, we don't need to tiddlerify a hover-state or a mouse-position. At least that would simply be pointless for most cases. Perhaps it actually isn't. Not sure. Depends on what you wish to model. The paradigm these days is: make it a tiddler (or part of one)... and as you can actually see in your example: you very much adhered to that paradigm. The one reason not to use and abuse the tiddler you look at is: its state got nothing to do with its content: those are two independent layers. Content (Model / standard tiddler) <> UI (View / system tiddler)... and in-between all that TiddlyWiki being the Controller. Best wishes, Tobias. -- 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/a12443cc-87f1-4cad-82de-021e00a0db90%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
