what is going on with Mori?!

Thanks for your response, Alfonso. And it is good to hear 1.7 is on the way.

I realize that you're winging it on your own. And I can see that you're very busy with a lot of things. But as a customer and a user of Mori, I am very interested in the status of Mori. I would love to hear about the progress you're making, and your ideas and plans regarding Mori's future. My point is that there is too little of that, and too much of other stuff. Of course you decide what you do with your time and what you publish on your web site. If there's too little of what I am interested in, I will walk away.

Good luck.

Jake4891

My question for you Alfonso is one I ask myself with respect to my own position every day: is this truly what drives me to get out of bed in the morning and am I doing my very best on this project?

If the answer to both of these questions is YES, then people will just have to deal with your shortcomings. Just communicate more and don't bristle when once every three months someone asks what the progress of the project is and why updates have glaring bugs. These people are very loyal to a living, evolving product - just look back at the forum in its heyday!

If the answer to either question is NO, then action must taken.

Your choice.

It wasn't an issue about someone asking about Mori's status and its progress. As I said before, it's a valid question and one I continue to answer.

The issue was concerning his complaint (among others) that he was using Mori 1.6 because there was no progress on Mori, and then complaining that he didn't want to use the updates up to, and including, the latest Mori version (1.6.10) I released.

FWIW, Mori users are a big part of what makes me try harder to be certain the 1.7 release is worthy of their support. The same is true of Clockwork users with respect to its upgrade.

-- Alfonso

I haven't seen you post in a while. Any update on 1.7?

I'm pushing through what I expect to be the final changes to get the next Oneill release out to testers. I don't want to tip my hand to what's coming because my competitors have added useful functionality to their digital notebook apps that Mori doesn't yet have, and I don't want them to work on catching up to Mori on the new features while I'm catching up to theirs. But I want to share with you what's being developed to gain your feedback, yet you and I know that talk is talk, and I want to get this into your hands ASAP.

I also noticed this (actually, Saturday 05-17) afternoon that some users have been unable to run 1.6.10 correctly, and I'm trying to quickly determine the cause and get them back up and running the latest Mori on the latest MOX version they're running (whether Tiger or Leopard).

Something useful is coming.

Thanks for the quick response Alfonso! Carry on the good work.
1.6.10 is working fine here (OS 10.5.2), although sometimes the program hangs when quitting. But I can live with that because nothing gets lost. :)

Jake4891

While I'm glad you're not livid at the program (or me) for hanging when you quit it, I'd rather not see it hang, and it sounds like it may be a similar problem that others are experiencing where updating the search indices are involved.

Please check your console log for messages from Mori the next time it hangs (they're usually present in the logs for a day or two afterwards, so there's no specific time it needs to be checked). Hopefully I can find the real culprit here and provide a final fix for it that doesn't break something else.

I'll check the logs. Need me to send the relevant passages (pertaining to Mori) to you?

Alfonso -

We started discussing it 8 weeks ago:

http://apokalypsesoftware.com/products/node/2613

It seems to be an issue with SpotLight between 10.4 and 10.5.

Mike

This is a reply to the last couple of posts, by Rolf and alaskamike, as well as to the first post in this thread.

I'm still using Mori 1.6.9 – not because I don't want to move on to 1.6.10, but because my Mori datafile will not open and run under Mori 1.6.10.

I'm one of those users for whom Mori 1.6.8 caused my datafile to become unusable. I was relieved when I found that my file would work under 1.6.9 . . . and very concerned when 1.6.10 seemed to break it again.

A number of us reported this problem with 1.6.10 back in March (http://apokalypsesoftware.com/products/node/2613), but as of this May evening, there has not been any response from Alfonso to our posts, or even any indication that he has seen them. (In fact, his comments earlier in this thread make it seem that he has _not_ seen the posts referred to in the URL above.)

GTD is a very important part of my life. I've tried any number of other GTD apps, but there is no question about the fact that Mori/mGTD is my GTD app of choice. (I've built a 'hybrid' from the mGTD plug-in and some of the features of Jim Harrison's implementation, coupled with some AppleScripts I've written to make it work just the way I want.)

I wouldn't be honest if I didn't admit that I have a lot of anxiety and concern about having such an important part of my life resting on Mori, given its present development situation. Every time I look at the post of the issues we reported back in March and see no response from Alfonso, every time I check the blog and find nothing new about Mori 1.7 or when it might actually arrive, I ask myself 'Should I just cut my losses here and migrate to OmniFocus or ActionTastic or Things or Jesse's TaskPaper, each of which seems to have more development activity, a clearer path to the future?'

Even more to the point, I find myself thinking 'It may be great that Mori lets me have GTD pretty much the way I want now, but what happens if 1.7 doesn't fix the issues with my datafile? What would I do if my data became a permanent 'orphan'?'

I'm not the only Mori/mGTD user who feels this way. I know there are people who could be contributing to using Mori for GTD, but who are holding back, unsure of whether it's worthwhile to commit effort to this product given its current development situation.

Alfonso inherited a community of users who are predisposed to like Mori, who want it to succeed and who would be willing to help develop it. That situation seems to me a little like what politicians mean when they talk about 'political capital'. As time goes forward, some of that capital is inevitably eroded, but wise politicians try to preserve as much of that capital as they can, being very careful to burn it only on really important matters.

I hope this helps, and that Mori 1.7 is solid and stable and encourages people like BMEguy and Jim Harrison to return to developing for GTD on Mori!

--Chris

A number of us reported this problem with 1.6.10 back in March (http://apokalypsesoftware.com/products/node/2613), but as of this May evening, there has not been any response from Alfonso to our posts, or even any indication that he has seen them. (In fact, his comments earlier in this thread make it seem that he has _not_ seen the posts referred to in the URL above.)

This is close to the fact. I believe I found the posts just shortly before I wrote the above comments, and was trying to figure out how I could have missed them before. Had I been aware that 1.6.10 was completely unusable by some I would have immediately corrected and released 1.6.11.

As it is, now I've isolated the cause of the bug (throwing one or more entries into the Trash, and emptying the Trash. Workarounds are to uncheck "Allow entries to be found by Spotlight" or delete the search indices in ~/Library/Caches/Metadata/Mori/.) and written what I believe is a correction. I'm attempting to isolate a similarly show-stopping bug with regards to Smart Folders and hopefully will release 1.6.11 within a day or two.

My apologies to all affected by this bug.

You haven't found any of the later updates satisfactory for your system? Please get in touch with me via iChat, IRC or Twitter so I can correct whatever bug is preventing you from using the latest (or soon to be latest, 1.6.11).

Yes, here it seems he's still alive:

http://twitter.com/huperniketes

However he's not too comunicative with Mori's users, maybe he's just shy...

I'm just trying to get things done, and do more than just talk about getting things done…particularly when my hope is to get the release out "in a few days".

But since it's been a couple weeks since the "hang on updating search indexing" bug has been squashed, I'm preparing to release the update with or without the Smart Folder bugs (which I've been unable to reproduce in 1.6.10, let alone the new release).

Alfonso