Now that we've got TiddlyWeb, we can consider the possibility of creating a serverside replica of the TiddlyWiki user interface that only relies on static HTML at the client, and doesn't require JavaScript or cookies to function.
We'll need to keep all the required state information in the page URI:
cdent questions whether this is something that one would want to do. I could have been clearer that I bought it up as something to consider, not a proposal for immediate action. Anyhow, the motivation for me is that TiddlyWiki applications often create an interface over the raw tiddlers that makes it hard for end users of the TiddlyWiki interface to jump back and forth to the generic facilities for manipulating raw tiddlers. The ability to automatically generate an equivalent static HTML app would resolve that.
We'll need to keep all the required state information in the page URI:
http://jermolene.tiddlyspace.com/static?view=HelloThere&edit=DefaultTiddlers&view=Another+TiddlerThat scheme isn't sufficient to do things like keeping track of switching tabs. We'd need something like this:
http://jermolene.tiddlyspace.com/static?view=HelloThere&tabSidebar=Recent
cdent questions whether this is something that one would want to do. I could have been clearer that I bought it up as something to consider, not a proposal for immediate action. Anyhow, the motivation for me is that TiddlyWiki applications often create an interface over the raw tiddlers that makes it hard for end users of the TiddlyWiki interface to jump back and forth to the generic facilities for manipulating raw tiddlers. The ability to automatically generate an equivalent static HTML app would resolve that.