Ticket #891 (closed enhancement: fixed)

Opened 4 years ago

Last modified 2 years ago

[TiddlyWeb] dynamically determine workspace

Reported by: FND Owned by: FND
Priority: minor Milestone:
Component: tiddlyweb Version:
Severity: low Keywords:
Cc:

Description

Currently, the TiddlyWebConfig? plugin sets a hardcoded default workspace (defaultCustomFields["server.workspace"] = "bags/common").

While this enables saving for the most basic use cases, it bypasses the recipe cascade - not only when saving, but also when loading tiddlers on demand.

It should thus be considered how the current workspace could be determined dynamically.

Change History

Changed 4 years ago by FND

  • owner changed from cdent to FND

Changed 4 years ago by FND

  • status changed from new to closed
  • resolution set to fixed

Fixed in changeset:8854.

The default workspace is set to the current recipe (determined from the TiddlyWebConfig? tiddler), using "bags/common" only as fallback.

It remains to be seen whether this is the correct thing to do (especially with regards to the hardcoded fallback value).

Changed 2 years ago by cdent

  • milestone TiddlyWeb 1.0 beta deleted

Milestone TiddlyWeb 1.0 beta deleted

Note: See TracTickets for help on using tickets.