I can add even more complexity of use-case(s). A version that is editable and when saved generates a static html version that the public uses. This one requires an actual http server and is more of a content management system.
On Tuesday, June 13, 2017 at 9:36:00 AM UTC-4, @TiddlyTweeter wrote: > > This thread springs off from a previous one at > https://groups.google.com/forum/#!topic/tiddlywiki/JeuinlhzMNU in which > Ton Gerner and Stef contributed good stuff. > > Stef's economical solution > <https://groups.google.com/d/msg/tiddlywiki/JeuinlhzMNU/pcQWJ9IFCQAJ> to > quick "Read Only" settings got me thinking. > > > > *WHAT IS "READ ONLY"?*The issue with enabling "read-only" mode in TW > quite often comes up. > > TBH I find it a less than an optimal way of thinking about the issue. *Its > too crude to the reality.* > > What IS the issue? Of course, its switching off access to functionality, > usually through CSS, so users don't get access to some stuff. It makes > their experience cleaner and to the point. It means the author can control > their public presentation. > > But WHICH functionality is switched off? Its not all one thing. There is > no such thing as THE way to do this. There is no such thing as a definitive > "Read Only" TW so long as you have a live Javascript machine under your > mouse. > > Different situations require differential accommodations. So, I think > "Read Only" is actually confusing the issue, though its a fine panhandle, > it does capture one general idea quite well, yet its also a bit of > dumbing-down. > > *USE CASES* > > We can do better ... Here are a few ... There are many others ... > > #1 - A TW of a Novel where you want to allow users to add annotations & > bookmarks but not to be able to directly create new Tiddlers, or ever see > anything starting "$:" With simple text search, no advanced. > > #2 - A TW that is always one main transcluding tiddler ("the page"). > Additions allowed through a modal editor but result are always constrained > to appear in that transcluding tiddler. (ToDoNow plugin by Telmiger > approximates this model) > > #3 - A TW that is used to present one Tiddler as an apparently static page > via a permalink. FullScreen. No menus. No Sidebar. No Editing. No Save. No > internal links. > > You get the idea. > > > > *GLOBAL SOLUTION?*Stef's approach to get together in one place many > settings in an economical form was really suggestive of possibilities. > > I was thinking that solution could be expanded with more options. Like > removing all menus etc. > > But also add, IF it were possible to have checkboxes next to every item. > Then the VARIABLE NEEDS evident in the Use Cases above, and more, could > become doable. > > My problem is I am not a programmer, but I can see we could get a lot more > fine-grained on "Read-Only", which should really be called something More > Positive like: > * "User Edition Settings".* > Best wishes > Josiah > > > -- 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/8e0dc39f-6d0e-43d2-8293-4e9384e37f8f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
