Hi Danielo, The way I would envision this is rather to have the cloud storage for "content tiddlers"... as the main host and then have some form of core / skelleton / app TiddlyWiki (like Taskgraph) into which you load those tiddlers via some ServerSync Plugin.
To go one step further, I'd rather see something like different "bags"... thus a number of storages from which you can pull content, which are even loaded in the background and neatly separated so as to have no name-clashes, although the displayed name would be that of the tiddler, and not some "source:// tiddler" construct. Then there'd be an indicator that for tiddler "Foo", there are, in fact, two different versions, one from source X and another from source Y. And the one from source Y even has updates that aren't yet loaded into your TiddlyWiki instance, so you can update it on-demand, compare, merge and sync back to that very store / source / bag. However, having that "TiddlyWiki" be the master seems counter-intuitive to the whole idea of having a dedicated content-store. As for me, that's the whole purpose of it. You have your content tid-by-tid up in the cloud accessible from whichever device and your individual TiddlyWiki's — whichever way they operate or look like — have one thing in common: a plugin that safely syncs changes to-and-from the server... while staying a functional TiddlyWiki "content-free" ...which can, however, optionally, be saved as a standalone backup of all content. Best wishes, Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
