Articles from 2008
The Transparent Experiment Lives!
CrystalClear Interface 2.0 will soon enter a public beta release. This is a major step from the previous version, released in March 2008 and described in the Mars article:
Those of you who found CCI 1.9 outlandish no doubt find that version 2.0 sets a new standard for outlandishness.
This second part of my report on the iPhone application marketplace covers the class of software that, while still falling squarely in the overall eReader category, is designed primarily for storing and managing documents. The primary distinctions between this class and the one covered in Part 1 are that the eReader apps discussed here:
- Handle a wide variety of common file formats found in the workplace, rather than just text and proprietary eBook formats,
- Don't include controls for customizing fonts,
- Don't let users do full-text search on documents,
- Have good embedded browsers and follow web links,
- More easily let users move files to and from their iPhones, and
- Typically let users organize and rename files and folders within their interface.
It still surprises me how rapidly this market is evolving, and that evolution makes keeping tabs on the capabilities of each application--and even on the entire set of applications--quite challenging. As I was finalizing this report, a new application in this class came to market that, it turns out, I've found to have among the very best features of any that came before. I have no doubt that many of the applications reviewed here will continue to be refined, rendering this snapshot fairly obsolete fairly quickly. But the observations here accurately reflect the current state of iPhone eReaders.
The iPhone application marketplace now offers a tantalizing variety of tools that can be used as eBook readers and file managers. As I concluded in the September 2008 report, "Without Even Trying, Apple's iPhone Takes the eBook Reader Sweepstakes," the iPhone and iPod Touch hardware finally enables truly practical eBooks, and the software now available for the iPhone platform just clinches the deal.
Having worked with the growing number of these applications since the first started appearing in June, I've concluded that the market is clearly divided into two major objectives:
- Applications designed primarily for reading text (books), and
- Applications designed primarily for storing and managing documents.
As I compiled notes and usability data on this group of applications, it became clear that trying to cover all 19 different applications for the iPhone that can server as e-document readers in one article (a 20th was released just as I was finalizing this report) would be a bit much--for me as well as for readers. As a result, this will be the first of two installments of the overall report. (Note: All of these applications, with one exception, work equally well on both the iPhone and iPod Touch. For simplicity and brevity, I'll use "iPhone" to refer to both devices going forward.)
This first part covers the following iPhone applications, which are primarily aimed at reading text and HTML documents:
The second installment will cover applications that specialize in enabling document repositories on the iPhone: Air Sharing, Annotater, Caravan, DataCase, File Magnet, Files, Folders, iStorage, Mobile Finder, TextGuru, and TouchFS.
Extending these to more difficult lines of inquiry, it's clear that changes in earth's atmosphere are causing global temperatures to rise, for the Arctic ice cap to melt, for glaciers around the world to disappear, and for the incidence of hurricanes and droughts to increase. These are facts, and nearly all scientists today agree that the inference from these facts is that Global Warming is a fact. It is the truth, even if it's extremely inconvenient.
I recently decided it was time to look again at the state-of-the-art in eBook reader hardware. It seems like I've waited forever for a company to design one I could really use in place of the traditional paper-filled parallelepiped. I first got excited by the possibility while implementing the PDF format for a magazine on CD-ROM back in 1995. "Wow!," I thought, "Whoever wrestles PDF onto a small electronic device is going to make a mint!"
Of course, PDF turned out to be not particularly well suited to small viewing screens, since publishers would have to make a special layout for the PDF version. And so, years went by, with talk of E-Ink, electrowetting, electronic paper, and other exotic technologies appearing to be on the verge of practicality.
What most of the would-be designers of eBook readers have seemingly failed to grasp, however, is that to replace paper books, eBooks must be nearly as light and portable as a paperback. They must work without cords, and be compatible companions to one's daily trip to the little boy's room. (I've honestly never met a woman who reads in the john, but it seems nearly all men do.) They must be able to accompany you to the beach, the pool, or the mountains. I'd really like something I could read while holding it in one hand, like I do a paperback. I don't want a reader that will break the bank, either. And most of all, an eBook reader needs to be comfortable to use in bed or in your favorite armchair.
Even today, with devices shrinking towards the ideal size and weight, nearly all fail to meet my needs for one reason or another. Quite surprisingly, one device has in fact replaced books for me, and it's not one I ever thought would or could. Because I had bought the device for another purpose entirely, this eBook reader has actually cost me nothing whatsoever.
This article covers five eBook reader devices, including two that are full-fledged personal computers serving as an eBook reader by way of third-party software, and another that is a multifunction "smart phone" with eBook reader capabilities. All five devices have strongly positive characteristics, and two of of them possess the full range that would allow them to serve as portable eBook readers for organizations that need access to technical and policy documentation. Even though I personally need a reader that's useful for novels and such, I'm evaluating these based on their utility as devices for storing and reading technical and other documentation rather than literature, each of which have quite different requirements for eBook reading.
That this overwhelming trend toward advanced, desktop-like applications has happened at all is the result of the efforts of determined developers from the Mozilla project, which rose from the ashes of Netscape's demise to create the small, light, powerful and popular Firefox browser. The activity of the Mozilla group spurred innovation from other browser makers and eventually forced a trend towards open standards that made the emergence of Ajax possible.
This article starts with a brief history of web browsers and then jumps into a look at the feature set of the four primary "modern" web browsers in 2008. The comparison of browser features begins by listing the core features that all these browsers have in common. The bulk of the article lists in detail "special features" of each browser and each browser's good and bad points, as they relate to the core browser characteristics. Following that, I present some recent data on the comparative performance of these browsers. The article concludes with recommendations I would make to organizations interested in making the switch from IE6 in 2008.
Looking back,This is an update to the article I wrote last summer, when Safari 3.0 was first released. In the 9 months since then, a lot has happened, and I wanted to try to keep this info up to date. Opera, iCab, Konqueror, and Firefox have all made progress in adopting CSS 3.0 specifications, the next generation of the W3C's Cascading Style Sheets standard.
However, the WebKit team continues to lead the pack, as they have since I first contemplated this article over a year ago. In the last 6 months, that team has not only adopted more of the CSS 3.0 specs ahead of the others, but they have proposed several exciting new specs of their own, which the W3C is taking up as draft recommendations.
In addition to updating the state of CSS 3.0 in WebKit/Safari, I've also added some new demos for the Backgrounds section.
Here are the CSS 3.0 features I wrote about in July 2007:
- Box-shadow: Yes! Add drop shadows through CSS!
- Multi-column layout: Can we really do this now? With HTML?
- Rounded corners: Any can be made round.
- Colors with transparency: There goes another ugly hack from way back!
- Background image controls: Remember how great it was when you could add images as well as colors to an element's background CSS style? Well, it's about to get a whole lot better!
And since then, WebKit and Safari 3.1 have adopted the following new ones:
- Adopted last October, WebKit introduced its first take at CSS Transforms, which it has submitted to the W3C for consideration. With CSS Transforms,
- Announced at the same time is the equally exciting implementation of CSS Animations. At the moment, the only type of animation that's documented and demonstrated on the WebKit blog is based on CSS Transitions, which let you define how an object or attribute changes over time from one state to another.
- Also in October, WebKit added the CSS Web Fonts feature, which lets designers beam fonts to users through CSS and HTML, approximating the capabilities of PDF in a much lighter-weight form.
- Then, after a lull, things started to heat up again last month, when Apple released Safari 3.1. Safari 3.1 incorporated all of the CSS 3.0 features WebKit had pioneered earlier, plus it added a bunch of things the WebKit team hadn't blogged about. Chief among these was support for CSS Attribute Selectors. This is something of a holy grail to advanced web developers, since it opens up a whole world of possibilities for using the Document Object Model (DOM) to build better web interfaces. When released, WebKit was the first and only browser to support this geeky, but highly practical feature.
- And then, just today, WebKit added support for CSS Gradients to its portfolio. Gradients are not yet a CSS 3.0 specification, but they are part of the HTML 5.0 spec. No doubt Apple's implementation will be referred to the W3C for consideration.
This release fixes a problem with the uninstaller, and is otherwise the same as 1.9.0. (Note: Today’s update fixes the error in yesterday’s release, which inadvertently still had the 1.9.0 installer. Sorry about that!) The uninstaller now runs a new utility, GraphicsToggle, after running the installer/uninstaller, and this takes care of making sure the Leopard graphics are fully restored. See the documentation included with the download for more information about GraphicsToggle.
This unexpected journey into the realm of transparent user interfaces has taken me much further than I ever imagined. It's been almost a year now since the first inkling of the idea rattled my brain, which led to the first release of Crystal Clear for ShapeShifter in mid-February.
Thanks to the Cocoa InputManager SetAlphaValue, I was led, Pied-Piper-like, into the enormous and strange world of Objective-C and Cocoa during the summer. I'm finally surfacing from that expedition and have brought a souvenir of my travels into the strange, terrifying, and glorious realm of Cocoa.
Each computer user will have to decide for themselves just how much transparency they can stand while working at their Mac. I was surprised at the amount of loathing that was expressed towards Leopard's newly translucent menubar last month. But I don't think it's indicative of any permanent flaw in the concept. Quite the contrary, in fact: If anything, Leopard's toying with translucency is too much of a baby step, on the one hand, and smacks of me-tooism with Vista, on the other.
Very briefly, the premise I'm proposing is that our computer monitors are essentially glorious light sources, much like the ones that shine through windows in our houses and automobiles. Just as we do with those windows, there are times when we want to bask in the beauty shining through, and other times that we prefer to close the blinds to avoid glare. On the computer, we already know how to close the blinds. I'm suggesting that there's a world of beauty awaiting computer users who can enjoy the light as well.