I swear we didn’t coordinate this, but MarsEdit’s older sibling NetNewsWire also celebrates a new release, turning 3.0 today!
I’ve been using this in its pre-release form for months and am very confident about its power and stability. A really excellent update. Nice work, Brent!
MarsEdit 1.2 is now available for download (or just “Check for Updates” from the app). This is a free update for all registered MarsEdit users.
Three relatively big changes in this release:
Growl support. MarsEdit now triggers Growl notifications after publishing, refreshing, and uploading an image or file.
Picasa image uploads for Blogger.com. This is pretty transparent. Just select your Blogger blog as the upload target from Images & Files, and MarsEdit will pop the images into a MarsEdit album in your Picasa Web Albums account. Note that Picasa only accepts JPG format images for upload.
Vox support. Currently a bit limited by the Vox implementation of Atom Publishing, but a welcome start for you Vox users who are tired of blogging through the web interface. Main limitations right now are you can’t edit or delete previous posts, and you can’t upload images.
On top of that we’ve got a few smaller enhancements and fixes:
Enjoy!
This blog post was written with out pressing the keyboard or clicking the mouse! Check it out!
Here’s a movie of me “typing” the above text with Dasher, an alternative text input interface.
Thanks to Jon Wight for tipping me off to Dasher.
FastScripts 2.3.2 has been released, and contains a few very significant bug fixes:
This was easily the most difficult bug-fix release I’ve shipped yet. See the first item in the list above? Wonder why there’s a an exclamation point at the end of that sentence? Partly it’s because the feature has been requested for many years, so it’s long overdue. But mainly it’s because finally delivering this functionality puts a cap on what have been some very frustrating and difficult design changes behind the scenes with FastScripts.
All of this work, and all I get is a double-dot bug fix release?
The reason is that although FastScripts is dramatically changed by this fix, I do consider the failure to support folder aliases as a bug. It was an oversight on my part when I first designed FastScripts, and the oversight cost me dearly in the ways I decided to implement it. The short story is that the automatic syncing that goes on between your scripts, the menu display, and your keyboard shortcuts is all sort of magical. It’s a design goal of FastScripts that you should be able to do just about anything you like with your scripts: move them, edit them, delete them, add shortcuts, remove shortcuts, etc., and that FastScripts should not only keep up but keep up correctly, without requiring you to quit and relaunch the application.
Allowing folder aliases just adds to the complexity. For instance, a particular script can now be pointed to by two separate keyboard shortcuts, which reach the script via different paths through the script tree. Sounds academic, but it’s important to distinguish between these two shortcuts, because one might be a global shortcut, and the other application-specific.
The magic comes at the cost of repeated developer forehead-slapping. Enjoy :)
Update: I was sort of holding my breath hoping nothing too terrible would be discovered in this release. Well, so far nothing too terrible, but Takaaki Kato found a little issue: aliases to applications bundles no longer show the application as a launchable icon in the menu. The problem here is aliases to .app bundles are technically aliases to folders. The new feature is working too well! I will get working on a fix for this.
Update 2: Fixed in 2.3.3.
The Red Sweater Blog features updates about our apps and articles about related topics.
