Hey thanks. I'm writing an end-user manual for TW so this information is very welcome. I will update the community wiki when i get around to it.
Okay but here is the scenario: - I import a plugin from tiddlytools.com and have it be linked to the source - I then remove a tag. - the plugin at tiddytools.com gets a version upgrade Now I go to the sync dialog. I select the plugin and click "sync". What happens? Does the sync look at modification date and only imports when the modification date of "remote" is newer than "local"? And in the case of the other adaptors, is the newest version retained? Haha, I did a test case. This is really weak. The sync tries to push my modified plugin back to tiddlytools.com, but fails, because there is no si.adaptor.putTiddler defined on that adaptor. -------- It would be really helpful if: - a source could identify itself as authoritative (no trying to push no matter how changed it is on the local) - the sync would take account of the adaptor being used, and not try to push or propose to push when that adaptor is being used This would mean that local tiddlers that are newer than remote tiddlers are either a) unselectable (grayed out) b) not selected by default c) either (a) or (b) and tagged "no push possible" It would also be helpful if the mechanism would take account of tiddler::Version slices when present on tiddlers both local and remote. These versions would have to be displayed in their own columns in the table. (Not a necessity per se). The "Synchronization status" field would indicate "new version available" and the version difference would take preference over the modification date. If version were the same, then modification date would take effect but the tiddler would be tagged "no push possible" There would be an "action" column in the table that showed what was going to happen upon sync. - pushing local changes / update remote - getting remote changes / update local - no push possible / cannot update remote An authoritative remote would only be able to have "update local" and "cannot update remote". The same would be true of the FileAdaptor. If a new version were available at the remote source, it is likely that it would also have a newer modification date, but not per se. Local changes would be lost. A minor use case scenario at best except if some automatic versioning system were used. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
