[TiddlyWeb] establish a system for managing the default server and bag for new tiddlers in a TiddlyWeb produced wiki

[cdent]

When running a TiddlyWiki with the TiddlyWebAutoSavePlugin? we need to be able to (optionally) state what the default server and default bag are for newly created Tiddlers which have not inherited such information from another tiddler.

One way to do this is to have a DefaultBag? tiddler somewhere in the Store. In the adaptor or the auto save plugin if required server.fields are not set, look in DefaultBag? for the url of a bag and calculate fields from it. If there is no url in the in the tiddler, look at its fields and use those.

Just a candidate idea. Are there better ones?

[cdent]

see  http://svn.tiddlywiki.org/Trunk/verticals/tiddlywebclient/plugins/TiddlyWebSpowtDefaulterPlugin.js for the way it is being done in spowt.

[FND]

For the initial release, the choice should be left to the user (e.g. a drop-down menu of currently active bags). More hands-on experience is needed for the final solution.

[FND]

This could be implemented as a toolbar command (automatically extending ToolbarCommands?).

[FND]

Initial efforts with TiddlyWebTiddlerSourcePlugin? (changeset:7732 ff)

[FND]

Upon further consideration, it appears that the current approach is misguided: Rather than having end-users select the source (host & bag) when creating/editing a tiddler, this decision should be made up-front by the respective document author* - usually by providing different buttons for tiddler creation (e.g. "New Private Note", "New Article" etc.).

To this end, the NewTiddler? macro might be extended to be able to read defaults from a systemServer tiddler. Also, systemServer tiddlers might need to support arbitrary fields.

* which, on initial setup, might be TiddlyWeb itself

[FND]

Server-side implementation in changeset:8014.

When creating an instance, TiddlyWeb will now create two bags, system and common, as well as a default recipe (cf.  discussion).

On the client side, a plugin needs to set defaultCustomFields accordingly:

config.defaultCustomFields = {
	"server.type": "tiddlyweb",
	"server.host": "127.0.0.1", // example
	"server.bag": "common"
};

It is currently unclear how the correct host can be determined automatically.

[cdent]

One could presumably set server.host by looking at the server.host field on some known tiddler somewhere, perhaps the adaptor plugin? I'm not sure which one would be best, but in case, there will be some tiddlers that server.host set, and digging in there somewhere should get the goods.

[FND]

One could presumably set server.host by looking at the server.host field on some known tiddler

While Jeremy would probably favor a solution based on systemServer tiddlers (see above), this sounds like a good first step.

I have just committed a simple  TiddlyWebConfig, which reads the host from its own tiddler.

[FND]

Server-side implementation in changeset:8014.
Client-side implementation in changeset:8020.

[FND]

While the components are ready, instancer still needs to be updated:

• remove TiddlyWebAutoSavePlugin?
• add  ServerSideSavingPlugin
• add  TiddlyWebConfig

[cdent]

patched, confirmed, released.

[cdent]

Milestone TiddlyWeb 1.0 beta deleted