Responding to jon
jon suggests some refactoring:
Given that the vast majority of this functionality is only useful in an online situation I would think that one option for the refactoring is to factor the useful code out of TiddlyWiki plugins and instead make javascript libraries that are loaded and used as needed either in the frontpage or backstage.
This seems like a good idea.
jon suggests some refactoring:
To do things such as login, register and logout 9 TiddlySpace plugins had to be added, including a javascript wrapper file to define some of the TiddlyWiki/Space environment
My immediate thoughts on this are some refactoring is in order as it is likely that many other spas will want to make use of the login/registration
Given that the vast majority of this functionality is only useful in an online situation I would think that one option for the refactoring is to factor the useful code out of TiddlyWiki plugins and instead make javascript libraries that are loaded and used as needed either in the frontpage or backstage.
My thought it as follows... on first registering a space, the default tiddlers should be a new tiddler and a GettingStarted tiddler so that a person can make a note straight away and see the immediate value.
This seems like a good idea.