Tinka would work if it would by default export the whole wiki with the filter [!prefix[$]] as a plugin. As Tinka stands, checking each checkbox is a too troublesome.
Here is a WikiAsPlugin approach: 1. George sets up his personal library of plugins 2. A button allows the publication of the current library to that plugin library 3. Any wiki can include another wiki as a plugin through that library The drawback would be in same-named toddlers being deleted with the deleting or even disabling of the plugin. On Friday, November 6, 2015 at 4:58:12 PM UTC+1, Tobias Beer wrote: > > Hi George, err Christopher :D > > >> George wants subwikis to be up-to-date in order to plan his activities >> transversally. >> > > Does "transversally" mean independently, simultaneously? > > GeorgeGeek will consult the sub-wiki tiddler updated from the meta-wiki >> file >> > > What exactly does George do here? > What does "updated from" mean? > > Create an WikiAsPlugin plugin. >> > > Perhaps useTinka > <https://groups.google.com/d/msg/tiddlywiki/xEZyPvDkZc0/IKaK9GpDAgAJ>? > I still haven't gotten to play more concretely with the idea of swarms > <https://groups.google.com/forum/#!topic/tiddlywiki/m6qGAjukiQs>, i.e. > more "losely defined bundles of tiddlers", plugin-like packaged. > > Exporting a wiki as a plugin will effectively allow the subwiki to be >> loaded into the meta wiki without having to restart either a node-js >> instance nor need to duplicate tiddlers in a current wiki file. >> > > Ideally, node will at some point not need restarting the server. > > >> WikiAsPlugin would mainly *have an export function*. The exported plugin >> would then replace the currently installed plugin with fresher content. >> > > Via drag+drop update? > >> >> - viewing changes to shadow tiddlers >> >> core feature => look at plugin => observe which plugin tiddlers are > overwritten > >> >> - exporting changes from shadow tiddlers on meta-wiki >> >> perhaps the right predefined-filter under "advanced search" will do to > get "all from plugin X" that are "not shadows"? > >> >> - importing changes from meta-wiki into sub-wiki >> >> Mhhh, why not edit the subwiki? > After all George, wants it packed and redistributed back to his meta wiki, > not having to figure out what overwritten shadows to eventually delete in > the Meta Wiki and when, etc. > > George, being a geek, would GIT-version the wiki-as-a-plugin and >> sychronize it with a node-js instance, etc. >> > > So he does use node, after all. Then I would perhaps recommend not to > endeavour this in-browser approach at all... but I can see how editing on a > tablet asks for a way to get those updates from in-there synced back > out-there, i.e. into node, > > The layman's approach could be: do edits and save them somewhere else, > e.g. a backlog in, say, Trello. From there, merge them into those "master > wikis" manually. > > Best wishes, > > Tobias. > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/91aa4d6a-73d4-415f-8789-9683d4f843cb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
