You might consider what your exact workflow requirements are. If everyone needs to work on the same tiddler or set of tiddlers at the same time, then your options are going to be limited. I think they would be limited no matter what your application is. Even most sql based applications are going to have some issues if two people want to work on the same record at the same time. Even CVS systems designed for this sort of situation can have problems.
But if you're working collaboratively, with some people working on one part of a project, and others working on another, then you might have other options. Each person could have their own TW with their part of the project to work on and and an IncludeList that pulls in the parts others have been working on. Each person could then see the entire project whenever they refreshed, but would only have the ability to write on the parts that were in their domain of responsibility. If they wanted to change something in what someone else had written, they would need to negotiate that with the party whose responsibility it was -- which is the only polite thing to do anyways. -- Mark On Feb 2, 7:29 am, Will <[email protected]> wrote: > Hi > > thanks to all for your responses. > > Sad to hear that there may just not be a solution to this problem, > other than human-intervention... but then I can't expect full wiki > software functionality without server side scripting, can I...? :) > > Thanks again everyone. And happy tiddlying. > Will. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
