2014-07-15 20:27 GMT+02:00 Esteban A. Maringolo <[email protected]>:
> I find the "... it" suffix obsolete. "Delete it", "Do it", "Print it", etc. > > Maybe it made sense in the past, but today it feels weird. > > There is no "Cut it", "Paste it", etc... nor similar in other software. > IMO, if the menu is contextual, the context already applies the "it" > (subject). > > Regards. > > Did you notice "it" is only mentionned when you will evaluate (do it / print it / debug it / ... )? Otherwise, if it's just text editing there is no it. So there is a sort of logic. IMO that makes sense, because evaluating is a special action. > > > > > Esteban A. Maringolo > > > 2014-07-15 15:16 GMT-03:00 kilon alios <[email protected]>: > > In python there is eval() which evaluates > > > > and there is exec() which executes > > > > The difference is that one calculates a value which it returns , the > other > > executes code. > > > > Personally I find "do it" very good choice because it makes clear what > you > > referring to , in contrast "evaluate" and "execute" can mean different > > things under different context. > > > > > +1 > > On Tue, Jul 15, 2014 at 9:07 PM, stepharo <[email protected]> wrote: > >> > >> In general I banned evaluate from the book vocabulary because people > think > >> that this is slower. > Compiler evaluate: is more how you do it ;) I'd say just do it (it's ok, we are an imperative language after all). > >> I saw teachers writing that smalltalk is interpreted and java compiled > :). > >> I use execute. > >> > >> > Ah, Cursor execute showWhile: [...], st80-v2 also had this vocabulary. So if the UI must reflect that you execute something, it's certainly a valuable word. I checked, it's still in Pharo 3.0 :) Personally, I find it too unpersonnal though. A robot, or an automaton executes a list of instructions. I prefer the anthropo-morphic programming ;) >> > >> On 15/7/14 19:20, Ben Coman wrote: > >>> > >>> > >>> Mostly I take for granted that "DoIt" has always been the way to > evaluate > >>> things with Smalltalk, however I find it awkward to use in writing a > >>> tutorial. Some examples... * After saving, select "Grid new" and > "DoIt" -- > >>> this sounds awkward, and even that you might need select the latter as > well. > >>> * After saving, "Grid new" DoIt. -- doesn't read nice > >>> * After saving, DoIt to "Grid new." -- worst of all > >>> > >>> I'd feel better writing something like this... > >>> * After saving, evaluate "Grid new". > >>> but "evaluate" is not an item in the menus. I think actually many > people > >>> talk this way with the implicit convention that "evaluate" means > "DoIt". > >>> > >>> So first, does anyone have a good way to compose sentences using > "DoIt". > >>> Second, how evil would it be to change the menus from "DoIt" to > >>> "Evaluate" and so avoid the implicit convention. > >>> > >>> cheers -ben > >>> > >>> > >>> > >>> > >> > >> > > > >
