Category: Software

I’ve finally figured out why Manila Envelope occasionally gets stuck in spinning progress bar hell. It has to do with how I handled user notification in the code.

Basically, there are three types of function involved: one gets user input, one executes a series of Manila function calls, and one wraps a SOAP call to a particular part of the Manila API. Unfortunately, I was reporting user errors via dialog boxes in all three functions in the chain.

This sequence diagram shows the problem–I was letting the Manila handler do the notification to the user. This caused timing problems in the window controller that kept it from successfully stopping the progress indicator and returning control to the user.

A little update before I go. I’ve been putting in some thought about the next version of Manila Envelope. There are some especially troubling bits about the preferences screen that will need some more thought before I can cleanly incorporate the Blogger API, but my first thoughts are here.

I got the first part of the Blogger API working in Manila Envelope. I’m starting with the prefs–there will have to be a major overhaul of the whole app to make this work, including restructuring the preferences file. But hey–I got the blogger.getusersblogs call working. Baby steps…

One problem: If you have a regular Blogger site, the API calls go to the Blogger server. If you have a Moveable Type or Radio site, do you send the API calls to the Blogger server or somewhere else?

I’ll be in and out today–I have a lot of errands to run before we head to Belgium for the weekend. I’m working on my own version of a Pictures tool for Manila Envelope. I’m really feeling the curve here… I thought about using AppleScript to hook into the Manila pictures API months ago but had difficulty making it work right.

I think I’m going to have to ask for some feedback from the users of Manila Envelope about how to proceed with incorporating the Blogger API. Look for a “survey” with some linked proposed screen shots in the next week or so.

Manila Envelope 1.0.2 is out. See the release notes. In particular, note the caution about posting to Radio sites. As noted yesterday, Manila Envelope does not post to Radio based websites. The problem is that Radio and radio.weblogs.com do not support the Manila API (a way of communicating with the website via XML). Tentative target for support of Radio is version 1.1.

I’ve had feedback from a few people who have tried to use Manila Envelope with Radio, either against their desktop website or on radio.weblogs.com. The short version is that Manila Envelope doesn’t work very well with Radio right now.

The long version is that Radio 8.0.1 doesn’t support the Manila API for SOAP calls, just the Blogger API. I didn’t start testing Radio until after its release, and just started to figure out some of the issues around the time that I did my 1.0 release.

The good news is that people had already requested the Blogger API as an option, and I’m looking at it for a future release. So this isn’t a permanent incompatibility, just a short term issue. I’m somewhat intrigued that people want to run Manila Envelope against their local Radio site; I didn’t think the Radio user interface through the browser was that bad, but I understand the desire for a consistent user interface.

Manila Envelope 1.0.1 has been released. Bugfixes, mostly, and a few new features, including importing text files and automatic translation of special characters (e.g. å, é, î, ò, ü, ç, ñ, etc.) to their HTML entity equivalents. Check out the full release notes for more details.

In doing this project, I’m continually reminded of things that I knew once and have subsequently lost. For instance, making sure that I follow a consistent process for building and publishing. I just realized that the build I made yesterday still showed 1.0A1 as the version number in the About box. As a result, I started a checklist for my build and deployment process. Our old configuration manager at AMS would be so proud…

I’ve finished all the bug fixes (that I know of) and a few surprise new features for Manila Envelope. I’ll release v. 1.0.1 tomorrow (I can’t get to my iDisk tonight).

For now, I wanted to publicly thank the folks who emailed me to report bugs and make suggestions: Nicholas Riley, Jeremy Wilker, Martin Fenner, Oliver Wrede, Clark Venable, Walter, and Peter Gallagher.

Snow falling in Boston tonight. A slow day waiting for the snow to start.

I fixed some bugs in Manila Envelope the last few days, including a dumb error with the icon this morning. I’m a very junior developer, but I’m finding that it’s difficult to get a good icon creation program. Apple ships IconComposer, which allows editing four sizes of icons. Then there’s Iconographer, which would be perfect if it would automatically scale images that were pasted into its icon windows. I had to use both to fix the icon problems I had today–the masks weren’t working very well and the icon was surrounded by a black outline at certain sizes. I will be releasing the bugfix Monday or Tuesday.

This is pretty cool: Manila Envelope got picked up by FrTracker at Bluedays Software, a software tracker in French. And the app isn’t even localized… If anyone out there wants to help me translate Manila Envelope into your language of choice, please let me know. (Hint: the biggest issue will probably be the Help file.)

I love the Mac community. The people who blog from the Mac are willing to try new things (about 171 people have downloaded my app from VersionTracker, not counting the ones who went to my site) and ready to tell you when they find bugs. I am really glad that you guys are out there–I was panicked that I had no testers, but I do now and they’re piling up the bug reports! Look for a new version soon to fix the initial bugs.

Dave asked for a screen shot for all the “Mac-impaired people” out there… so here it is.