[Bf-funboard] With respect to interface simplicity
bf-funboard@blender.org
bf-funboard@blender.org
Wed, 8 Oct 2003 16:06:09 -0500
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C38DDF.FF0559B0
Content-Type: text/plain;
charset="iso-8859-1"
I couldn't agree more. It took me a long time to learn Blender, but
now that I have, I wouldn't want it any other way.
Timothy Baldridge
> ----------
> From: Jeffrey F. Cuff
> Reply To: bf-funboard@blender.org
> Sent: Monday, October 6, 2003 10:22 PM
> To: Bf-funboard@blender.org
> Subject: [Bf-funboard] With respect to interface simplicity
>
> I feel like I'm late at this party, so to break the ice and get down
> to business quickly I'll make this initial posting fairly general.
> I'm still wading thru archived postings, so it may take
> me a while to get up to speed.
>
> This first posting is a statement of what I have really liked about
> the Blender UI which I've used it since version 1.5, and I guess
> stability / consistancy counts for a lot. I'm not into change for its
> own sake.
>
> I've boiled what I like about the Blender UI down to one principle which
> I will state as the prime directive in UI design.
>
> 1. Respect the user.
>
> Blender assumes that I will spend most of my life as an experienced,
> intelligent user who knows what he's doing instead of a naive user in
> need of constant hand-holding, training wheels (used for 1 week but
> welded to the frame of the bike), and wizards (who insist on asking
> seven questions in seven different windows, when one will do).
>
> Like: assuming that if I ask the program to do something, I mean it
> (e.g. Yes, darn it, I do want to overwrite that file, not change from
> the default answer of "no" first). Like: when a window does pop up, I
> want the cursor be in it. That I will learn the meaning of a simple icon
> which can be drawn small to save screen-space (e.g plus/minus means
> zoom, I don't need a detailed picture of a magnifying glass).
>
> Respect is probably the most important UI design parameter, as it
> ramifies through the system. Ulimately, it is more important than
> "friendliness" to the new user.
>
> 2. Even-handed operation (one on trackball, one on keyboard).
>
> Crucial to efficient use of Blender. (imagine how cumbersome it would be
> to have to trundle the cursor to the menu bar and select Grab every time
> you wanted to move something instead of using Key-G) This has
> implications for hotkey assignment, as keybrd real estate is even more
> limited than screenspace.
>
> There are still a few unassigned keys on the keyboard. The core
> features, properly, got first call on the "simple" [one press] key
> functions. Before taking up the remaining ones for new features, thought
> should be given to how often the function will be used.
>
> I'd also like to see one or two keys explicitly declared off limits
> ("reserved for user"). Then in the absence of embedded macros, an
> external kbd buffer-stuffing macro program could be called into service.
>
> See "respect", above.
>
>
> 3. Uncluttered screen.
>
> e.g. Non-overlapping windows, small icons, low chrome-content. Muted and
> restrained use of colour. Named views.
>
> Having ten (related) options on one pane instead of ten.
>
> I like bars, buttons and icons, small and simple. When I'm working, I
> want to see my work, not the UI.
>
> I like the idea of auto-abbreviating the words on a button instead of
> making the button bigger... although honing the abbrevation algorithm
> might lead to more legible labels. For instance when I cram the render
> pane into a small area :
>
> 'Border' becomes 'rder';
> Gamma is "ma" and
> "Unified Renderer" is "ed Renderer"
>
> A "smarter" truncation algorithm would favour dropping
> double consonants, vowels (latter dropped first),
> split the losses in multiword lables, and try to preserve capital
> letters.
>
> Even straight-up trailing end truncation would be an improvement over
> beheading words.
>
> (oops, i didn't mean to actually make a suggestion in this post)
>
> Brdr , Gm, Unifd Rndrr much more mneumonic for a given letter count, no?
>
> See "respect", above.
>
> ***
>
>
> I think it is important be explicit about the good points (and
> principles) before making suggestions, lest an important principle be
> sacrificed for a mere feature.
>
> And though this may be late in the UI design process, I figure it's
> never a wrong time to say "you're on the right track".
> _______________________________________________
> Bf-funboard mailing list
> Bf-funboard@blender.org
> http://www.blender.org/mailman/listinfo/bf-funboard
>
>
------_=_NextPart_001_01C38DDF.FF0559B0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Bf-funboard] With respect to interface simplicity</TITLE>
</HEAD>
<BODY>
<BR>
<P> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">I couldn't agree more. It took me a long time =
to learn Blender, but now that I have, I wouldn't want it any other =
way.</FONT></P>
<P> =
<FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">Timothy Baldridge</FONT>
</P>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">----------</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">From:</FONT></B> <FONT =
SIZE=3D2 FACE=3D"Arial">Jeffrey F. Cuff</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Reply To:</FONT></B> =
<FONT SIZE=3D2 =
FACE=3D"Arial">bf-funboard@blender.org</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Sent:</FONT></B> <FONT =
SIZE=3D2 FACE=3D"Arial">Monday, October 6, 2003 10:22 PM</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">To:</FONT></B> =
<FONT SIZE=3D2 FACE=3D"Arial">Bf-funboard@blender.org</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Subject:</FONT></B> =
<FONT SIZE=3D2 =
FACE=3D"Arial">[Bf-funboard] With respect to interface =
simplicity</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">I feel like I'm late at this party, =
so to break the ice and get down</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">to business quickly I'll make this =
initial posting fairly general.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">I'm still wading thru archived =
postings, so it may take</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">me a while to get up to =
speed.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">This first posting is a statement of =
what I have really liked about </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">the Blender UI which I've used it =
since version 1.5, and I guess</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">stability / consistancy counts for a =
lot. I'm not into change for its</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">own sake.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">I've boiled what I like about the =
Blender UI down to one principle which</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">I will state as the prime directive =
in UI design.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">1. Respect the user.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">Blender assumes that I will spend =
most of my life as an experienced, </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">intelligent user who knows what he's =
doing instead of a naive user in</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">need of constant hand-holding, =
training wheels (used for 1 week but</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">welded to the frame of the bike), =
and wizards (who insist on asking</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">seven questions in seven different =
windows, when one will do). </FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">Like: assuming that if I ask the =
program to do something, I mean it</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">(e.g. Yes, darn it, I do want to =
overwrite that file, not change from</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">the default answer of "no" =
first). Like: when a window does pop up, I</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">want the cursor be in it. That I =
will learn the meaning of a simple icon</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">which can be drawn small to save =
screen-space (e.g plus/minus means</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">zoom, I don't need a detailed =
picture of a magnifying glass).</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">Respect is probably the most =
important UI design parameter, as it</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">ramifies through the system. =
Ulimately, it is more important than</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">"friendliness" to the new =
user.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">2. Even-handed operation (one on =
trackball, one on keyboard). </FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">Crucial to efficient use of Blender. =
(imagine how cumbersome it would be</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">to have to trundle the cursor to the =
menu bar and select Grab every time</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">you wanted to move something instead =
of using Key-G) This has</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">implications for hotkey assignment, =
as keybrd real estate is even more</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">limited than screenspace.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">There are still a few unassigned keys =
on the keyboard. The core</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">features, properly, got first call =
on the "simple" [one press] key</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">functions. Before taking up the =
remaining ones for new features, thought</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">should be given to how often the =
function will be used.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">I'd also like to see one or two keys =
explicitly declared off limits </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">("reserved for user"). =
Then in the absence of embedded macros, an</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">external kbd buffer-stuffing macro =
program could be called into service.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco"> </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">See "respect", =
above.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2 FACE=3D"Monaco">3. Uncluttered screen.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">e.g. Non-overlapping windows, small =
icons, low chrome-content. Muted and</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">restrained use of colour. Named =
views. </FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">Having ten (related) options on one =
pane instead of ten.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">I like bars, buttons and icons, small =
and simple. When I'm working, I</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">want to see my work, not the =
UI.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">I like the idea of auto-abbreviating =
the words on a button instead of</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">making the button bigger... although =
honing the abbrevation algorithm</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">might lead to more legible labels. =
For instance when I cram the render</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">pane into a small area :</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">'Border' becomes 'rder'; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">Gamma is "ma" and =
</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">"Unified Renderer" =
is "ed Renderer"</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">A "smarter" truncation =
algorithm would favour dropping </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">double consonants, vowels (latter =
dropped first), </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">split the losses in multiword =
lables, and try to preserve capital</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">letters. </FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">Even straight-up trailing end =
truncation would be an improvement over</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">beheading words.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">(oops, i didn't mean to actually make =
a suggestion in this post)</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">Brdr , Gm, Unifd Rndrr much more =
mneumonic for a given letter count, no?</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">See "respect", =
above.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">***</FONT>
</P>
<BR>
<P><FONT SIZE=3D2 FACE=3D"Monaco">I think it is important be explicit =
about the good points (and</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">principles) before making =
suggestions, lest an important principle be</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">sacrificed for a mere =
feature.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Monaco">And though this may be late in the UI =
design process, I figure it's</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">never a wrong time to say =
"you're on the right track".</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Monaco">_______________________________________________</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">Bf-funboard mailing list</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">Bf-funboard@blender.org</FONT>
<BR><U><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Monaco"><A =
HREF=3D"http://www.blender.org/mailman/listinfo/bf-funboard" =
TARGET=3D"_blank">http://www.blender.org/mailman/listinfo/bf-funboard</A=
></FONT></U>
</P>
<BR>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C38DDF.FF0559B0--