Simon, all

Hi, it is my first time writing to this group, so I wish first, to
thank Simon B. (and everyone else who contributed) on the excellent
implementation of GTD using the TW engine.

I'm a long timer TW user, (back from 2005/06), and have tested few
GTD's implementations by now, but only lately, start using the
MonkeyGTD (Alpha 3.0 alpha r823143, in its current shape), for real
(actual) work .

Not in a regular sense, but using it on a serverside ccTiddlyWiki
(with backbone of Apache, PHP and MySQL database). I recommend to all
to use ccTiddlyWiki, but this is another story ...

Anyhow, there are only minor issues involved with running MGTD on
ccTiddly, I will write about in another message someday soon. So far -
I'm working around the limitations.

But, just lately I've stumbled across an issue in "Cleanup" tiddler,
which quite annoying, and is completely MGTD related, so thought to
ask if anyone else have encountered / not.

The Cleanup tiddler, properly displays items (tasks) that belong to
the active Realm(s), thanks to the mgtdList macro.
However, when attempting to delete the 'displayed' items, the system
attempts to delete ALL outdated items, from ALL REALMS. This is
probably, due to use of a different method to collect the tiddlers, -
with <<deleteAllTagged>> macro.
A side note, to that, is that, I had to hack the <<deleteAllTagged>>
macro, to work under ccTiddlyWiki, for deleting tiddlers from the
server, but - I leave this for another message thread.

Any idea's on fixing <<deleteAllTagged>> to consider the active Realm
(s) only ?

Thanks again, and keep up the good work.
(Marry Christmas to those that applies ;-)

Y.A.





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