November 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [[ false ] whileFalse: [ ]] in workspace

by Mariano Martinez Peck

On Thu, Nov 29, 2012 at 5:26 PM, Serge Stinckwich < serge.stinckwich(a)gmail.com> wrote: > On Thu, Nov 29, 2012 at 3:30 PM, Camillo Bruni <camillobruni(a)gmail.com> > wrote: > > if you have time try to figure out in which pharo version the bug > appeared... > > (I should write a tool for that :P) > > > > => do a binary search over pharo versions > http://pharo.gforge.inria.fr/ci/image/20/ > > Like a git bissect ? :-) > > http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html > > Cami, the wiki police says you should store this as a student project ;) > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/ > > -- Mariano http://marianopeck.wordpress.com

Nov. 29, 2012

Re: [Pharo-project] Getting started with Athens

by Casimiro de Almeida Barreto

Yeah, The problem is that Fedora sometimes (many times) just does not have libXX.so but libXX.so.1 (or whatever). Creating the simlinks solved the problems !!! Thanks Igor & Vanessa !!!

Nov. 29, 2012

Re: [Pharo-project] [[ false ] whileFalse: [ ]] in workspace

by Serge Stinckwich

On Thu, Nov 29, 2012 at 3:30 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > if you have time try to figure out in which pharo version the bug appeared... > (I should write a tool for that :P) > > => do a binary search over pharo versions http://pharo.gforge.inria.fr/ci/image/20/ Like a git bissect ? :-) http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://doesnotunderstand.org/

Nov. 29, 2012

Re: [Pharo-project] Spec question: menues

by Benjamin

I think it could be extended on other widgets :) They are only implemented here because the need was for menus in list and text I guess :) Ben On Nov 29, 2012, at 4:36 PM, Goubier Thierry wrote: > Le 29/11/2012 16:11, Benjamin a Ã©crit : >> Thank you for your explanation, I didn't have time to reply (sorry :( ) >> >> The mechanism describe is still working (or at least should), but I thought that the second argument was a boolean to know is shift was pressed or not. I may be wrong :) > > Oups :-( You're right, it's the shift status. So it should be : > > textModel menu: [:aMenu :shifted | self buildMenu: aMenu shifted: shifted ] > > And: > > buildMenu: aMenu shifted: shifted > > self isActive ifTrue: [ > (aMenu add: self label target: self selector: #execute) > enablementSelector: #isEnabled; > icon: (self icon notNil > ifTrue: [ UITheme current perform: self icon ] > ifFalse: [ nil ]); > keyText: self keyString ] > > Oh, and I notice that now : #menu: only exists for ListComposableModel and TreeModel in Spec, so this method will only work for them. But as this is where you usually needs it, it should be Ok :). > > Thierry > >> Thanks again, > > Thanks for correcting my example. > > Thierry > >> Ben >> >> On Nov 29, 2012, at 4:05 PM, Goubier Thierry wrote: >> >>> Le 28/11/2012 10:03, Torsten Bergmann a Ã©crit : >>>> Can anyone point me to a spec example >>>> with a (context) menu with icons and >>>> where we can enable/disable specific >>>> menue items depending on state? >>>> >>> >>> I'm not sure there is anything Spec specific in menus doing that but... >>> >>> A source for doing what you want is available in the OmniBrowser (Pharo 1.4). I reused a simplified version of that code in the Alt Browser in Pharo 2.0; if you browse around version 40, it is linked to a Spec-built interface. >>> >>> The example goes like that : >>> >>> A menu command object answer the following methods: >>>>> isActive (in the menu or not in the menu) >>>>> isEnabled (greyed out in the menu) >>>>> execute (the command to execute when selected) >>>>> icon (the icon symbol name) >>>>> label (the text of the menu item) >>>>> keyString (if you want to add a keymapping shortcut as well, it lists itself in the menu). >>> >>> Building a menu item is then the following, once you get the menu given to you by the widget : >>> >>> buildTreeMenu: aMenu on: aTarget >>> >>> ... >>> self isActive ifTrue: [ >>> (aMenu add: self label target: self selector: #execute) >>> enablementSelector: #isEnabled; >>> icon: (self icon notNil >>> ifTrue: [ UITheme current perform: self icon ] >>> ifFalse: [ nil ]); >>> keyText: self keyString ] >>> ... >>> >>> When you create your Spec GUI, you ask the widget model to give you the menu before showing it to the user (this is in initializePresenter) >>> >>> textModel menu: [:aMenu :aTarget | self buildMenu: aMenu on: aTarget ] >>> >>> The resulting menu will look like the picture in attachment. >>> >>> Note: This is with a fairly old version of Spec. Newer versions may have changed the way to get the menu from the widget model. >>> >>> Note 2: Since the menu is built each time the user asks for it then its easy to have a menu which depends on the state of the application (the type of selected item, etc...) >>> >>> Thierry >>> -- >>> Thierry Goubier >>> CEA list >>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>> 91191 Gif sur Yvette Cedex >>> France >>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>> <Capture du 2012-11-29 15:45:34.png> >> >> >> >> > > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Nov. 29, 2012

Re: [Pharo-project] Spec question: menues

by Goubier Thierry

Le 29/11/2012 16:11, Benjamin a Ã©crit : > Thank you for your explanation, I didn't have time to reply (sorry :( ) > > The mechanism describe is still working (or at least should), but I thought that the second argument was a boolean to know is shift was pressed or not. I may be wrong :) Oups :-( You're right, it's the shift status. So it should be : textModel menu: [:aMenu :shifted | self buildMenu: aMenu shifted: shifted ] And: buildMenu: aMenu shifted: shifted self isActive ifTrue: [ (aMenu add: self label target: self selector: #execute) enablementSelector: #isEnabled; icon: (self icon notNil ifTrue: [ UITheme current perform: self icon ] ifFalse: [ nil ]); keyText: self keyString ] Oh, and I notice that now : #menu: only exists for ListComposableModel and TreeModel in Spec, so this method will only work for them. But as this is where you usually needs it, it should be Ok :). Thierry > Thanks again, Thanks for correcting my example. Thierry > Ben > > On Nov 29, 2012, at 4:05 PM, Goubier Thierry wrote: > >> Le 28/11/2012 10:03, Torsten Bergmann a Ã©crit : >>> Can anyone point me to a spec example >>> with a (context) menu with icons and >>> where we can enable/disable specific >>> menue items depending on state? >>> >> >> I'm not sure there is anything Spec specific in menus doing that but... >> >> A source for doing what you want is available in the OmniBrowser (Pharo 1.4). I reused a simplified version of that code in the Alt Browser in Pharo 2.0; if you browse around version 40, it is linked to a Spec-built interface. >> >> The example goes like that : >> >> A menu command object answer the following methods: >>>> isActive (in the menu or not in the menu) >>>> isEnabled (greyed out in the menu) >>>> execute (the command to execute when selected) >>>> icon (the icon symbol name) >>>> label (the text of the menu item) >>>> keyString (if you want to add a keymapping shortcut as well, it lists itself in the menu). >> >> Building a menu item is then the following, once you get the menu given to you by the widget : >> >> buildTreeMenu: aMenu on: aTarget >> >> ... >> self isActive ifTrue: [ >> (aMenu add: self label target: self selector: #execute) >> enablementSelector: #isEnabled; >> icon: (self icon notNil >> ifTrue: [ UITheme current perform: self icon ] >> ifFalse: [ nil ]); >> keyText: self keyString ] >> ... >> >> When you create your Spec GUI, you ask the widget model to give you the menu before showing it to the user (this is in initializePresenter) >> >> textModel menu: [:aMenu :aTarget | self buildMenu: aMenu on: aTarget ] >> >> The resulting menu will look like the picture in attachment. >> >> Note: This is with a fairly old version of Spec. Newer versions may have changed the way to get the menu from the widget model. >> >> Note 2: Since the menu is built each time the user asks for it then its easy to have a menu which depends on the state of the application (the type of selected item, etc...) >> >> Thierry >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> <Capture du 2012-11-29 15:45:34.png> > > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Nov. 29, 2012

Re: [Pharo-project] Spec question: menues

by Benjamin

Thank you for your explanation, I didn't have time to reply (sorry :( ) The mechanism describe is still working (or at least should), but I thought that the second argument was a boolean to know is shift was pressed or not. I may be wrong :) Thanks again, Ben On Nov 29, 2012, at 4:05 PM, Goubier Thierry wrote: > Le 28/11/2012 10:03, Torsten Bergmann a Ã©crit : >> Can anyone point me to a spec example >> with a (context) menu with icons and >> where we can enable/disable specific >> menue items depending on state? >> > > I'm not sure there is anything Spec specific in menus doing that but... > > A source for doing what you want is available in the OmniBrowser (Pharo 1.4). I reused a simplified version of that code in the Alt Browser in Pharo 2.0; if you browse around version 40, it is linked to a Spec-built interface. > > The example goes like that : > > A menu command object answer the following methods: > >>isActive (in the menu or not in the menu) > >>isEnabled (greyed out in the menu) > >>execute (the command to execute when selected) > >>icon (the icon symbol name) > >>label (the text of the menu item) > >>keyString (if you want to add a keymapping shortcut as well, it lists itself in the menu). > > Building a menu item is then the following, once you get the menu given to you by the widget : > > buildTreeMenu: aMenu on: aTarget > > ... > self isActive ifTrue: [ > (aMenu add: self label target: self selector: #execute) > enablementSelector: #isEnabled; > icon: (self icon notNil > ifTrue: [ UITheme current perform: self icon ] > ifFalse: [ nil ]); > keyText: self keyString ] > ... > > When you create your Spec GUI, you ask the widget model to give you the menu before showing it to the user (this is in initializePresenter) > > textModel menu: [:aMenu :aTarget | self buildMenu: aMenu on: aTarget ] > > The resulting menu will look like the picture in attachment. > > Note: This is with a fairly old version of Spec. Newer versions may have changed the way to get the menu from the widget model. > > Note 2: Since the menu is built each time the user asks for it then its easy to have a menu which depends on the state of the application (the type of selected item, etc...) > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > <Capture du 2012-11-29 15:45:34.png>

Nov. 29, 2012

Re: [Pharo-project] Spec question: menues

by Goubier Thierry

Le 28/11/2012 10:03, Torsten Bergmann a Ã©crit : > Can anyone point me to a spec example > with a (context) menu with icons and > where we can enable/disable specific > menue items depending on state? > I'm not sure there is anything Spec specific in menus doing that but... A source for doing what you want is available in the OmniBrowser (Pharo 1.4). I reused a simplified version of that code in the Alt Browser in Pharo 2.0; if you browse around version 40, it is linked to a Spec-built interface. The example goes like that : A menu command object answer the following methods: >>isActive (in the menu or not in the menu) >>isEnabled (greyed out in the menu) >>execute (the command to execute when selected) >>icon (the icon symbol name) >>label (the text of the menu item) >>keyString (if you want to add a keymapping shortcut as well, it lists itself in the menu). Building a menu item is then the following, once you get the menu given to you by the widget : buildTreeMenu: aMenu on: aTarget ... self isActive ifTrue: [ (aMenu add: self label target: self selector: #execute) enablementSelector: #isEnabled; icon: (self icon notNil ifTrue: [ UITheme current perform: self icon ] ifFalse: [ nil ]); keyText: self keyString ] ... When you create your Spec GUI, you ask the widget model to give you the menu before showing it to the user (this is in initializePresenter) textModel menu: [:aMenu :aTarget | self buildMenu: aMenu on: aTarget ] The resulting menu will look like the picture in attachment. Note: This is with a fairly old version of Spec. Newer versions may have changed the way to get the menu from the widget model. Note 2: Since the menu is built each time the user asks for it then its easy to have a menu which depends on the state of the application (the type of selected item, etc...) Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Nov. 29, 2012

[Pharo-project] Delay bug

by Guillermo Polito

Hi, When using a Delay and saving the image, the delay becomes stupidly broken. Look at this: With the following code Object subclass: #DelayBug instanceVariableNames: 'delay process' classVariableNames: '' poolDictionaries: 'private' category: 'DelayBug' start delay := Delay forMilliseconds: 300. process := [ [ Transcript logCr: 'test'. delay wait . false ] whileFalse: [ ] ] fork. - Then evaluate. *db := DelayBug new.* *db start.* - inspect *db instVarAt: 'delay'.* * * The delay seems ok. - save the image The delay has a stupid time to be finished :/ Guille

Nov. 29, 2012

Re: [Pharo-project] Internship

by Goubier Thierry

Le 27/11/2012 09:45, StÃ©phane Ducasse a Ã©crit : > > On Nov 26, 2012, at 10:02 AM, Goubier Thierry wrote: > >> Le 23/11/2012 19:04, StÃ©phane Ducasse a Ã©crit : >>> thierry >>> >>> we will publish this offer. >>> Now did you look at dave mason work on C header parsing. >> >> Hi Stef, >> >> no I haven't but I can have a look if you had any pointer. >> >> I started doing C parsing out of Lex/Yacc and studying C implementations (pcc, gcc before 4.0, gcc 4+, CLANG/LLVM) and ocaml (CIL, Frama-C) (looked a bit at ANTLR as well). After a few years of C/Flex/Bison, I moved to Pharo/SMACC. > > this is cool. > what is the license of the Pharo one? Internal use only. We may discuss that when you will come :) Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Nov. 29, 2012

Re: [Pharo-project] [[ false ] whileFalse: [ ]] in workspace

by Camillo Bruni

if you have time try to figure out in which pharo version the bug appeared... (I should write a tool for that :P) => do a binary search over pharo versions http://pharo.gforge.inria.fr/ci/image/20/ On 2012-11-29, at 11:04, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Hi! > > I was surprised by trying to evaluate the following expression in a > workspace: > > [[ false ] whileFalse: [ ]] > > and getting an error SubscriptOutOfBounds: 1... > > The strange thing is that compiling that expression inside a block works, > but not in the workspace... > > Any idea? > Guille

Nov. 29, 2012