Hi Esteban, I think the
Do/Evaluate it Print it Debug it menu naming is a tribute to Smalltalk history as it was already part of ST80 (see http://www.cosc.canterbury.ac.nz/wolfgang.kreutzer/cosc205/images/stShot13.gif) In this case the text is seen not only as text but as a real expression - maybe that's the reason for the "it" and also the reason for having this in a separate menu group divided by a separator line. I would not change it, even when it is not consistent or make some people feel uncomfortable for three reasons: 1. The do it/print it/debug it is part of nearly any Smalltalk or Pharo tutorial/books so this is what people would expect it to look like 2. The Cut/Copy/Paste is known from any other UI based operating system and application, so this is what people would expect it to look like and the strongest reason: 3. If you change "Print it" to just "Print" people would expect something is coming out of their printer device! ;) We can change anything in Pharo - but not so easy the expectation of users. Bye T. > Gesendet: Mittwoch, 16. Juli 2014 um 16:01 Uhr > Von: "Esteban A. Maringolo" <[email protected]> > An: "Pharo Development List" <[email protected]> > Betreff: Re: [Pharo-dev] consideration of Smalltalk "DoIt" > > 2014-07-15 23:32 GMT-03:00 Eliot Miranda <[email protected]>: > > On Jul 15, 2014, at 1:50 PM, "Esteban A. Maringolo" <[email protected]> > > wrote: > > >> Why make a distinction between copying text and > >> evaluating/profiling/debugging it? I only saw this in Smalltalk. > > > > ?? I'd be more than annoyed if copying the text "rm -rf *" evaluated it > > too... > > Well... it would be sending the object at the variable rm the message > selector #- with rf as argument :) > > I'm not sure if I understood what you meant. But I'm talking about > consistency, it is we use "verb + it" for everything, or we don't. > > Ej: > A) > Do/Evaluate it > Print it > Debug it > Copy it > Cut it > Paste it > > B) > Evaluate > Print > Debug > Copy > Cut > Paste > > Certainly the latter feels better to me. And I haven't seen a single > UI/UX guideline suggesting the naming of commands like A. > > But again, maybe i'm lost in translation here. > > Regards. > > Esteban A. Maringolo > >
