Not so much a request for operations, more a wish list...
Assuming that
TiddlyWebWiki is being used to host multiple
TiddlyWikis, and that the End User view will only be from within
TiddlyWiki pages, the following is a list of things that would be useful from an End User perspective from within a Default Wiki:
1) A
TiddlyWebLogon TiddlyWiki macro that provides User Logon (basic)
2) A
TiddlyWebRecipeList TiddlyWiki macro that lists Recipe Names and Descriptions that are available to the current User - appended to each item should be a hyperlink to that view
TiddlyWiki3) A
TiddlyWebUser macro that allows that User or Admin to change their Password
I would anticipate that these operations use AJAX techniques, so that the content of 2) is updated by the use of 1). Just the provision of these will allow a consistent UI where Default can be used as a navigator to other Wikis without constant editing.
The provision of an Admin Wiki that can include the following functions from within the Admin Wiki:
4) A
BagAdmin TiddlyWiki macro that lists Bag Names and Descriptions and allows for the creation, update and deletion of Bags
5) A
RecipeAdmin TiddlyWiki macro that lists Recipe Name, Description, Contained Bags and Policy, and that allows for the creation, update and deletion of Recipes and the set of Roles that can access them
6) A
UserAdmin TiddlyWiki macro that lists User Name, Note, Roles and Recipes that each User can access, and that allows for the creation, modification and deletion of Users
7) A
BagImport macro that supports the import of Tiddlers from a local file
TiddlyWiki into a Bag with the option of only importing changed Tiddlers.
Most of these are already possible, but are not automatically available from within a
TiddlyWiki. I haven't thought too much about whether these should be included into
BackStage functions or be embedded into Tiddlers, but my thought is that it should be possible to administrate a
TiddlyWikiWeb site without having to open an SSH onto the server.
Number 7) would be useful as we autogenerate
TiddlyWiki files only containing the Store Div, but don't have the ability to generate deltas, so an import into an existing bag using wimport creates new versions of tiddlers unchanged apart from the created date - if the body and tags of the tiddler are unchanged it would be useful to avoid creating new revisions.
Rather more of a nice to have, because I don't think that it is a such a generic requirement is the concept of a "Template" - this would be optionally used when a new Bag is created to set the Policy for the bag, and to automatically create a Recipe of the same name. The new Recipe to include the new Bag somewhere in a predefined list of Bags and to use a predefined Policy. This would allow for automatic publishing as a Recipe as a single step triggered by Bag creation.
Matt Flower