[UI] Squeak UI guidelines/heuristics

[Brad Fuller]

I'd like to get your ideas on compiling a list of UI guidelines or heuristics 
that Squeak developers should follow. A few have mentioned they liked the 
idea, but I'd like to hear from the whole group. Is it a dumb idea or maybe a 
good one but tough to follow through? Too tough for our first go-round? 
(which I should mention now: I think we need to find a couple of "jobs" that 
we can accomplish fairly quickly to provide some success to the group.)

If you think it's a good idea, we could discuss one at a time and when we have 
a statement that we like, we could place it on the squeak wiki on a "Squeak 
UI Guidelines" page.

As I mentioned before, there are already plenty of Squeak UI precedences set 
and maybe we could start with those that have been successful. Most of the 
successful ones are ubiquitous and thus sometimes hard to see cuz we're so 
used to them,  (for instance, the fact that you can edit what you see is a 
basic and powerful attribute of Squeak. No need to go to a special "editor" 
like a text editor or graphics editor to edit a morphic. )

We could also discuss ideas that others have had, such as Jef Raskin's Humane 
Interface, and if applicable bring them into our domain.


brad