Thomas, I stand to be corrected, but clearly in the above example are we discussing https://Tupper.online <https://www.google.com/url?q=https%3A%2F%2FTupper.online&sa=D&sntz=1&usg=AFQjCNEt3iULBQ4EkdcmwT1fsyCzeogvaA> is a read only published website, which is substantially different to a dynamic editable tiddlywiki. The first question did not make this differentiation.
The only thing I dispute, which I expected a newbie to be mistaken is the browser back button in writable tiddlywiki. If auto-save is on and permalinks displayed this may be achievable but when a single file wiki is in use back and forward force the browser to load the whole wiki again on each action. Changes not saved will not be found after back or forward. As nice as save on every action is when you have large wikis or data tiddlers, turning off auto-save is needed, and you must manually save before leaving the page. In the examples discussed, this is clearly tiddlywiki as a website (prior to web 2.0) , I agree totally that it would be ideal if it behaves like any other website and honors the forward and back buttons as navigation tools, but surely this needs to be a static website, lest you load the whole wiki every-time? If you can set me strait on the question and issues please to so. Tony -- 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/8792c1be-5c7d-4e0c-97ba-90505cd3d2e5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
