Hi Danielo > When I started with tiddlyDrive project it was very clear on my mind that I did not want to create a syncAdaptor. The main reason is because the syncadaptors are focused on server side, so unless the server is running on your own machine you end up with nothing.
That's not quite right. The syncer manager runs on both the server and in the browser. On the server, the sync adaptor called filesystemadaptor handles synchronising changes to the filing system. In the browser, the sync adaptor called tiddlywebadpator handles synchronising changes to the server via HTTP requests. I'm not sure that I've followed all of the details of this discussion but it sounds like you should consider structuring your code as a sync adaptor - assuming you're saving individual tiddlers to the server? It sounds like you might also want to look at the lazy loading mechanism which allows you to serve a "skinny" tiddler without including the "text" field, which is then loaded dynamically when it is referenced. Best wishes Jeremy On Tue, Dec 2, 2014 at 1:48 PM, Tobias Beer <[email protected]> wrote: > 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. >> > > It sure involves effort to setup different TiddlyWiki environments but > that's not a pain. It's like having different computers working with files > off of, say, google drive. :) > > So, I prefer to be able to set up each device as is suitable for the > device and the workflow(s) associated with it. > > So, if you want a plugin, you would install that into your > "environment-wiki".. but not into the content store. Perhaps a "system" bag > could serve for that purpose to have a selected number of plugins load in > all environments, if desired... just like that content, but not in the same > folder. > > Anyway, thanks to the ability to manually upload tiddlers you can upload >> ANY TIDDLER and download that tiddler later in any other wiki. > > > I wouldn't have expected anything else ^_^ > > 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. > > > I understand the lazy-loading paradigm, I just wanted to point out that > there are situations when you really don't want that... so as to have full > text search available... unless you would also throw in a TiddlyDrive > search adapter. :D > > 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. > -- Jeremy Ruston mailto:[email protected] -- 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.
