- Pharo-dev - lists.pharo.org

Completion again ...

by Igor Stasenko

trying to fix completion autopopups when there is nothing to suggest to prevent popping up the empty and useless menu, i stumbled upon this: initializeInstVars (clazz isNil or: [ includeVariables not ]) ifTrue: [ ^ self ]. instVars := clazz allInstVarNames asSortedCollection. instVars := instVars collect: [ :each | NECInstVarEntry contents: each type: #instVar ]. instVars add: (NECSelfEntry contents: 'self' type: #self). instVars add: (NECSuperEntry contents: 'super' type: #super) there's something sick with that.. first we using NECSelfEntry but then, if that's not enough, we pass 'self' as its contents.. but that's also not enough! we pass 'self' as its type as well.. checking many subclasses of NECEntry and how they initialized, it is almost every time the same: - you use NECXXXXEntry , we always pass separate #XXXX as its type like just using NECXXXXEntry not enough to indicate that. i going to fix that as well -- Best regards, Igor Stasenko.

Sept. 16, 2013

Re: [Pharo-dev] [Pharo-users] Please help us by buying the book

by Alexandre Bergel

Thanks for your nice words :-) Alexandre On Sep 16, 2013, at 11:57 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 16 Sep 2013, at 16:24, Damien Cassou <damien.cassou(a)gmail.com> wrote: > >> Hi, >> >> please support our work on Pharo by buying the new Deep into Pharo book >> >> http://rmod.lille.inria.fr/deepIntoPharo/ >> >> Your money go to the Pharo Association, so it's worth it. > > Done. > > Great work, Damien, StÃ©phane, Alexandre & Jannik. > > Your effort is much appreciated. > > Sven > >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 16, 2013

Re: [Pharo-dev] [Pharo-users] Please help us by buying the book

by Sven Van Caekenberghe

On 16 Sep 2013, at 16:24, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Hi, > > please support our work on Pharo by buying the new Deep into Pharo book > > http://rmod.lille.inria.fr/deepIntoPharo/ > > Your money go to the Pharo Association, so it's worth it. Done. Great work, Damien, StÃ©phane, Alexandre & Jannik. Your effort is much appreciated. Sven > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

Sept. 16, 2013

Re: [Pharo-dev] Issues trying to use NewList on Nautilus

by Benjamin

On Sep 16, 2013, at 4:18 PM, Nicolas Passerini <npasserini(a)gmail.com> wrote: > Last Saturday in the Pharo Sprint in Buenos Aires, together with Mariano Peck and Guido Chari we have been trying to address issue 11605, i.e. using NewList in Nautilus. I am still trying to finish with this task, and I have a few questions, may be somebody here can enlighten me. > > We have encountered some problems with multiple selections. First, the list has 4 ValueModels for its selected elements: selectedIndex, selectedIndexes, selectedItem, selectedItems. I would like to understand more clearly how should we use them. In particular I find difficult to bring the plural versions and the singular versions together. > If I select more than one element in the list, it seems that the value in the selectedItem/selectedIndex points to the last one I clicked. But then the model in Nautilus is receiving two updates, one from selectedItem/Index and the other from selectedItems/indexes, should we just ignore the singular one or what? If your UI is based on multi selection (and Nautilus definitely is) you should not register to whenSelectedIndexChanged:/whenSelectedItemChanged:, but only the plural version. > > Second, in my linux the list doesn't seem to receive ctrl+click events. Any clue about this? VM ? > > Finally, another question not related to multiple selections. > The old list (it was a PluggableIconListMorph) has a "searchedElement" attribute. Looking at the categories list in Nautilus, the usage is so: if you have not selected any category (i.e. you are seeing the method of all categories in a class) and you click on a method in the method list, the searched element of the category list points to the category of the selected method. This is different from selecting the category, because selecting the category would filter the method list. It also highlights the category in a different color. > > So, my question is, should we keep this behaviour while migrating Nautilus to new lists o not? Yes we should :) > If the answer is yes, I would ask how to do it, because the NewList does not seem to have this feature. Should I add the searchedElement to the NewList or is there another way to achieve the same behaviour? As far as I remember, this feature exists in NewList, but I do not think it's publicly exposed. But I would like to finish by saying we (the community) should better put effort on the Spec based Nautilus new version that the NewList in Nautilus. The event mechanism between PluggableListMorph and NewList is so different, it will be really painful for you guys :) MCHttpRepository location: 'http://smalltalkhub.com/mc/BenjaminVanRyseghem/Nautilus/main' user: '' password: '' Ben

Sept. 16, 2013

Re: [Pharo-dev] Issues trying to use NewList on Nautilus

by Camillo Bruni

On 2013-09-16, at 11:18, Nicolas Passerini <npasserini(a)gmail.com> wrote: > Second, in my linux the list doesn't seem to receive ctrl+click events. Any > clue about this? yes, that is actually the part gisela and nahuel hacked on during the sprint. Seems like this combination of key modifiers + mouse click is not properly reported to the image :/.

Sept. 16, 2013

Re: [Pharo-dev] [Pharo-users] Please help us by buying the book

by Damien Cassou

On Mon, Sep 16, 2013 at 4:34 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > What about a tweet from the pharo tweeter so we can retweet? ;) I tweeted from my account and ESUG's one. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Sept. 16, 2013

Re: [Pharo-dev] [Pharo-users] Please help us by buying the book

by Guillermo Polito

What about a tweet from the pharo tweeter so we can retweet? ;) On Mon, Sep 16, 2013 at 4:24 PM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > Hi, > > please support our work on Pharo by buying the new Deep into Pharo book > > http://rmod.lille.inria.fr/deepIntoPharo/ > > Your money go to the Pharo Association, so it's worth it. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >

Sept. 16, 2013

Re: [Pharo-dev] Issues trying to use NewList on Nautilus

by Guillermo Polito

Ben? :D On Mon, Sep 16, 2013 at 4:18 PM, Nicolas Passerini <npasserini(a)gmail.com>wrote: > Last Saturday in the Pharo Sprint in Buenos Aires, together with Mariano > Peck and Guido Chari we have been trying to address issue 11605<https://pharo.fogbugz.com/default.asp?pre=preMultiSearch&pg=pgList&pgBack=p…>, > i.e. using NewList in Nautilus. I am still trying to finish with this task, > and I have a few questions, may be somebody here can enlighten me. > > We have encountered some problems with multiple selections. First, the > list has 4 ValueModels for its selected elements: selectedIndex, > selectedIndexes, selectedItem, selectedItems. I would like to understand > more clearly how should we use them. In particular I find difficult to > bring the plural versions and the singular versions together. > If I select more than one element in the list, it seems that the value in > the selectedItem/selectedIndex points to the last one I clicked. But then > the model in Nautilus is receiving two updates, one from selectedItem/Index > and the other from selectedItems/indexes, should we just ignore the > singular one or what? > > Second, in my linux the list doesn't seem to receive ctrl+click events. > Any clue about this? > > > Finally, another question not related to multiple selections. > The old list (it was a PluggableIconListMorph) has a "searchedElement" > attribute. Looking at the categories list in Nautilus, the usage is so: if > you have not selected any category (i.e. you are seeing the method of all > categories in a class) and you click on a method in the method list, the > searched element of the category list points to the category of the > selected method. This is different from selecting the category, because > selecting the category would filter the method list. It also highlights the > category in a different color. > > So, my question is, should we keep this behaviour while migrating Nautilus > to new lists o not? > If the answer is yes, I would ask how to do it, because the NewList does > not seem to have this feature. Should I add the searchedElement to the > NewList or is there another way to achieve the same behavior? > > > > > >

Sept. 16, 2013

Please help us by buying the book

by Damien Cassou

Hi, please support our work on Pharo by buying the new Deep into Pharo book http://rmod.lille.inria.fr/deepIntoPharo/ Your money go to the Pharo Association, so it's worth it. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Sept. 16, 2013

Issues trying to use NewList on Nautilus

by Nicolas Passerini

Last Saturday in the Pharo Sprint in Buenos Aires, together with Mariano Peck and Guido Chari we have been trying to address issue 11605<https://pharo.fogbugz.com/default.asp?pre=preMultiSearch&pg=pgList&pgBack=p…>, i.e. using NewList in Nautilus. I am still trying to finish with this task, and I have a few questions, may be somebody here can enlighten me. We have encountered some problems with multiple selections. First, the list has 4 ValueModels for its selected elements: selectedIndex, selectedIndexes, selectedItem, selectedItems. I would like to understand more clearly how should we use them. In particular I find difficult to bring the plural versions and the singular versions together. If I select more than one element in the list, it seems that the value in the selectedItem/selectedIndex points to the last one I clicked. But then the model in Nautilus is receiving two updates, one from selectedItem/Index and the other from selectedItems/indexes, should we just ignore the singular one or what? Second, in my linux the list doesn't seem to receive ctrl+click events. Any clue about this? Finally, another question not related to multiple selections. The old list (it was a PluggableIconListMorph) has a "searchedElement" attribute. Looking at the categories list in Nautilus, the usage is so: if you have not selected any category (i.e. you are seeing the method of all categories in a class) and you click on a method in the method list, the searched element of the category list points to the category of the selected method. This is different from selecting the category, because selecting the category would filter the method list. It also highlights the category in a different color. So, my question is, should we keep this behaviour while migrating Nautilus to new lists o not? If the answer is yes, I would ask how to do it, because the NewList does not seem to have this feature. Should I add the searchedElement to the NewList or is there another way to achieve the same behavior?

Sept. 16, 2013