Archive for October 16, 2012

Tuesday, October 16, 2012

Stop Breaking The Back Button

Giles Bowkett:

Undoubtedly overkill, but the time for sacrificing basic usability to personal cleverness was the 1990s, when the Web was new and its user experience fundamentals were unknown enough to justify experimenting.

No more infinite scrolling, please. Aside from breaking the Back button, it doesn’t work well with products like Instapaper and EagleFiler.

FoldingText 1.0

Jesse Grossjean:

FoldingText combines the best of what we’ve learned from WriteRoom and TaskPaper into a new tool for plain text productivity. The foundation is a plain text outliner that uses Markdown formatting. But that’s just the start. I think the movie does a good job of showing what it’s really all about, go watch it!

Here’s the Web site. It’s Mac App Store–only, alas, but there is a demo. 1.0

Joost Schuttelaar: is the ideal tool for the casual RSS user. The app is almost invisible: It is embedded in the status menu and uses Mountain Lion’s Notification Center to alert you of new posts.

Neat idea, and a good way to get at your subscriptions that became inaccessible after Apple removed RSS support in Mountain Lion. However, Apple rejected it from the Mac App Store citing rule 2.8:

Apps that are not very useful or do not provide any lasting entertainment value may be rejected.

Rentzsch’s OpenSSL Tech Note

Jonathan Rentzsch:

Ideally the OpenSSL project would do a better job at API compatibility, but it’s really not in their unixy source-code-oriented worldview. Sure we could get big into the project to try to improve it, but we’d rather put the resources into making OS X rock harder.

Both SecTransform and lowly CommonCrypto offer API compatibility, allowing us to add functionality and fix security problems even in shipping apps, which is awesome for users.

OpenSSL is kind of a mess. SecTransform looks pretty nice. It’s becoming tempting to require Lion.

CoreGraphics, Patterns and Resolution Independence

Marcel Weiher:

With all the graphics specified using pure geometry, CoreGraphics can now do its thing and automatically handle varying device resolutions, wether it’s a retina display or a zoomable interface or even print, all without ever having to deal with the different resolutions in code. Although I haven’t tested it, the code should also use less memory, because it doesn’t create potentially large temporary bitmaps, and for the cherry on top it’s also a fraction of the code.

It’s tempting to rewrite my graphics code in his MPWDrawingContext style.