Probable Release of v1.6.7 Today
21 11 2007Since it appears that the users still experiencing the “empty window” or missing notes problem are running Leopard and have some strange mixture of preferences (particularly “Enable check spelling as you type in new windows”), I should be able to get some update out today to Tiger users at least.
I received word a short while ago from users experiencing this specific symptom, and byakkie, who thankfully took the time to experiment with all the preferences to help pin down the most likely causes, regarding the results of running an experimental build to deal with the big remaining issues. With those results, and knowing it’s Leopard-specific (those more stringent parameter requirements!) I’ll reboot into Leopard in a moment and get down to exorcising that gremlin. If it’s like the other Leopard problems encountered it should be relatively easy to find the problem, and hopefully not-too-difficult to engineer a solution.
While I had awaited word, I worked on streamlining and pruning certain aspects of the build process and decided to tackle the recurring error message on my console:
*** -[NSKeyedUnarchiver decodeObjectForKey:]: cannot decode object of class (WebView)
which is always cause for concern for developers when things go wrong that you didn’t even realize were going on! “WebView?! Since when is there a WebView in an outliner?”
So I tackled it and discovered it is part of Blocks’ software update service, which checks for new versions of Mori and displays the release notes when found. Once I linked the WebKit framework into the Blocks software update plug-in, the release notes window popped up to announce a new version! Then it had a redirect issue I had to fix (because www.apokalypsesoftware.com redirects to apokalypsesoftware.com). Then I discovered the links in the release notes weren’t pointing to the correct location. And so on.
This all leads me to one conclusion: you folks are hard-core Mori users! Do you Fred Flintstone your way to work? Do you eat stale bread? Do you really love Mori’s features so much that you’ve been willing to put up with the broken stuff for so long? (And just what Mori features are you particularly fond of? I’d like to intensify that experience for you!) It’s just a more pleasant experience when the software does things for you like it should. Wow!
Well, while I am half-joking, I am truly impressed and grateful that you’ve been willing to endure some inconvenient obstacles just for the productivity that you gain with Mori. Thank you so much! I plan to continue fixing these annoyances as features are added, so that you find there’s more that can be done by Mori and less roadblocks it puts in your way.
Anyway, now on to Leopard and that fix!
thanks for your hard work. i’ve got the leopard box on my desk, waiting for a stable release of mori. i rely on your software, and waiting until it’s ready to go is worthwhile for me and my workflow. a few weeks of waiting isn’t that big of a deal.
Yikes! You’re waiting until Mori runs on Leopard before you’ll install it? Don’t let Apple hear you say that! Especially since they’re getting Bento ready to launch. (Of which I have more to write once the dust settles.)
Hard-corde Mori users? Well, if you must know: I hate it. I loved Hog Bay Notebook and had thousands of notes in it when Jesse dicontinued it. It still had severe (if rare) bugs in its file format and just doesn’t scale to 4500 entries. So I use Mori. And curse daily about keyboard and focus issues.
I’m glad you’re able to express your frustration with Mori. And I see that you’ve been quite particular in what it is about Mori you’re discontent with. And I share your unhappiness with many of the same navigation and interface issues…albeit perhaps a tad less intensely.
You’re an excellent candidate to try out Mori v1.7. It will be the version focusing on usability and navigation. So if you’re pleased with the result, it may be the ideal work environment many users have patiently waited for. I’ll be in touch.
I was pretty worried when Jesse sold Mori to you. I have seen that happen too many times over the years and it rarely turns out for the best. I was considering looking around for something to replace Mori, but seeing your dedication has made me decide to wait a bit longer.
Time to test out version 1.6.7 and see if it was worth the wait.
I started on Mori about 6 weeks ago, using it for GTD. I had been looking for a suitable app for several months when I came across Jim Harrison’s ‘MoriGTD’ page. I haven’t found the flexibility I wanted in any of the apps written for GTD (scriptability, in particular). I’m still on 1.6.3, and will stay there until the dust settles (and won’t move to Leopard for quite some time).
I’m really happy seeing you make progress!
I purchased HogBay, I purchased Mori. It was my second brain under 10.4. It still is under 10.5 but now face issues (moving several entries into another folder can crash Mori, I can get a frozen keyboard aso). I purchased OmniOutliner but put it away after a few hours. I like Mori more, in particular the automatic created/modified columns which can be sorted.
I recognize with some relief that development is still going on and want to emphasize this. Once I get back the old stability under Leopard I will purchase a third time - promised.
Is this v1.6.7 that’s exhibiting those bugs?
Also, I invite you to participate in our forums and report bugs in the tracking system so the community is sure to know what’s been taken care of.
No, it was 1.6.5. I’ll check with 1.6.7. for the move-many-command-key-selected-items issue and come back in the forum if it can be reproduced. Thanks for your effort.
BTW: Bento mentioned above is no substitute for Mori.