On Mon, Jul 28, 2014 at 9:58 PM, Chris Muller <asqueaker@gmail.com> wrote:
The goal of "Print it" serves as a quick and light readonly feedback, and I think it has a distinct place that is separate from the inspector which is a place where you interact and manipulate the object. Furthermore, in the current implementation, the "print it" is floating and non intrusive (it goes away easily) while the inspector is at the moment a lasting piece.
Maybe remapping Command+p to inspect would solve it equally? ��:)
This is a point worth debating (I really love when we allocate time to talk about our UI - this is the one interface that we, in this community, use every day).
Of course, we could imagine an inspector that could be embedded in the popper window (in fact, I have that implementation, too :)), but the problem is that in its current form, the inspector is not made to be easily scalable. This might change with the adoption of Athens.
In the meantime, one direction I think we could take is to produce several scalable "printouts" that can also be visual.
��
Both of the example cases justifying it were that the user pressed the wrong key. ��UI's should not try to solve problems between the human <--> hardware interface.
I am not sure I follow. Could you elaborate please?
Cheers,
Doru
��
On Sun, Jul 27, 2014 at 6:33 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Hi,In the course of revamping the Pharo environment, we stumbled across the print it action and we (Andrei and I) decided to rethink it.
You can find more details here:http://www.humane-assessment.com/blog/rethinking-print-it-in-pharo
Let us know what you think.Cheers,Doru--
"Every thing has its own flow"
"Every thing has its own flow"