On Jun 8, 2010, at 10:07 AM, Stéphane Ducasse wrote:
>
> On Jun 8, 2010, at 9:28 AM, Fernando olivero wrote:
>
>> Hi Simon,
>>
>> On Jun 7, 2010, at 5:48 PM, Simon Denier wrote:
>>
>>>
>>> OK two other things
>>>
>>> 1) (minor) I find myself repeatdly trying to extend a Shape size to display
>>> more instance variables and methods by looking for the resize handle in the
>>> bottom right corner
>>>
>>
>
> Fernando if you listen what simon is telling you is that he does not want to
> see the code in larger font.
> he said that on his 30 inches screen he would like to see more method names
> at once.
> Now looking at what your hand is doing is interesting: simon hand wanted to
> have a large number of methods
> so he tried to grab the corner.
>
> In terms of UI assessment, one guru said that we can debug 50% of the
> problems by asking people to speak aloud when they try
> an interface. So this is a cheap but really effective way of making progress.
>
>> We wanted to provide a concise and compact view of the shapes, due to the
>> restrictions that the current Morphic is pixel based and not scalable, to
>> take the most of the real estate of a pampas. Possibly once i migrate to a
>> scalable and vectorized UI framework ( Morphic3 ?), resizing would be
>> considered.
>
> You have a far easier solution if you want to let people work better.
>
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.
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.
> ....
> if you want to run a real user experience feedback I can be a guinea pig
> you can ask me to do some tasks and tape me.
>
> Stef
Thanks Stef!
I'll set up an experiment and will take your offer!
Fernando
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
