There is a couple of options to you...

First is The TiddlyLock plugin.  It places a a lock file on it, but as you
say, people will have to f5 to see other user's changes.

I wanted the same, and I became a guinea pig for TiddlyWeb (which is still
in beta).  A python based tiddly web server...

It works great for the needs you've described, whilst effectively (after
installation) keeping the ease of use of TiddlyWiki.

There are also ccTiddly (I think), which I don't really know.  Probably even
more.

Regards,
-Reenen

On Mon, Feb 2, 2009 at 10:38 AM, Will <[email protected]> wrote:

>
> Hello,
>
> I have searched this group and the web for a solution to this problem,
> but have so far come up with nothing. Hopefully someone can help!
>
> I would like to set up a tiddlywiki file on a local shared hard drive
> for several different users to access and work on simultaneously from
> different PCs.
>
> The obvious problem is that when more than one user has the file open
> at once, the changes of one person are all "reset" when another user
> changes a different tiddler and then saves (as the first lot of
> changes aren't yet loaded into the second user's Web browser state
> memory).
>
> I have tried the AutoRefresh script and plugin, but it doesn't seem to
> work.
>
> The only other solution I can think of is requiring each user to
> remember to hit F5 to refresh the latest copy before they edit any
> tiddlers...
>
> Can anyone give me some advice on how to get around this problem?
>
> Many many thanks!
> Kind regards
> William.
>
> >
>


-- 
o__
,_.>/ _
(_)_\(_)_______
...speed is good
_______________
I believe five out of four people have a problem with fractions.

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to