Who needs the New York Times crosswords when I have someone like you to toss me puzzles :-)

As it turns out, this wasn't as difficult as I anticipated. I didn't realize this until just recently that the GyroQ.ini file is actually a very straightforward text file that you could copy/paste from directly for backups. This also makes it relatively straightforward to import into GyroQ.

This actually will be very handy for me as I'm constantly voting off old tags and need to back them up. I can also see it being modified to act as a utility to look for tag duplications - -people with an old version that is superceding a newly installed version.

http://wiki.activityowner.com/index.php?title=GyroQReader.mmbas

The one place the new macro probably isn't complete or entirely correct is in all the hex code conversions.

>
That's why I took out the triangle icon :). So I made the following concessions (prior to the explicit context feature you recently posted)
1. Use the disappearing act (e.g. "Check oil [@home today!]).
2. Relied on associating appropriate icon to task
3. Rarely create project/result (unless I was busy & needed a placeholder) through GyroQ
a. Since project/result with its multiple tasks typically involves more thought, the addition/deletion of project/result has become a part of my weekly review
4. If I'm taking the effort to add it to my GyroQ queue, I take the extra 2-5 seconds to properly mark it up for MindReader

With the "explicit context" feature, perhaps a better approach would be to look for a context. If a context isn't found, then add the amorphous blob icon. I think finding a green slime ball might be more representative too .. heh.

1 — Substitute the right leading verb into the task
2 — Add its leading verb to mindreader.mmap using mra
3 — Realize that it is not really a next action

Having used it for awhile, it would be interesting to look back and see how many accumulated tasks don't fall into one of these categories and why. Reviewing my lists quickly I see several verbs that would be difficult to pre-assign a context to ("check", "take", "empty").

The trick is to use the new "explicit context" feature and just toss it into the task as @home, @web, etc. You can have it "disappear" from the task by putting it (and other markup) in brackets (e.g. "Check oil [@home today!]).

Your code is cleaner than mine :). I agree that 'an amorphous blob of potential undoability' should be represented & now I understand why that was added. Unfortunately, unless an AI engine is built into MindReader I think it will have a difficult time distinguishing well-formed tasks from the amorphous blob. I think I'll keep my approach but add the triangle back in. That way if I'm absent-minded enough to forget to use my common verbs in the config map then I'll know it may potentially be an amorphous blob.

Thanks,
Bill

Here's a challenge for you.

When I updated to the released 1.9.3 I lost my tags.

Any chance to write a tag that takes them out of the ini file and generates a map as a form of back up? I would like to end up with my own custom tag library map so that if I need to reinstall I can set it up the same way each time.

I am sure this would be easy for a genius such as yourself!

Cheers

The "stock" icon was added early on based on a suggestion by Hans to have it represent a "amorphous blob of potential undoability". A item with no recognized "action verb" or context that might need more GTD "processing" to translate into something that is actionable.

I added some code to make its use optional and set the default so its not used. I think that may be a cleaner approach than looking for lack of icons. I do appreciate your code suggestion though.

I uploaded new version to the wiki "development" page.

http://wiki.activityowner.com/index.php?title=MindreaderNLP-dev.mmbas

Let me know if that works for you.

In this release I set mindreader up to stay open rather than opening and closing it hidden twice for each topic. This provides some of the speed boost but I should probably check if it is worth the distraction of having it visible and left open.

I could have it be hidden, but I worried that would cause problem for folks that are actually using it (particularly at the configuration stage). Perhaps the code can check to see if it is already open and visible and choose route base on that someday.

I didn't experience any of the problems Tom listed above - nothing ended up in the config file map. GyroQ worked as expected for me - but was a MILLION times faster. The only thing is that the MindReader configuration file is left open - was that always the case? I seem to remember it closed by itself

One of the changes in this release is that instead of opening and closing the mindreader.mmap file as a hidden map. It opens it visible and leaves it open. Perhaps going back to hidden will help.

The "destination map" is the map linked to the 1st "defaultmap" entry in the mindreader.mmap configuration file. It isn't related to the destination set in GyroQ.

You can send mail to info at activityowner dot com.

Another thing I noticed (not necessarily connected to this problem) is that I can't change the destination map from the GyroQ options box. I tried changing from GyroQ daily capture to mrsample.mmap as a test, but the map does not change.

If you send me e-mail address I will send screen-shots.

Cheers,

Tom