Stef, i was not speaking of font resize, we used the scroller widget to reveal hidden attributes or methods, and not shape resizing, providing a compact view of the shapes for the reasons above expressed.
but may be the user can decide if he wants more :)
Every shape is has a fixed dimension of 340p x 400px, because we wanted to avoid getting rid of real state quickly and not being able to attack this problem with the current Morphic.
Even though i agree that the hand behaves differently, and this in direct conflict with the habits of Pharo users, there is no "resize" handle of visual cue in the bottom corner of the shapes ( at least for now , till the Morphic dependency is dropped).
2) when I want to edit a method, the shape takes the full screen and I can't see any other data. Why can't I edit the method in-place
This was a decision i took, based on the fact that this lets you focus on writing that method only, similar to what Ommwriter proposes. http://www.ommwriter.com/
Bad bad bad idea. You never want to have a look at other code while programming. For me this will be the reason 1 for not using gaucho. Smalltalk is already bad because you have to open another browser but gaucho is a jail since you cannot even look at something else.
Thats why we needed to release it! To get good feed back like this one! You are right, occluding other methods shapes behind the Code editor view is to restricting. I'll modify this behavior ASAP.
Good because else this is clearly a no go at all for me. I got enough frustrated with smalltalk editors.