> > If somebody would ask me for a blueprint of file level syncing of TW5 in a > efficient but also simple way I would suggest the following: > - keep things simple with the single file approach - over disadvantages it > has many advantages > > - on sync side A: > -- use the TW5 autosave capabilities to do not a save but an export of a > file (call it syncStatusA) that has the following contents > --- the logic to say what has changed (tiddler updated) > --- the data that changed (tiddler data) > -- the exported file will be automatically synced (if thats possible) by > the cloud service client you are using (it's possible in mine) > - on sync side B: > -- use the TW5 autosave logic to do an import (read) instead of an export > (if that's possible???) > -- look for a exported file that has also been synced in the current file > space (the syncStatusA file) and import it > -- maybe a file naming convention for the syncStatus file is neccessary & > sufficient here, but a property inside tiddlywiki describing the exact name > of the import file for the current session would do it >
When I started tiddlydrive that was my goal. Currently the project is frozen, but you can check it out at http://danielo515.github.io/TiddlyDrive4Community Basically is a single file HTML that syncs from and to google drive. Regards. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
