January 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Growl setting name

by Henrik Nergaard

The underlying class and implementation relies on Morph and since it is also a subclass of Morph, should end with the Morph postfix. Had the implementation used Bloc or similar I would expect it to be named ...Bloc or ...Brick to signal this. Best regards, Henrik -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Ferlicot D. Cyril Sent: Friday, January 15, 2016 10:32 PM To: pharo-dev(a)lists.pharo.org Subject: Re: [Pharo-dev] Growl setting name Le 15/01/2016 22:25, Henrik Nergaard a Ã©crit : > NotificationMorph | NotifierMorph | InformationMorph ? > > Best regards, > Henrik > Since Morph will be replace by Bloc I don't know if it's wise to name things with "Morph". -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

Jan. 15, 2016

Re: [Pharo-dev] Growl setting name

by Nicolai Hess

2016-01-15 22:25 GMT+01:00 Henrik Nergaard <henrik.nergaard(a)uia.no>: > NotificationMorph | NotifierMorph | InformationMorph ? > +1 for Notification > Best regards, > Henrik > > -----Original Message----- > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of > Tudor Girba > Sent: Friday, January 15, 2016 10:21 PM > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] Growl setting name > > Hi > > I think it should not be named âdialogâ and âpopupâ is too generic. > > How about âPopupInfoâ? > > Doru > > > > On Jan 15, 2016, at 10:11 PM, Ferlicot D. Cyril < > cyril.ferlicot(a)gmail.com> wrote: > > > > Apparently "Growl" is the name of Mac notification. But me, that never > > used Mac, I don't know that. I think I am not the only one in that case. > > > > If it's not just my ignorance, I propose to rename "Growl" as "Popup > > dialog" or "Popup" or "Popup dialog/Growl". > > > > What do you thing guys ? > > If you think as me I will open an issue. > > > > -- > > Cyril Ferlicot > > > > http://www.synectique.eu > > > > 165 Avenue Bretagne > > Lille 59000 France > > > > -- > www.tudorgirba.com > www.feenk.com > > "Every now and then stop and ask yourself if the war you're fighting is > the right one." > > > > > >

Jan. 15, 2016

Re: [Pharo-dev] Growl setting name

by Ferlicot D. Cyril

Le 15/01/2016 22:25, Henrik Nergaard a Ã©crit : > NotificationMorph | NotifierMorph | InformationMorph ? > > Best regards, > Henrik > Since Morph will be replace by Bloc I don't know if it's wise to name things with "Morph". -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

Jan. 15, 2016

Re: [Pharo-dev] Growl setting name

by Sven Van Caekenberghe

> On 15 Jan 2016, at 22:25, Henrik Nergaard <henrik.nergaard(a)uia.no> wrote: > > NotificationMorph | NotifierMorph | InformationMorph ? +1 > Best regards, > Henrik > > -----Original Message----- > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Tudor Girba > Sent: Friday, January 15, 2016 10:21 PM > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] Growl setting name > > Hi > > I think it should not be named âdialogâ and âpopupâ is too generic. > > How about âPopupInfoâ? > > Doru > > >> On Jan 15, 2016, at 10:11 PM, Ferlicot D. Cyril <cyril.ferlicot(a)gmail.com> wrote: >> >> Apparently "Growl" is the name of Mac notification. But me, that never >> used Mac, I don't know that. I think I am not the only one in that case. >> >> If it's not just my ignorance, I propose to rename "Growl" as "Popup >> dialog" or "Popup" or "Popup dialog/Growl". >> >> What do you thing guys ? >> If you think as me I will open an issue. >> >> -- >> Cyril Ferlicot >> >> http://www.synectique.eu >> >> 165 Avenue Bretagne >> Lille 59000 France >> > > -- > www.tudorgirba.com > www.feenk.com > > "Every now and then stop and ask yourself if the war you're fighting is the right one." > > > > >

Jan. 15, 2016

Re: [Pharo-dev] Growl setting name

by Henrik Nergaard

NotificationMorph | NotifierMorph | InformationMorph ? Best regards, Henrik -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Tudor Girba Sent: Friday, January 15, 2016 10:21 PM To: Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: Re: [Pharo-dev] Growl setting name Hi I think it should not be named âdialogâ and âpopupâ is too generic. How about âPopupInfoâ? Doru > On Jan 15, 2016, at 10:11 PM, Ferlicot D. Cyril <cyril.ferlicot(a)gmail.com> wrote: > > Apparently "Growl" is the name of Mac notification. But me, that never > used Mac, I don't know that. I think I am not the only one in that case. > > If it's not just my ignorance, I propose to rename "Growl" as "Popup > dialog" or "Popup" or "Popup dialog/Growl". > > What do you thing guys ? > If you think as me I will open an issue. > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 165 Avenue Bretagne > Lille 59000 France > -- www.tudorgirba.com www.feenk.com "Every now and then stop and ask yourself if the war you're fighting is the right one."

Jan. 15, 2016

Re: [Pharo-dev] Growl setting name

by Tudor Girba

Hi I think it should not be named âdialogâ and âpopupâ is too generic. How about âPopupInfoâ? Doru > On Jan 15, 2016, at 10:11 PM, Ferlicot D. Cyril <cyril.ferlicot(a)gmail.com> wrote: > > Apparently "Growl" is the name of Mac notification. But me, that never > used Mac, I don't know that. I think I am not the only one in that case. > > If it's not just my ignorance, I propose to rename "Growl" as "Popup > dialog" or "Popup" or "Popup dialog/Growl". > > What do you thing guys ? > If you think as me I will open an issue. > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 165 Avenue Bretagne > Lille 59000 France > -- www.tudorgirba.com www.feenk.com "Every now and then stop and ask yourself if the war you're fighting is the right one."

Jan. 15, 2016

Growl setting name

by Ferlicot D. Cyril

Apparently "Growl" is the name of Mac notification. But me, that never used Mac, I don't know that. I think I am not the only one in that case. If it's not just my ignorance, I propose to rename "Growl" as "Popup dialog" or "Popup" or "Popup dialog/Growl". What do you thing guys ? If you think as me I will open an issue. -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

Jan. 15, 2016

Re: [Pharo-dev] [Moose-dev] [Pharo-users] [ann] gtdebugger in pharo 5.0

by Esteban Lorenzano

problem is that *all other tools* have accept/cancel in context menu. if you change one, you need to change allâ¦ otherwise you are breaking muscular/visual memory for no gain. Soâ¦ I propose to put them in same place all other tools have it: in the contextual menu. cheers, Esteban ps: in general, contextual menus are not the ones depending on selection, but the ones depending on the widget (a contextual menu in a list is different than a contextual menu of a text area, etc.). Thenâ¦ once in the *context* we want, you can pick selection actions or not. So put them there is perfectly OK. > On 15 Jan 2016, at 18:28, David Allouche <david(a)allouche.net> wrote: > > >> On 15 Jan 2016, at 13:39, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >>> On Jan 14, 2016, at 12:59 PM, Andrei Chis <chisvasileandrei(a)gmail.com <mailto:chisvasileandrei@gmail.com>> wrote: >> >>> Most (all?) other tools don't have Accept/Cancel buttons. >> >> The logic is that these are actions that do not depend on the selection, so in Glamour we map these on actions that are applicable to the entire presentation. A similar approach is present in the inspector, although probably it does not appear so prominently because there is no text. We could try to add them in a dropdown menu. Would that help? > > In my opinion, they actions should either be directly visible in the window, or in the contextual menu, or both. But not in a dropdown. > > They are common actions, so I see no value in putting them in a dropdown. Dropdown menus are only interesting for actions that need to be discoverable, by providing a visual clue to explore. But they are more often than not, a bad idea. > > Actually, I would love if Pharo had more toolbars and menu bars. A good rule of Human Interface Guidelines (HIG) is that actions should be accessible in multiple ways: > > Toolbars and buttons. Not too many of them please, just for essential, application-specific actions. > Menus, either in the window MS-style or at the top of the display Apple-style. > Contextual menu. > Shortcuts (all of them, discoverable by examining menus and contextual menus). >

Jan. 15, 2016

Re: [Pharo-dev] Git repository and branch for spur enable pharo-vm

by Esteban Lorenzano

Hi, > On 15 Jan 2016, at 18:29, Holger Freyther <holger(a)freyther.de> wrote: > > Hi, > > what is the official pharo-vm git repository? It looks like github.com/pharo-project/pharo-vm is not being updated right now. It looks like esteban's fork is currently being used and the spur64 branch. Is that correct? Can it it to be used for spur32 and spure64? Is there any plan to merge this back into a repositpory in pharo-project/pharo-vm? yes to everything :) - right now is the one Iâm updating - it will be merged with pharo-project (I didnât have the time to do it, but it will be soon) - you can do a spur32 and theoretically a stack 64bits, but since we still do not have a 64bits image (one of my soon (â¢) next steps) it doesnât looks meaningful right now :) cheers, Esteban > > kind regards > holger

Jan. 15, 2016

Re: [Pharo-dev] Color yzw

by Sven Van Caekenberghe

> On 15 Jan 2016, at 20:38, stepharo <stepharo(a)free.fr> wrote: > >> >> > No, you are right. It isn't shown in red, even if it is a unknown symbol. >> > >> > I'll have a look. >> >> Oh, that is bad. >> The check for existing Symbols always succeeds, because >> Parsing an expression with RBParser creates RBMethod- and RBMessageNodes >> And they use always #asSymbol for its selectors. >> > Argh this is a pity because this is a really useful >> That means, as soon as we parse an expression, we add all new Symbols. >> >> And as the parser is now used for syntax highlighting as well, this means >> new symbols will be added on compiling new methods and expressions >> or just highlighting them. That's bad. >> > > Yes I was discussing with students that used Pharo 40 during a lecture and they loved it. >> anyone an idea? >> > I'm trying to think. > Looks like it would be good to be able to make a distinction between symbols and selectors (selectors installed > in method dictionaries) 'selectors' is a misleading name I think, but your definition is OK: 'selectors installed in method dictionaries'. I had already noticed that sometimes in completion you get suggestions like p pr pri prin print which is probably related. Just because someone somewhere defines a symbol (that might become garbage soon), does not yet make it a valid selector. But how fix this in an efficient way ? > Stef >> >> >> 2016-01-15 13:10 GMT+01:00 stepharo <stepharo(a)free.fr>: >> >>> >> >>> Hi >> >>> >> >>> In the past in Pharo when a message was not matching an existing selector the selector was turned into red >> >> >> >> >> >> I think this only happened for names not known as a symbol, regardless whether this symbol exists as a message selector or just a symbol. >> >> >> >> If no symbol table includes the symbol yzw >> >> >> >> Color yzw >> >> >> >> will show yzw red, >> >> >> >> Color yello >> >> will print yello in italic >> >> Color yellow >> >> will print yellow normal >> >> Color jaune >> >> will print jaune red, as long it is not in a SymbolTable. >> >> >> >> >> >>> >> >>> So we could see immediately that you typed an error. >> >>> >> >>> Right now, the behavior only exists for Class >> >>> so >> >>> >> >>> Po is italiczec >> >>> Pox is red >> >>> >> >>> I played with the blueStyleTable but I cannot get it working on selector. >> >>> Does anybody know? >> >>> >> >>> Such kind of glitch is slowing me when shooting new pharo videos. >> >>> >> >>> Stef >> >>> >> >>> >> >> >> > >> > >

Jan. 15, 2016