I think Jeremy has some revision-handling code hiding in the Core (no?). Certainly revisions could be handled as Tiddlers, even with the same name, where the Core would just pull the latest by "modified" field, or give you an Older/Newer button a lá Apple's Time Machine by pulling the appropriately modified Tiddler and putting some indicator icon next to the title.
Notifications could be either AJAX (doable, see my AJAX plugin in Cardo), or simply let each other overwrite and save the millisecond-stamped revisions - if you use the above scheme where you keep the name the same but just sort by modification, you leave it between the users to figure it out without deleting anything. They can agree on which mod is best and mark it as "latest". I think it's best to keep it as simple as possible while allowing collaboration - you don't need it turning into SharePoint! On Friday, 24 February 2017 07:09:45 UTC-5, Arlen Beiler wrote: > > That's a start. How would you handle edit conflicts where two users can > both edit the same tiddler? How about notifying other users that an edit > was made? Where do you store the tiddlers? What mechanism do you use and > what about server side rendering? How about revision history? Those are the > main questions I am wondering right now, and maybe at some point I will > answer them. Because that is really all that needs to be done. The answers > just need to be decided, really. > > -- 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 https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/d2157331-ef66-4e53-a950-cbdb340486cf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
