good idea.

Just as a feedback. I tried to use Pharo to implement some algorithms in course I'm giving. This was instructive ... but I think I won't do it next year (except if I implement a pseudo-language a la etoy tile to do algorithmics). The major showstopper was Smalltalk syntax (except for good students). But, more importantly I think (and it bet this was far worst in squeak) is the lack of coherence, ergonomy, etc... I know this is something difficult. I don't espacially care for myself as I know all workarounds but these are really annoying for newcomer who at the end have a feelling of "this doesn't really work". I think ergonomy and coherence is something to discuss... Here are some remarks:

-I've always felt bored with the tool size that I always are resizing manually (I would prefer full screen by default actually)

-some shortcuts works with alt and ctrl, some only with alt (disturbing for newcomer that are used to ctrl - I use alt)

-shortcuts are working primarly for qwerty keyboards (especially ��those that add remove [])

-the selection of the code pane is sometime boring too... you have to click twice, or deselect/select

-...

I know I should open bugs tickets for that and will do it (just tell me those).

But more importantly, I think we should agree on these important usability feature. And especially, I'd like we rethink the browser. Alain did the whisker browser no ? What I want to say here is that it might be more appropriate for newcomers to have one big robust coding tool (classic browser + workspace + Transcript + Test Runner). I cannot do that by myself but it could be one topic to discuss in a meeting.��

��