Hello,

I found a solution for using the TiddlyLock plugin in the monkeyGTD.
It requires changes in the source code, but seems to be working pretty
fine. If someone is interested, I can share the required code changes.

Kind regards,
Jordi.


On Nov 12, 10:43 am, Jordi Ballester Alomar
<[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have started to test using the monkeyGTD to process actions for my
> team. We act as 'one' with respect to other teams in a project, and so
> I considered that the GTD method should apply.
>
> We put the html in a shared folder. After some use, we realized that
> we could not make changes concurrently. Then I found the TiddlyLock
> plugin (http://minormania.com/tiddlylock/tiddlylock.html), which
> should lock and unlock the tiddlywiki as required, allowing multiple
> users to edit the Tiddlywiki without fear of overwriting other user's
> changes.
>
> I have imported the TiddlyLock plugin into the monkeyGTD, and found
> that it works well whenever I'm editting an action or project. I mean,
> when I double click on a tiddler to edit it, the system will lock the
> mGTD with my user, and will prevent changes being made in the mGTD by
> other users.
>
> However, whenever I would expect that whenever I'm creating new
> actions, projects, ticklers or reference items, the application should
> automatically lock the file, or show an error message if it was
> unlocked.
>
> I wonder if it would be possible to adapt the mGTD in order to
> integrate smoothy with the TiddlyLock plugin? I expect that it would
> really have a big impact for my team!
>
> Thank you very much!!
>
> Jordi Ballester.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GTD 
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/GTD-TiddlyWiki?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to