TiddlyWiki has a special place in TiddlySpace. For the vast majority of users it is the primary interface for reading, writing and otherwise using tiddlers. It is, however, only one of several interfaces, and over time there will be more (e.g. things like dash, dashboard and TiddlyWiki5 will eventually be mature enough to be important parts).
As the developers of TiddlySpace we need to insure that TiddlyWiki continues to work well (or better) and takes advantage of the tiddler ecosystem that TiddlySpace provides while at the same time doesn't damage the ecosystem. There are several conflicting issues which need to be resolved:
In general I would like to see the server provide a three different types of TiddlyWiki:
Enabling that functionality will then allow us to identify and categorize bugs and missing features and do the right work in the right place.
Plugins which may not make sense when "unplugged" (some of these may not make any sense any more):
As the developers of TiddlySpace we need to insure that TiddlyWiki continues to work well (or better) and takes advantage of the tiddler ecosystem that TiddlySpace provides while at the same time doesn't damage the ecosystem. There are several conflicting issues which need to be resolved:
- A downloaded TiddlyWiki includes a fair bit of code that is only needed if fully online. This is redundant and causes spurious errors both in the client and on the server.
- An online TiddlyWiki includes some TiddlySpace administrative code that would be better served as external code. A migration (to /_space and /_account) has started, but that stuff is still wrapped in the backstage handling. which leads to:
- The TiddlyWiki backstage should be a separate thing from the TiddlySpace backstage. Anything in the TiddlyWiki backstage that is actually for TiddlySpace, should be in the UniversalBackstage.
-
/_tiddlywikimakes more effective use of server resources while providing a snappier response for using TiddlyWiki when connected to the server. We should complete it and integrate it. - The most common bug when trying to use random TiddlyWiki plugins on TiddlySpace is the result of calls to
saveTiddlerwithoutconfig.defaultCustomFieldsbeing merged into the fields of the being saved tiddler. We might consider changing this. It turns out it has been but the change may be incomplete. This is because: - We want TiddlyWiki to behave effectively and how a TiddlyWiki user would expect, whatever the context. To that end:
- We need to protect the current TiddlyWiki when another TiddlyWiki is imported into it. This means rejecting known bad tiddlers and highlighting those which pmario calls "alien shadows".
- It needs to be easy to identify the online functionality which is required (e.g. TiddlyWebAdaptor) versus the online functionality which is there for establishing an environment (e.g. following etc).
In general I would like to see the server provide a three different types of TiddlyWiki:
- by default something like
/_tiddlywiki - optionally (via ServerSettings) TiddlyWiki + online plugins, filled on the server (the traditional serialization)
- a download version which is clear of extra stuff
Enabling that functionality will then allow us to identify and categorize bugs and missing features and do the right work in the right place.
Notes on getting rid of redundancies
- If you click download from a space that has a different index (via ServerSettings) it doesn't work, should use tiddlers.wiki as the link there.
- A download wiki should not load backstage.js
- A file: wiki should not try to do following
Plugins which may not make sense when "unplugged" (some of these may not make any sense any more):