On Jan 12, 12:16 am, Amzg <[email protected]> wrote: > The question posed is a very important one, from a user and usability > perspective IMO. > Maybe TiddlyWeb (and the other related) are aimed to deal with this? > For one thing, I believe ccTiddly would be a possible solution. Agree that a wiki with a server-side would be better suited but that route has been investigated and, as mentioned, is not currently possible.
> Like what Mr. Girard suggests; One central TW and everyone makes his/ > her changes into a copy. Additionally, this copy is set up so that its > timeline is refreshed continuously from the central TW at some > periodic time interval. Maybe plugins like Mr.Shulmans > LoadTiddlersPlugin, or ExportTiddlersPlugin plus Mr.Borkowskis > AutoRefreshPlugin could be used, with the latter autorefreshing the > sidebar-lists thus. This way, I figure, each user gets force fed with > an updated listing ensuring it is at least a recent edition. I can see that might work with a small group and a relatively small wiki but I suspect the overheads would be too high with a larger wiki and group of people, and you still seem to run the risk of people's changes being accidentally overwritten. > (If the above is possible perhaps a primitive plugin could deal with > the following potential solution: > Now, if the user is about to save, maybe it's possible to have > something comparing the "last modified" time, i.e; > Say, tiddler A has a "last modified time" at 1 o'clock. This is stored > at t1 > You open A to edit. > Meanwhile, there is a sync (as described above) with the central TW. > Now, as you wish to save tiddler A, t1 is compared to the "last > modified time" for A. > If A has a *new* "last modified time", this means someone else has > saved a new copy of A, and you're informed about it - and perhaps with > the option of opening the latest A to apply your intended changes to > it, or maybe you can save your version as A(1) etc... > ) Thanks for the ideas. I still think that TIddlyLockPlugin on one central wiki, then devising some kind of warning where a tiddler is being edited 'offline' would be simplest and minimise risks of accidental overwrites though. Regards Jonathan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
