Hello Tobías > > 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... > > Ok. I never mentioned this but my idea is to sync only CONTENT tiddlers. This is what makes sense to me. Then a special edition of the server and a different plugin will be available for installing plugins from a repository.
> 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. > I also though about that scenario. But we have to face the fact that there con only be one tiddler with with certain title within one TW, and the server does not have that limitation. Mi idea was to have one server running and separate the wiki data based on the folder. The folder is a wiki wide configuration and affects most of the server uploads/downloads. Having one server sync is complicated, I can't even think about sync to multiple ones. Maybe I can include the option, but with any extra guarantee. > > >> > > I wasn't (yet) talking of anything automated, just as simple side by side > view and manual editing :) > Me neither. There is no automatic way to merge semantic content. > :) 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. > You are giving me opposite messages. First you said that the sync thing should not include configurations or plugins, I agree with that, but after that you wrote that it is a pain to install all the necessary plugins on every TW. Which setup would you prefer? I prefer the first one, and maybe, install plugins from the future-plugin repository when needed. Anyway, thanks to the ability to manually upload tiddlers you can upload ANY TIDDLER and download that tiddler later in any other wiki. > > 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. > That is also interesting. With lazy I mean that the content is load on-demand, but automatically. The idea is to load first the basic wiki with the basic tiddlers hard-coded into the html file. Then, the rest of the tiddlers are downloaded during the session, maybe when clicking a link to a tiddler maybe based on a queue that starts to download immediately after wiki start-up. > > 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.
