Some different approaches include
- a package of tiddlers in one wiki which you can see in an iframe, you can drag from the iframed wiki to the current one to install
- My recently mentioned use of bookmarklets.
The issue about “injecting” is you can do it by editing the html file, perhaps even easier now the tiddlers are stored in JSON, however if someone has the wiki open they may not see the file update and save back over it without keeping the injected tiddlers.
- One approach I considered was use autosave on the wiki, then once saved start a timer eg 30seconds. Once the 30seconds has passed make the wiki read only so to use it you must reload from disk, and thus catch the tiddlers injected by another process. Or some version there of.
- Another may be only inject tiddlers at midnight, and save and lock the wiki from saving at midnight, forcing a reload before use.
There are a subset of cases where just loading the “scheduled for injection tiddlers” at open of the wiki for interactive use is feasible, like you are importing content over time and no one else needs to see the “scheduled for injection tiddlers” until the owner opens it interactivly and imports them.
- This method would benefit from code that detects and input JSON exists and imports its tiddler.
- This allows the owner to curate injected tiddlers, but is otherwise automated.
It would be great if we could get a way to message a running wiki to tell it what to do if someone is currently using it interactively. Eg Save a logout, or load tiddlers etc…