Re: [Pharo-dev] Can not open Browser on a given selector in 2.0
Yes probably much better to write a simple new one. I will try this evening as an exercise. Stef On Sep 18, 2013, at 8:23 AM, Marcus Denker wrote: > > On Sep 18, 2013, at 8:20 AM, Stéphane Ducasse > wrote: > >> hilaire >> >> I trid to understand why the browser is showing a different symbol and I got >> stuck. >> > We really should not waste our time with the old browser. > > >> Stf >> >> On Sep 18, 2013, at 7:17 AM, Stéphane Ducasse >> wrote: >> >>> >>> On Sep 17, 2013, at 10:53 PM, Hilaire Fernandes >>> wrote: >>> With 1.4, I use to open programmatically a *mini* browser on a given selector with the following code: Browser newOnClass: Number selector: #/ Now it bring a DNU Retangle>>topOffset: >>> >>> this is probably due to a missing layoutFrame >>> can you try asLayoutFrame I can use Nautilus but it opens a full complete browser and I don't want this. I can fix the code adding a asLayoutFrame (see cs) but then the browser does not open on the proper method. Hilaire >>> >>> >> >> >
Re: [Pharo-dev] Can not open Browser on a given selector in 2.0
On Sep 18, 2013, at 8:20 AM, Stéphane Ducasse wrote: > hilaire > > I trid to understand why the browser is showing a different symbol and I got > stuck. > We really should not waste our time with the old browser. > Stf > > On Sep 18, 2013, at 7:17 AM, Stéphane Ducasse > wrote: > >> >> On Sep 17, 2013, at 10:53 PM, Hilaire Fernandes >> wrote: >> >>> With 1.4, I use to open programmatically a *mini* browser on a given >>> selector with the following code: >>> >>> Browser newOnClass: Number selector: #/ >>> >>> Now it bring a DNU Retangle>>topOffset: >> >> this is probably due to a missing layoutFrame >> can you try asLayoutFrame >>> >>> I can use Nautilus but it opens a full complete browser and I don't want >>> this. >>> >>> I can fix the code adding a asLayoutFrame (see cs) but then the browser >>> does not open on the proper method. >>> >>> Hilaire >>> >> >> > > signature.asc Description: Message signed with OpenPGP using GPGMail
[Pharo-dev] if Pharo is key for you
Hi guys if Pharo is key for you then you should ask yourself what you did for Pharo recently. Writing code, writing documentation helping closing bug entries, participating to the association, to the consortium... Pharo is not happening from spontaneous generation. Stef
Re: [Pharo-dev] Can not open Browser on a given selector in 2.0
hilaire I trid to understand why the browser is showing a different symbol and I got stuck. Stf On Sep 18, 2013, at 7:17 AM, Stéphane Ducasse wrote: > > On Sep 17, 2013, at 10:53 PM, Hilaire Fernandes > wrote: > >> With 1.4, I use to open programmatically a *mini* browser on a given >> selector with the following code: >> >> Browser newOnClass: Number selector: #/ >> >> Now it bring a DNU Retangle>>topOffset: > > this is probably due to a missing layoutFrame > can you try asLayoutFrame >> >> I can use Nautilus but it opens a full complete browser and I don't want >> this. >> >> I can fix the code adding a asLayoutFrame (see cs) but then the browser does >> not open on the proper method. >> >> Hilaire >> > >
Re: [Pharo-dev] Can not open Browser on a given selector in 2.0
On Sep 17, 2013, at 10:53 PM, Hilaire Fernandes wrote: > With 1.4, I use to open programmatically a *mini* browser on a given selector > with the following code: > > Browser newOnClass: Number selector: #/ > > Now it bring a DNU Retangle>>topOffset: > > I can use Nautilus but it opens a full complete browser and I don't want this. > But the old Browser will be removed. It would have already been removed if there would not be a subclass. (course of a crappy system: even throwing stuff away is difficult) > I can fix the code adding a asLayoutFrame (see cs) but then the browser does > not open on the proper method. > After some people ran into that we added: https://pharo.fogbugz.com/f/cases/11624 But the real mistake was to not clean up the old Browser code. We are wasting our time for nothing maintaining two code bases. Marcus signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [Pharo-dev] Can not open Browser on a given selector in 2.0
We will remove all the StringHolder hierarchy so I suggest to have a look at the Spec tutorial and write a little mini browser. It should not be difficult based on the examples. We should move on and get rid of old code. Stef On Sep 17, 2013, at 10:53 PM, Hilaire Fernandes wrote: > With 1.4, I use to open programmatically a *mini* browser on a given selector > with the following code: > > Browser newOnClass: Number selector: #/ > > Now it bring a DNU Retangle>>topOffset: > > I can use Nautilus but it opens a full complete browser and I don't want this. > > I can fix the code adding a asLayoutFrame (see cs) but then the browser does > not open on the proper method. this is strange > > Hilaire >
Re: [Pharo-dev] Can not open Browser on a given selector in 2.0
On Sep 17, 2013, at 10:53 PM, Hilaire Fernandes wrote: > With 1.4, I use to open programmatically a *mini* browser on a given selector > with the following code: > > Browser newOnClass: Number selector: #/ > > Now it bring a DNU Retangle>>topOffset: this is probably due to a missing layoutFrame can you try asLayoutFrame > > I can use Nautilus but it opens a full complete browser and I don't want this. > > I can fix the code adding a asLayoutFrame (see cs) but then the browser does > not open on the proper method. > > Hilaire >
[Pharo-dev] Can not open Browser on a given selector in 2.0
With 1.4, I use to open programmatically a *mini* browser on a given selector with the following code: Browser newOnClass: Number selector: #/ Now it bring a DNU Retangle>>topOffset: I can use Nautilus but it opens a full complete browser and I don't want this. I can fix the code adding a asLayoutFrame (see cs) but then the browser does not open on the proper method. Hilaire 'From Pharo2.0 of 7 March 2013 [Latest update: #20600] on 18 September 2013 at 10:36:20 pm'! !Browser methodsFor: 'initialization' stamp: 'HilaireFernandes 9/17/2013 22:32'! openAsMorphClassEditing: editString "Create a pluggable version a Browser on just a single class." | window dragNDropFlag hSepFrac switchHeight mySingletonClassList | window := (SystemWindow labelled: 'later') model: self. dragNDropFlag := true. hSepFrac := 0.3. switchHeight := 25. mySingletonClassList := PluggableListMorph on: self list: #classListSingleton selected: #indexIsOne changeSelected: #indexIsOne: menu: #classListMenu:shifted: keystroke: #classListKey:from:. mySingletonClassList enableDragNDrop: dragNDropFlag. self addLowerPanesTo: window at: (0@hSepFrac corner: 1@1) with: editString. window addMorph: mySingletonClassList fullFrame: ((0@0 corner: 0.5@0) asLayoutFrame bottomOffset: switchHeight). self addMorphicSwitchesTo: window at: ((0.5@0 corner: 1.0@0) asLayoutFrame bottomOffset: switchHeight). window addMorph: self buildMorphicMessageCatList fullFrame: ((0@0 corner: 0.5@hSepFrac) asLayoutFrame topOffset: switchHeight). window addMorph: self buildMorphicMessageList fullFrame: ((0.5@0 corner: 1.0@hSepFrac) asLayoutFrame topOffset: switchHeight). window setUpdatablePanesFrom: #(messageCategoryList messageList). ^ window! !
Re: [Pharo-dev] Pharo on Raspberry
On 17 Sep 2013, at 20:23, Stéphane Ducasse wrote: > Is there any pointer on how to get Pharo on raspberry? > > Stef Pharo 1.4 runs fine with the squeak VM that comes with the standard Raspberry Pi OS, Rasbian. Higher Pharo versions need a Pharo specific VM AFAICT.
[Pharo-dev] Pharo on Raspberry
Is there any pointer on how to get Pharo on raspberry? Stef
Re: [Pharo-dev] Smalltalkhub => 503
Hi! It's up again. Mongo was down for some reason, I'm looking at it now. Sorry for the inconvenience, Nico 2013/9/17 Guillermo Polito > it's down and I need to commit!! >
Re: [Pharo-dev] Issues trying to use NewList on Nautilus
A note about click and control/alt. Now for unix system the command in mac is equivalent to the alt key. Particularry alt + click are catched by the os (to do some fancy windows moves). So what works in mac as command + click is mapped in unix as alt + click. 2013/9/17 Benjamin > If you want to react to some selection, you should better use > whenSelectedItemChanged: I guess > > Ben > > On Sep 17, 2013, at 4:00 AM, Nicolas Passerini > wrote: > > > If your UI is based on multi selection (and Nautilus definitely is) you >> should not register to whenSelectedIndexChanged:/whenSelectedItemChanged:, >> but only the plural version. >> > > Ok, I get that. > Still, when you create a NewList you have to provide a setIndexSelector, > for example in the CategoryWidget I am doing: > > categoriesList := NewList > on: self > getItemsSelector: #getCategories > setIndexSelector: #selectedCategoryIndex: > getDisplaySelector: #categoryWrapper:. > > So, every time you click on the categories list (both selecting multiple > categories or not) the CategoryWidget receives the #selectedCategoryIndex: > message. > The current selectedCategoryIndex: message reads like this: > > selectedCategoryIndex: anInteger > > | anObject | > anObject := self getCategories at: anInteger ifAbsent: [ nil ]. > self model selectedCategory: anObject. > self changed: #selectedCategoryIndex. > self model categorySelectionChanged. > self model changed: #currentHistoryIndex. > > > Also the NewList is in the list of dependents of the CategoryWidget, so it > also gets the #update: message > Is this right? > > >
Re: [Pharo-dev] Issues trying to use NewList on Nautilus
If you want to react to some selection, you should better use whenSelectedItemChanged: I guess Ben On Sep 17, 2013, at 4:00 AM, Nicolas Passerini wrote: > > If your UI is based on multi selection (and Nautilus definitely is) you > should not register to whenSelectedIndexChanged:/whenSelectedItemChanged:, > but only the plural version. > > Ok, I get that. > Still, when you create a NewList you have to provide a setIndexSelector, for > example in the CategoryWidget I am doing: > > categoriesList := NewList > on: self > getItemsSelector: #getCategories > setIndexSelector: #selectedCategoryIndex: > getDisplaySelector: #categoryWrapper:. > > So, every time you click on the categories list (both selecting multiple > categories or not) the CategoryWidget receives the #selectedCategoryIndex: > message. > The current selectedCategoryIndex: message reads like this: > > selectedCategoryIndex: anInteger > > | anObject | > anObject := self getCategories at: anInteger ifAbsent: [ nil ]. > self model selectedCategory: anObject. > > self changed: #selectedCategoryIndex. > self model categorySelectionChanged. > self model changed: #currentHistoryIndex. > > > Also the NewList is in the list of dependents of the CategoryWidget, so it > also gets the #update: message > Is this right?
Re: [Pharo-dev] Smalltalkhub => 503
Thanksss :) On Tue, Sep 17, 2013 at 5:32 PM, nicolas petton wrote: > Hi! > > It's up again. Mongo was down for some reason, I'm looking at it now. > > Sorry for the inconvenience, > Nico > > > 2013/9/17 Guillermo Polito > >> it's down and I need to commit!! >> > >
[Pharo-dev] Smalltalkhub down?
We noticed smalltalkhub is currently down. We have been generating some load, walking smalltalkhub a bit today, to see how we could get access to the latest versions of all packages. That should help us determine which projects use deprecated methods. Diego & Stephan
[Pharo-dev] Smalltalkhub => 503
it's down and I need to commit!!
Re: [Pharo-dev] Please help us by buying the book
On Tue, Sep 17, 2013 at 3:18 PM, Cédrick Béler wrote: > Just ordered too... thank you very much Cédrick. It's cool you are still around! -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
Re: [Pharo-dev] Please help us by buying the book
Just ordered too... Thanks a lot for the hard work. Cédrick Le 16 sept. 2013 à 22:48, David T. Lewis a écrit : > On Mon, Sep 16, 2013 at 04:24:07PM +0200, Damien Cassou 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. >> > > Thanks, I just ordered my copy of the hard copy book. > > Dave > >
[Pharo-dev] Fwd: Athens HTML5 canvas
>Hi Igor, >Where can I find an updated page to compile Pharo on the Raspberry ? >Best regards >Annick I don't know any details regarding Raspberry. I hope Pavel (or others) know better. -- Best regards, Igor Stasenko.
Re: [Pharo-dev] Understand Icons in Pharo
Thank you Fernado , you definitely made my life easier. I think I begin to understand how the whole thing work. Will concetrate now in reading the code to get a very solid idea. -- View this message in context: http://forum.world.st/Understand-Icons-in-Pharo-tp4708501p4708750.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/506/ 3 regressions found. FuelTests.FLMethodContextSerializationTest.testDoIt Tests.Release.ReleaseTest.testObsoleteBehaviors Tests.Release.ReleaseTest.testObsoleteClasses
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/506/ 3 regressions found. FuelTests.FLMethodContextSerializationTest.testDoIt Tests.Release.ReleaseTest.testObsoleteBehaviors Tests.Release.ReleaseTest.testObsoleteClasses
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=linux-stable-worker/506/ 3 regressions found. FuelTests.FLMethodContextSerializationTest.testDoIt Tests.Release.ReleaseTest.testObsoleteBehaviors Tests.Release.ReleaseTest.testObsoleteClasses
[Pharo-dev] [update 3.0] #30405
30405 - 11618 Introduce KMMetaModifier and KMUntypeableSingleKeyCombination https://pharo.fogbugz.com/f/cases/11618 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Keymapping-KeyCombinations-MarcusDenker.19.diff signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [Pharo-dev] scripts for automating the moose release
Yes this is really nice. I still have on my todo the private project handling. And I will get there. > Hi, > > I wrote a little blog post describing the process of releasing Moose: > http://www.humane-assessment.com/blog/automating-moose-4-8-release > > Perhaps this might be useful for others. And perhaps we can find ways to > improve it. > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "The coherence of a trip is given by the clearness of the goal." > > > > >
Re: [Pharo-dev] Please help us by buying the book
On Sep 17, 2013, at 9:02 AM, Damien Cassou wrote: > On Tue, Sep 17, 2013 at 12:22 AM, kilon wrote: >> how long for the amazon version ? I am Greek and I am not sure if the first >> choice delivers here. > > lulu delivers everywhere (including in Europe). Jannik, what is the > status of the amazon process? It takes 6-8 weeks to be available on Amazon. Just wait a bit, we will announce it when it will be there. Best, Jannik > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill
Re: [Pharo-dev] Please help us by buying the book
On Tue, Sep 17, 2013 at 12:22 AM, kilon wrote: > how long for the amazon version ? I am Greek and I am not sure if the first > choice delivers here. lulu delivers everywhere (including in Europe). Jannik, what is the status of the amazon process? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
Re: [Pharo-dev] Please help us by buying the book
On Mon, Sep 16, 2013 at 10:48 PM, David T. Lewis wrote: > Thanks, I just ordered my copy of the hard copy book. Thank you very much David. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
