|
|
||
Eitan Suez's BlogDecember 2005 ArchivesUbuntu ReviewPosted by eitan on December 14, 2005 at 11:58 AM | Permalink | Comments (7)Approximately in June or July of 2005, I started weaning myself off of my powerbook G4, and learning the Gnome environment under Ubuntu (v5.04, now v5.10). Overall, it's been a terrific experience, and it's looking like I've come here to settle down. So I thought I'd summarize my experiences, from my perspective as a Java software developer, and as a computer user in general. The GoodHere are a few things I really like in Ubuntu / Linux:
The Bad
SummaryThe main reason I switched to ubuntu is that I can now compile and launch my java apps in 1/2 to 1/3 the time it used to take me on my last laptop. I used to run a 1GHz powerbook G4. Now I run a 1.7GHz intel centrino (same amount of ram on both). That's a serious advantage. Finally, contrary the general perception, I don't compile my gnome apps or kernel. I download and install precompiled binary distributions of all my apps. I'm very satisfied with Ubuntu and in the event that you're looking for the right home, I hope this short review was helpful. An EpiphanyPosted by eitan on December 14, 2005 at 09:48 AM | Permalink | Comments (5)Everyone stands behind their favorite web browsers. Firefox definitely appears to be at the forefront. But then you come across people who prefer Camino, for example, which is a web browser that uses the Gecko layout engine but taylors its user interface to fit the MacOSX mold, so to speak. Camino indeed is pretty cool and pretty fast. If you run macosx, you should definitely check out Camino. In a similar vein, I recently (maybe two-three months ago) came across Epiphany..and i'm in love. Epiphany is to Gnome what Camino is to MacOSX: a web browser that uses Gecko but its UI uses the Gnome and GTK APIs for a user interface. Epiphany was designed to fit in on a Gnome desktop. Indeed, it is the endorsed web browser for Gnome. But that's not the reason I so love Epiphany. Epiphany's philosophy appears to be along the lines of stay out of the user's way and less is more. So, beside the fact that Epiphany has the following favorable traits:
the feature that really speaks to me is the design of its bookmark system and the way in which you can customize the browser with actions for URL handling without having to write any code. This is subtle but a most wonderful feature. Allow me to illustrate. When you launch Epiphany, you won't find two text fields at the top edge of the window: one for the URL address and another for doing the Google search. Instead you'll find a single text field where the URL address is entered. How then does one perform a Google search without having to first visit google.com? By writing a plugin. Here's how:
Now, open a new browser window and type "java" in the URL field. You'll notice that a pull down menu will appear containing the option "Google this." Selecting that option will automatically visit the google search URL, replacing that "%s" in that bookmarked url with the search string you entered in the url field. It's a dynamic bookmark. How wonderful! In my browser, I've configured four such dynamic bookmarks: google search, wikipedia search, dictionary search, and ashkelon search. So now when I'm coding I can just type in the url field: "String*" and select the 'ashkelon search' option from the Epiphany context menu, et voila: i get my ashkelon (javadoc) search results. In addition to this cool search feature, if you type a substring of the name of a bookmark in that magic url field, that bookmark will show up in the context menu as well. If you do use Gnome, I highly encourage you to give Epiphany a try. It's a stable and robust browser. But just as importantly it's well-designed. If you don't use Gnome but would like to give it a whirl, I strongly recommend the ubuntu distribution. Last note: Epiphany also works on KDE. Humane Interfaces: Setting the Record StraightPosted by eitan on December 14, 2005 at 08:20 AM | Permalink | Comments (12)Every so often I go and read the wisdom of elharo over at cafeaulait.org. So today I came across this specific entry discussing "humane" interfaces: http://www.cafeaulait.org/oldnews/news2005December7.html Here is a snippet from elharo's blog entry: "More buttons/methods does not make an object more powerful or more humane, quite the opposite in fact. Simplicity is a virtue. Smaller is better." Hearing stuff like this makes my blood boil. I am a disciple of Jef Raskin (z"l), the person who designed the first Macintosh, the author of the book "The Humane Interface" (THI). My goal in this entry is very simple: to prevent the perversion of the meaning of the word "Humane", to set the record straight. I read Raskin's THI a number of years ago, and don't have it in front of me at the moment. The claim made by elharo is simple:
That's absolute nonsense. The 100-button remotes are infinitely better. The ipod has serious usability issues. The problem was easily illustrated to me one day when I tried to teach my poor daughter to use the ipod's interface a year or two ago (she was 4 or 5 years old). The poor girl was getting so frustrated that pushing the sequence of buttons I instructed her to push did not have the desired outcome. Instead of scrolling a song list, the volume would go up! Why?? The ipod only has three or four buttons. That's not enough to express 100 different operations. So the buttons must be overloaded; they must be made modal. That is, the same button does different things in different contexts. This is precisely what you want to _avoid_ when designing a _humane_ interface. With the 100-button remote, there's no ambiguity, no context, no modality. With the 100-button remote, you don't have to remember to press a sequence of buttons in a specific order, with specific time intervals between the button presses. With the 100-button remote, the operation boils down to pressing a single button. Even better: once you've performed an operation once or twice, you've formed the habit. Doing the same operation again later would take you no time, because you now know that the second button from the left on the top row is the one you want. I have nothing against the apple ipod. it just has an in-humane interface, that's all. Why am I talking about iPods on a Java weblog? Because the same principle behind designing the interface for a remote control applies to designing humane interfaces in our software applications. elharo brought up remotes as an analogy in the context of designing interfaces for List or Array objects, stating that such a class should have a minimum of methods, and that its design was consequently better. We're all in one way or another responsible for designing interfaces. Let's make sure they're humane. If you haven't already read THI, I highly recommend you do. Here's the link: http://www.amazon.com/gp/product/0201379376/104-7232126-4081541 | ||
|
|