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. >> >
> I don't understand this part, could you please elaborate what do you mean > with "content tiddlers" ? > I was separating the TiddlyWiki as a setup of plugins, themes, languages, etc... from the actual content it is to contain, eventually, which at some point better be something else than just "TiddlyWiki"... e.g. my tasks, my notes, my project, my references, my bookmarks... 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. >> > > Does the folders fits this? Maybe we can save to which folder a tiddler is > saved via some custom field like gas_folder. Anyway, the file ID identifies > that particular tiddler unequivocally > Not necessarily folders, I was actually even thinking of a setup with possibly a number of different servers to talk to. But folders would also be interesting, although sharing the same server configuration... and thus more appropriately what in TiddlyWeb are bags. But yes, I was indeed talking of even tieing different servers together in one multi-server-capable-sync module. > 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. >> > > Unless the merge and compare thing this is also possible. Let me know if > you think something different. > I wasn't (yet) talking of anything automated, just as simple side by side view and manual editing :) 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. >> > > I don't understand the first sentence. There is no "master" tiddlywiki. I > just want to provide the ability to sync your wiki to a server without > loosing the option to save that content on your own wiki. That is something > that drives me crazy about syncadaptors and every other implementation of > tiddlywiki. You have to choose between being 100% online or be 100% > offline, there is nothing halfway. > :) I see how you wish to just work offline, go back online and do some syncing, updating, merging. However, I was thinking in terms of not storing the entire wiki but only that which is considered actual content... not setup stuff, like themes or plugins or whatever... although, you could do that but it would just clutter the content with setup stuff. Of course, content can be tied to plugins, but that would mean that you'd have to install those plugins into every TiddlyWiki that is to pull that content from server(s)... and that's not always practical. For example, you could have some slim mobile client that poorly handles plugins x y and z, so you'd chose a slimmed down version of TiddlyWiki and, however, that magic multi-server-sync-adapter... which also allows you to simply edit offline... but in a simplified, a different setup. Another workflow could be to have a presentational wiki be readonly and using the server-sync-adapter only to actually pull content (full, not lazy) ...while you'd have an editing environment with plugins and other tools to actually create the content that is going to be available on your presentational wiki once synced to the server. 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.
