blogs

I've always assumed that feature request and bug tracking was a good idea, but after reading this article I'm not so sure.

The basic problem with feature request / bug tracking in my experience is that the requests come in faster then I can work. The list seemed manageable at first, but over time it just gets longer and longer. I added voting to so I would know what features where most important, but votes also grow over time so it doesn't really solve the problem. The end result is that right now I've got a really long list of requests and just thinking about it is a bit depressing.

I'm considering selling Mori to another developer. So far I've received interest from a number of developers, but all talks are still in the exploratory phase. I think the chances of this actually going through are around 50%, but in the spirit of openness I'm posting here to let Mori users know what's going on.

The reasons for considering a sale are that I want more time to focus on some new projects, but I don't want to put Mori on a back-burner and forget about it. So the simplest way to solve this problem is to find some other developer who will take over Mori's development.

Other possibilities are:

johnzeratsky.com - Getting things done with Mori

Time for some news.

First look on this site tomorrow for the release of Mori 1.6. Version 1.6 adds tagging support and a bunch more. Also for everyone who thinks WriteRoom is to expensive there will be a one day sale on MacUpdate tomorrow. Click here to find out more. (url might not point to WriteRoom sale until tomorrow).

Bigger news is that in about 2 weeks I'll be coming back to work on Hog Bay Software full time again. It's been about 16 months that I've been part time, and I'm looking forward to coming back. With that in mind I'm trying to step back a bit and figure out what my goals will be now that I'll be back full time.

Two new write-ups on using Mori for the David Allen's Getting Things Done (GTD) appeared this week. They are both good intros to GTD and just good intros to the various ways that you can use Mori. If you have a few minutes I'd recommend checking them both out.

First Jeff has posted a screen-cast that documents a basic Mori GTD process, and also gives a nice tutorial of Mori in the process. The method he describes can be extended with his mGTD plugin which he plans to document in a later screen-cast. Thank you!

I've just released Mori 1.5, but be warned it's a pretty small release. The changes will certainly be welcome for some people, but I didn't add any of the big ticket requests this time around. This release is mostly a grab bag of lots of little features that I've added along the way as I was focusing mostly on WriteRoom. Next time around (Mori 1.6) I hope to have more exciting features to show off.

This might be a bad idea, but it's stuck in my head. I'd love to hear what others think and for people to help me make it a reality.

What would happen if you could snap your fingers and all of your favorite indie Mac developers started using the same code and company processes?

I think a lot of cool things would happen for both Mac user and Mac developers.

For users.

Next time you wanted to buy an application it would be simple. You'd know the order and checkout process and wouldn't have to poke your way through yet another almost pretty good shopping cart. Once you paid you'd know exactly what would happen next, all developers would use the same smooth and tried and true registration process. Want to make a feature request or report a bug, you'd use the same process that you do for all the Mac developers, no more poking around for hidden email addresses and user forums that might be the correct place or might not.

I just got an email (thanks for letting me know) that I've been anticipating for a long, long, time. Someone's finally posted a way to get around WriteRoom's (works for Mori and Clockwork too) license scheme. Here's the link:

http://www.macserialjunkie.com/forum/viewtopic.php?t=105979&highlight=writeroom

But you'll need to sign up to see that, so here are the instructions:

Follow the steps below if you're wondering how to manually crack the program yourself:
- Right-click (a.k.a control-click) on WriteRoom and select "Show Package Contents"
- Navigate to "Contents/PlugIns/"
- Locate the file "BKLicense.plugin", right-click on it and select "Show Package Contents"

Mori's now availible for one day on MacUpdate at $24.95. Even if you don't want to buy it clicking that link and visiting the site helps me. Click!

I have a new beta for people to try out, this is version 1.4b3. This beta has less big new features then the last couple of betas, but it contains a lot of bug fixes and small refinements.

First I’ve found a workaround that now makes the smart folder rule “Note contains ...” work properly even if your note contains multiple paragraphs. For new notebooks it should just work, if you are using a notebook that you’ve created in an earlier version of Mori you should first run the Help > Check and Repair Notebook menu command, and then it should work. Unfortunately performance isn't great. I know how to improve performance for the future, but for now your best bet to speed things up is to make the "Note contains" rule the last rule in your list of smart folder rules. That way it won't have to run over so many entries since the preceding rules will narrow down the list of possible entries.