A fine idea, but the challenge is "what people wants" is not a single thing.

Some want Squeak to behave like MS so it will be easier for newbies to
get started.

Others want more powerfully leveraged gestures, without apologizing
for being unconventional.

Rather than channeling energy into endless discussions trying to agree
on "one ultimate solution" that will inevitably leave the minority
unhappy (and disobedient), we may choose instead to channel it into a
proper "Squeak solution,"; flexing its dynamism to be what every
individual end-user wants it to be.  This is what I eventually did to
bring 3.9 to my taste.

A small core with one-click-loadable configurations will of course
make this a lot better in the future.  Until that time the official
base images are the starting points we have into which loaded
Universes / SqueakMap / Monticello / ChangeSet packages should be what
we use to get us to any of a thousand *destinations* (-dev, -web,
-squeakland, -tweak, -croquet, -seaside, -etc, -etcetc).


On 7/13/07, Sebastian Sastre <ssastre at seaswork.com> wrote:
> I think we can benefit a lot ourselves and other squeak users by organizing
> usability and ergonomics in some kind of system like mantis or such, so
> people knows what people wants (in regard to ergonomics and usability).
>
> The squeak mantis could be used to put under a category of "usability
> issues" (or something like that) this kind of requeriments, expressions,
> wishes?
>
> Demostrating that we are being conscious of this and we are valorating it is
> for sure a step ahead in the "smalltalk experience",
>
>         all the best,
>
> Sebastian Sastre
>
>
> > -----Mensaje original-----
> > De: squeak-dev-bounces at lists.squeakfoundation.org
> > [mailto:squeak-dev-bounces at lists.squeakfoundation.org] En
> > nombre de Todd Blanchard
> > Enviado el: Jueves, 12 de Julio de 2007 16:47
> > Para: The general-purpose Squeak developers list
> > Asunto: Ergonomics - Rant
> >
> > Since we are talking about ergonomics, I haven't done any
> > coding in modern images in some time (my production system is
> > 3.7 based) and when I started working on a fix to a minor
> > problem in the HTML parser in a very new image, I found
> > myself frustrated at every turn.
> >
> > 1) When I browse senders, I get a browser with a bunch of methods.
> > If I modify one of the methods, I DO NOT WANT IT TO VANISH
> > FROM THE BROWSER ON SAVE!  I keep having to go find the
> > freakin' thing for every edit.  STOP IT!
> >
> > 2) When I select a class in the browser, please show all the
> > methods initially in the methods pane.  What used to take 1
> > click now takes a couple.  Consider that I'm browsing up and
> > down a hierarchy looking for the level that contains the
> > implementation for a method.  It takes a couple clicks just
> > to look to see if the method is there.
> >
> > In general, the click per operation count seems to be going
> > up, while useful buttons in the browser button bar seem to be
> > vanishing (where is the one that lets me find ivar references now?)
> >
> > Rant over for now.
> >
> > -Todd Blanchard
> >
>
>
>