20120407/Raskin vs Engelbart: Difference between revisions

No edit summary
No edit summary
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
I am no academic, this is just a hobbyist characterization that may only be roughly useful.
I am no academic, this is just a hobbyist characterization that may only be fun.


[[File:Toaster from zalgon on flickr.jpg|200px|left|I'm going to resist captioning this as if I was a chirpy yet caustic British guy]]
[[File:Toaster from zalgon on flickr.jpg|200px|left|I'm going to resist captioning this as if I was a chirpy yet caustic British guy]]


I met [http://en.wikipedia.org/wiki/Jef_Raskin Jef Raskin] briefly around 2000, he was giving out copies of his book [http://en.wikipedia.org/wiki/The_Humane_Interface The Humane Interface]. Raskin (who died in 2005) was one of the creators of the original Apple Macintosh, and a proponent of an appliance idea of computing. For every application, the computer interface changes to become the simplest, most straightforward representation of a particular use. So, if an app is for controlling a toaster, we pretend the computer is not a computer, but rather it's a toaster, and model those well-understood controls on the screen. To pop the toast, "click" on the on-screen lever. For every new application, an entirely use-appropriate usage model may be used. The advantage is, if you're familiar with the appliance, it's very easy to use.<br class="cleared" />
I met [http://en.wikipedia.org/wiki/Jef_Raskin Jef Raskin] briefly around 2000, he was giving out copies of his book [http://en.wikipedia.org/wiki/The_Humane_Interface The Humane Interface]. Raskin was one of the creators of the original Apple Macintosh, and a proponent of an appliance idea of computing. For every application, the computer interface changes to become the simplest, most straightforward representation of a particular use. So, if an app is for controlling a toaster, we pretend the computer is not a computer, but rather it's a toaster, and model those well-understood controls on the screen. To pop the toast, "click" on the on-screen lever. For every new application, an entirely use-appropriate usage model may be used. The advantage is, if you're familiar with the appliance, it's very easy to use.<br class="cleared" />


[[File:Toolbox by Austin and Zak on flickr.jpg|200px|left]]
[[File:Toolbox by Austin and Zak on flickr.jpg|200px|left]]


[http://en.wikipedia.org/wiki/Douglas_Engelbart Douglas Englebart] is a [http://en.wikipedia.org/wiki/Douglas_Engelbart#Career_and_accomplishments profound innovator] in technology, envisioning and creating early models of many of the most important features of modern computing decades before they became mainstream. In my interpretation of his approach, particularly after reading the excellent book [http://en.wikipedia.org/wiki/What_the_Dormouse_Said What the Dormouse Said], is that we should treat the computer as a computing device, that offers re-usable facilities across all applications. In an exaggerated Englebart toaster application, there'd be a menu option for "Operations" (common to all similar in all applications) with an option to "Pop toast." The disadvantage is, you have to learn the facilities.<br class="cleared" />
[http://en.wikipedia.org/wiki/Douglas_Engelbart Douglas Engelbart] was a [http://en.wikipedia.org/wiki/Douglas_Engelbart#Career_and_accomplishments profound contributor] to technology, envisioning and creating early models of many of the most important features of modern computing decades before they became mainstream. In my interpretation of his approach, particularly after reading the excellent book [http://en.wikipedia.org/wiki/What_the_Dormouse_Said What the Dormouse Said], is that we should treat the computer as a computing device, that offers re-usable facilities across all applications. In an exaggerated Engelbart toaster application, there'd be a menu option for "Operations" (common to all similar in all applications) with an option to "Pop toast." The disadvantage is, you have to learn the common facilities.<br class="cleared" />


If there were camps (no doubt these ideas are complementary, particularly when their developed features become common), I'd be soundly in the Englebart camp. If I'm spending so much time with it, I want my computer to be a computer, I want to learn how to consistently work with content, I want an expanding, consistent toolset that eventually offers me meta capabilities.
If there were camps (no doubt these ideas are complementary, particularly when their developed features become common), I'd be soundly in the Engelbart camp. If I'm spending so much time with it, I want my computer to be a computer, I want to learn how to consistently work with content, I want an expanding, consistent toolset that eventually offers me meta capabilities.


A good example of Raskin's approach is the iPhone. It's designed to be as simple as possible, with just one button (aside from volume). Android, on the other hand, has (with some current changes), three buttons. A home button (like the iPhone), a menu button, which consistently accesses the app's functions, a back button, used for navigation in most apps, and a search button. Granted, these buttons don't apply for every type of app, but they make apps more obvious for me, and iPhone has had to come up with some really, really inobvious workarounds (like having to double-click the button, hah hah).
A good example of Raskin's approach is the iPhone. It's designed to be as simple as possible, with just one button (aside from volume). Android, on the other hand, has (with some current changes), four buttons. A home button (like the iPhone), a menu button, which consistently accesses the app's functions, a back button, used for navigation in or between apps, and a search button. Granted, these buttons don't apply for every type of app, but they make apps more obvious for me, and iPhone has had to come up with some really, really inobvious workarounds (like having to double-click the button, hah hah).


This is also reflected in current operating environment design. For a while, we had a kind of plateau in [http://en.wikipedia.org/wiki/WIMP_(computing) WIMP] interfaces. Windows, Mac, Unix/Linux graphical interfaces all pretty much worked the same way, with the mouse, menus, toolbars, copy and paste all ready functions, very much, in my mind, in the Englebart model. Now, operating systems are struggling to merge or subsume their operation with "the touchscreen way." The result, currently, to my mind, is mess. Word, Firefox and Chrome pretty much have entirely reinvented their interfaces several times, each time it's a new puzzle game to figure out where things are. Fine for savvy people with an interest in constantly figuring things out, but leaving many other people out.
This is also reflected in current operating environment design. For a while, we had a kind of plateau in [http://en.wikipedia.org/wiki/WIMP_(computing) WIMP] interfaces. Windows, Mac, Unix/Linux graphical interfaces all pretty much worked the same way, with the mouse, menus, toolbars, copy and paste all ready functions, very much, in my mind, in the Engelbart model. Now, operating systems are struggling to merge or subsume their operation with "the touchscreen way." The result, currently, to my mind, is mess. Word, Firefox and Chrome pretty much have entirely reinvented their interfaces several times, each time it's a new puzzle game to figure out where things are. Fine for savvy people with an interest in constantly figuring things out, but leaving many other people out.


Another example is Wikipedia (and Mediawiki sites generally) vs. the typical Web 2.0 website. Wikipedia has a standard menu set that makes many people groan, because they never use "[http://en.wikipedia.org/wiki/Special:RecentChanges recent changes]," (neat to see what's going on) "[http://en.wikipedia.org/w/index.php?title=Facebook&action=history history]" (pretty essential to understand the progression and current state of a page), or "[http://en.wikipedia.org/wiki/Talk:Facebook talk]," where you can see the formulations, controversies, and subjective content about a topic, as well as the personalities behind their development.
Another example is Wikipedia (and Mediawiki sites generally) vs. the typical Web 2.0 website. Wikipedia has a standard menu set that makes many people groan, because they never use "[http://en.wikipedia.org/wiki/Special:RecentChanges recent changes]," (neat to see what's going on) "[http://en.wikipedia.org/w/index.php?title=Facebook&action=history history]" (pretty essential to understand the progression and current state of a page), or "[http://en.wikipedia.org/wiki/Talk:Facebook talk]," where you can see the formulations, controversies, and subjective content about a topic, as well as the personalities behind their development.


The Web 2.0 website is as simple as possible. It has a logo in a large font, a search in the middle of the screen, maybe a few items of category below that, all in primary colours. The user is there for one thing, though there's probably a programming interface.
The contrasting Web 2.0 (not a perfect category) website is as simple as possible. It has a logo in a large font, a search in the middle of the screen, maybe a few items of category below that, all in primary colours. The user is there for one thing, though there's probably a programming interface.


I don't really like divided worlds, and there tends to be a large chasm between these approaches. We spend so much time with computers, I think it's reasonable for most people to learn a few common operations. Sure, a child can learn to use some iPhone operations intuitively, but once you get past that subset, they have to get into learning things, and a lot of things get left behind when oversimplified (as an example, the iPhone had a lot of catching up to do when Apple realized people wanted to run more than one app at once). Is "digital literacy," which increasingly affects individuals ability to interact with the world, expressed best by an iPhone, or a reusable toolset built on the facts of computing? I think the latter.
I don't really like divided worlds, and there tends to be a large chasm between these approaches. We spend so much time with computers, I think it's reasonable for most people to learn a few common operations. Sure, a child can learn to use some iPhone operations intuitively, but once you get past that subset, they have to get into learning things, and a lot of things get left behind when oversimplified (as an example, the iPhone had a lot of catching up to do when Apple realized people wanted to run more than one app at once). Although interface will continue to evolve, sometimes it feels like there's change for the sake of change, or simply half baked ideas. Is the mindset of "digital literacy," which increasingly affects individuals ability to interact with the world, expressed best by an iPhone, or a reusable toolset built on the facts of computing? I think the latter.


{{Blikied|April 7, 2012}}
{{Blikied|April 7, 2012}}

Latest revision as of 18:29, 27 July 2013

I am no academic, this is just a hobbyist characterization that may only be fun.

I'm going to resist captioning this as if I was a chirpy yet caustic British guy

I met Jef Raskin briefly around 2000, he was giving out copies of his book The Humane Interface. Raskin was one of the creators of the original Apple Macintosh, and a proponent of an appliance idea of computing. For every application, the computer interface changes to become the simplest, most straightforward representation of a particular use. So, if an app is for controlling a toaster, we pretend the computer is not a computer, but rather it's a toaster, and model those well-understood controls on the screen. To pop the toast, "click" on the on-screen lever. For every new application, an entirely use-appropriate usage model may be used. The advantage is, if you're familiar with the appliance, it's very easy to use.

Toolbox by Austin and Zak on flickr.jpg

Douglas Engelbart was a profound contributor to technology, envisioning and creating early models of many of the most important features of modern computing decades before they became mainstream. In my interpretation of his approach, particularly after reading the excellent book What the Dormouse Said, is that we should treat the computer as a computing device, that offers re-usable facilities across all applications. In an exaggerated Engelbart toaster application, there'd be a menu option for "Operations" (common to all similar in all applications) with an option to "Pop toast." The disadvantage is, you have to learn the common facilities.

If there were camps (no doubt these ideas are complementary, particularly when their developed features become common), I'd be soundly in the Engelbart camp. If I'm spending so much time with it, I want my computer to be a computer, I want to learn how to consistently work with content, I want an expanding, consistent toolset that eventually offers me meta capabilities.

A good example of Raskin's approach is the iPhone. It's designed to be as simple as possible, with just one button (aside from volume). Android, on the other hand, has (with some current changes), four buttons. A home button (like the iPhone), a menu button, which consistently accesses the app's functions, a back button, used for navigation in or between apps, and a search button. Granted, these buttons don't apply for every type of app, but they make apps more obvious for me, and iPhone has had to come up with some really, really inobvious workarounds (like having to double-click the button, hah hah).

This is also reflected in current operating environment design. For a while, we had a kind of plateau in WIMP interfaces. Windows, Mac, Unix/Linux graphical interfaces all pretty much worked the same way, with the mouse, menus, toolbars, copy and paste all ready functions, very much, in my mind, in the Engelbart model. Now, operating systems are struggling to merge or subsume their operation with "the touchscreen way." The result, currently, to my mind, is mess. Word, Firefox and Chrome pretty much have entirely reinvented their interfaces several times, each time it's a new puzzle game to figure out where things are. Fine for savvy people with an interest in constantly figuring things out, but leaving many other people out.

Another example is Wikipedia (and Mediawiki sites generally) vs. the typical Web 2.0 website. Wikipedia has a standard menu set that makes many people groan, because they never use "recent changes," (neat to see what's going on) "history" (pretty essential to understand the progression and current state of a page), or "talk," where you can see the formulations, controversies, and subjective content about a topic, as well as the personalities behind their development.

The contrasting Web 2.0 (not a perfect category) website is as simple as possible. It has a logo in a large font, a search in the middle of the screen, maybe a few items of category below that, all in primary colours. The user is there for one thing, though there's probably a programming interface.

I don't really like divided worlds, and there tends to be a large chasm between these approaches. We spend so much time with computers, I think it's reasonable for most people to learn a few common operations. Sure, a child can learn to use some iPhone operations intuitively, but once you get past that subset, they have to get into learning things, and a lot of things get left behind when oversimplified (as an example, the iPhone had a lot of catching up to do when Apple realized people wanted to run more than one app at once). Although interface will continue to evolve, sometimes it feels like there's change for the sake of change, or simply half baked ideas. Is the mindset of "digital literacy," which increasingly affects individuals ability to interact with the world, expressed best by an iPhone, or a reusable toolset built on the facts of computing? I think the latter.


Créer la version française

Error creating thumbnail: File missing
20120407/Raskin vs Engelbart


Location

Toronto


Lata Pada is a Canadian choreographer and Bharatanatyam dancer of Indian descent. Pada is the Founder and Artistic Director of Sampradaya Dance Creations, a dance Company that performs South Asian dance. She is also the Founder and Director of Sampradaya Dance Academy, a leading professional dance training institution that is the only South Asian dance school in North America affiliated with the prestigious, UK-based Imperial Society for Teachers of Dancing.Pada founded the dance company in 1990 because she wanted to showcase Bharatantyam dance as an art form throughout the world.

Pada, who attended Elphinstone College in Mumbai, trained under the gurus Kalaimamani Kalyanasundaram and Padmabhushan Kalanidhi Narayanan.Pada lives in Mississauga, near Toronto. Pada married geologist Vishnu Pada when she was 17 years old.

In 1985 Lata Pada and her family decided to take an extended vacation to India. On June 23 of that year Vishnu Pada and daughters Arti and Brinda died in the bombing of Air India Flight 182. Lata Pada was not aboard since she left on an earlier date to tour India for Bharatanatyam recitals in Bangalore and across India; Lata was in Mumbai rehearsing for her tour, while her husband and daughters stayed behind in Sudbury, Ontario because Brinda was graduating from high school; afterwards the three flew on Air India 182. Lata Pada became a spokesperson for the families of the victims. After the crash she created the dance piece "Revealed By Fire" in remembrance of the incident. Pada received a master's degree in fine arts from York University in 1997.

Pada married Hari Venkatacharya in September, 2000. Venkatacharya is an entrepreneur and was Managing Director of Nytric Business Partners and is the Immediate Past President of TiE Toronto. He also serves on the Boards of the Ontario Science Centre and Fields Institute for Research in Mathematical Sciences. They both met while founding the South Asian advisory committee at the Royal Ontario Museum in 1995, where they raised over $3 million Canadian dollars for Canada's first permanent South Asian Gallery.

In December 2008, she was made a Member of the Order of Canada for her contributions to the development of Bharatanatyam as a choreographer, teacher, dancer and artistic director, as well as for her commitment and support of the Indian community in Canada. Lata was also recently appointed as Adjunct Professor in the Graduate Faculty of Dance, York University, Toronto.


This article based on content from http://www.wikipedia.org. Original version: http://en.wikipedia.org/wiki/Lata_Pada