March 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Settings browser

by Peter UhnÃ¡k

Hi, take a look at WidgetExamples class>>exampleBasicControls one of the inputs is a morph drop list. Peter On Tue, Mar 24, 2015 at 6:02 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Hello, > > From the settings browser, I want a drop list populated with morph of my > choice; for example coloured rectangle morphs: I want the user to select > a colour from such a predefined set and not from a text list. > > I did not find it is possible. Did I miss something ? > > > > (aBuilder pickOne: #pointColor) > label: 'Colour' translated; > description: 'The default point colour.'; > default: #red; > domainValues: {#red->Color red asMorph . > #black-> Color black asMorph}]. > > Thanks > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istoa.drgeo.eu > > > >

March 24, 2015

Re: [Pharo-users] Question about loading Roassal2 in Pharo4

by Andrei Chis

Use: Gofer new smalltalkhubUser: 'Moose' project: 'Glamour'; package: 'Glamour-Tools'; package: 'Glamour-Roassal2-Presentations'; load On Tue, Mar 24, 2015 at 6:15 PM, Javier PimÃ¡s <elpochodelagente(a)gmail.com> wrote: > Loading Glamour-Tools was ok with: > > Gofer new > smalltalkhubUser: 'Moose' project: 'GToolkit'; > package: 'Glamour-Tools'; > load > > Yet, I don't know where to find Glamour-Roassal2-Presentations package > > > On Mon, Mar 23, 2015 at 5:17 PM, Andrei Chis <chisvasileandrei(a)gmail.com> > wrote: > >> You should also load the packages Glamour-Tools >> and Glamour-Roassal2-Presentations from the Glamour repo. >> >> >> Cheers, >> Andrei >> >> On Mon, Mar 23, 2015 at 8:49 PM, Javier PimÃ¡s <elpochodelagente(a)gmail.com >> > wrote: >> >>> Hi guys, I see the same problem with latest pharo4. I loaded gt >>> extensions for roassal but now I get a message not understood when >>> selecting the examples. I'm loading roassal and the extensions with >>> >>> Gofer it >>> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; >>> configurationOf: 'Roassal2'; >>> loadStable. >>> >>> Gofer new >>> smalltalkhubUser: 'Moose' project: 'GToolkit'; >>> package: 'GT-InspectorExtensions-CoreRoassal'; >>> load >>> >>> am I doing something wrong? >>> >>> Cheers >>> >>> On Thu, Jan 8, 2015 at 5:17 AM, stepharo <stepharo(a)free.fr> wrote: >>> >>>> You understand what I wrote in the Pharo vision document about the >>>> process that we should get automated and in place before >>>> really be fully modular. >>>> >>>> Stef >>>> >>>> Hi, >>>> >>>> Let's not panic :). >>>> >>>> The situation is like this: >>>> - in Pharo 4, we have ConfigurationOfGlamourCore loaded which does not >>>> have the Roassal2 presentation >>>> - to get the Roassal2 presentation, you have to load >>>> ConfigurationOfGlamour (so, the full Glamour) >>>> - an extra problem can come from the configurations in the image not >>>> being the latest versions so there can be loading incompatibilities due to >>>> that. That is why, for the current Moose jobs we load manually the latest >>>> versions of the ConfigurationOf* classes (fun). >>>> - then you can use the GT-InspectorExtensions-CoreRoassal >>>> >>>> >>>> This situation has to improve, but in the meantime, you can use the >>>> gtoolkit or the moose 5.1 image which already has everything loaded >>>> correctly. >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> On Wed, Jan 7, 2015 at 2:26 PM, Alexandre Bergel < >>>> alexandre.bergel(a)me.com> wrote: >>>> >>>>> You also need Glamour-Roassal2-Presentations. But the last version >>>>> does not seem to load. >>>>> >>>>> Any idea how to fix this situation? >>>>> >>>>> Cheers, >>>>> Alexandre >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> > On Jan 7, 2015, at 10:22 AM, Sven Van Caekenberghe <sven(a)stfx.eu> >>>>> wrote: >>>>> > >>>>> > Thx. >>>>> > >>>>> > I loaded GT-InspectorExtensions-CoreRoassal-AndreiChis.25 >>>>> > >>>>> > but then I get >>>>> > >>>>> > Author: SvenVanCaekenberghe >>>>> > Date: 2015-01-07T14:20:37.659713+01:00 >>>>> > >>>>> > GLMCompositePresentation(Object)>>doesNotUnderstand: #roassal2 >>>>> > RTView>>gtInspectorViewIn: >>>>> > [ :eachPragma | >>>>> > (eachPragma selector findTokens: $:) size = 1 >>>>> > ifTrue: [ self perform: eachPragma selector with: composite ]. >>>>> > (eachPragma selector findTokens: $:) size = 2 >>>>> > ifTrue: [ self perform: eachPragma selector with: composite >>>>> with: aGTInspector ] ] in >>>>> RTView(Object)>>gtInspectorPresentationsIn:inContext: >>>>> > Array(SequenceableCollection)>>do: >>>>> > RTView(Object)>>gtInspectorPresentationsIn:inContext: >>>>> > [ :d | each gtInspectorPresentationsIn: d inContext: self ] in [ :x >>>>> | (GLMCompositePresentation new with: [ :d | each >>>>> gtInspectorPresentationsIn: d inContext: self ]) startOn: x ] in [ :a :each >>>>> | >>>>> > a title: [ self printObjectAsAnItem: each ]. >>>>> > a dynamicActions: [ :aPresentation | each gtInspectorActions >>>>> asOrderedCollection ]. >>>>> > a titleAction: [ :aPresentation | self closeActionFor: aPresentation >>>>> ]. >>>>> > a dynamic >>>>> > display: [ :x | (GLMCompositePresentation new with: [ :d | >>>>> each gtInspectorPresentationsIn: d inContext: self ]) startOn: x ] ] in [ >>>>> :browser | >>>>> > browser fixedSizePanes: self class numberOfInspectorPanes. >>>>> > browser >>>>> > show: [ :a :each | >>>>> > a title: [ self printObjectAsAnItem: each ]. >>>>> > a dynamicActions: [ :aPresentation | each >>>>> gtInspectorActions asOrderedCollection ]. >>>>> > a titleAction: [ :aPresentation | self closeActionFor: >>>>> aPresentation ]. >>>>> > a dynamic >>>>> > display: [ :x | (GLMCompositePresentation new >>>>> with: [ :d | each gtInspectorPresentationsIn: d inContext: self ]) startOn: >>>>> x ] ] ] in GTInspector>>compose >>>>> > GLMCompositePresentation(GLMPresentation)>>with: >>>>> > [ :x | (GLMCompositePresentation new with: [ :d | each >>>>> gtInspectorPresentationsIn: d inContext: self ]) startOn: x ] in [ :a :each >>>>> | >>>>> > a title: [ self printObjectAsAnItem: each ]. >>>>> > a dynamicActions: [ :aPresentation | each gtInspectorActions >>>>> asOrderedCollection ]. >>>>> > a titleAction: [ :aPresentation | self closeActionFor: aPresentation >>>>> ]. >>>>> > a dynamic >>>>> > display: [ :x | (GLMCompositePresentation new with: [ :d | >>>>> each gtInspectorPresentationsIn: d inContext: self ]) startOn: x ] ] in [ >>>>> :browser | >>>>> > browser fixedSizePanes: self class numberOfInspectorPanes. >>>>> > browser >>>>> > show: [ :a :each | >>>>> > a title: [ self printObjectAsAnItem: each ]. >>>>> > a dynamicActions: [ :aPresentation | each >>>>> gtInspectorActions asOrderedCollection ]. >>>>> > a titleAction: [ :aPresentation | self closeActionFor: >>>>> aPresentation ]. >>>>> > a dynamic >>>>> > display: [ :x | (GLMCompositePresentation new >>>>> with: [ :d | each gtInspectorPresentationsIn: d inContext: self ]) startOn: >>>>> x ] ] ] in GTInspector>>compose >>>>> > BlockClosure>>glamourValueWithArgs: >>>>> > BlockClosure(Object)>>glamourValue: >>>>> > GLMDynamicPresentation(GLMPresentation)>>displayValue >>>>> > GLMDynamicPresentation>>currentPresentation >>>>> > GLMMorphicDynamicRenderer>>render: >>>>> > GLMMorphicDynamicRenderer class(GLMMorphicWidgetRenderer >>>>> class)>>render:from: >>>>> > GLMMorphicRenderer>>renderDynamicPresentation: >>>>> > GLMDynamicPresentation>>renderGlamorouslyOn: >>>>> > GLMMorphicRenderer(GLMRenderer)>>render: >>>>> > GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderObject: >>>>> > >>>>> GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderWithTitleOrNil: >>>>> > GLMMorphicTabbedRenderer>>render: >>>>> > GLMMorphicTabbedRenderer class(GLMMorphicWidgetRenderer >>>>> class)>>render:from: >>>>> > GLMMorphicRenderer>>renderTabbedCompositePresentation: >>>>> > GLMTabbedArrangement>>renderGlamorouslyOn: >>>>> > GLMCompositePresentation>>renderGlamorouslyOn: >>>>> > GLMMorphicRenderer(GLMRenderer)>>render: >>>>> > GLMMorphicPaneRenderer(GLMMorphicWidgetRenderer)>>renderObject: >>>>> > GLMMorphicPaneRenderer>>renderContainerFor: >>>>> > GLMMorphicPaneRenderer>>render: >>>>> > GLMMorphicPaneRenderer class(GLMMorphicWidgetRenderer >>>>> class)>>render:from: >>>>> > GLMMorphicRenderer>>renderPane: >>>>> > GLMPane>>renderGlamorouslyOn: >>>>> > GLMMorphicRenderer(GLMRenderer)>>render: >>>>> > GLMMorphicPagerRenderer(GLMMorphicWidgetRenderer)>>renderObject: >>>>> > GLMMorphicPagerRenderer>>actOnPaneReplaced: >>>>> > MessageSend>>value: >>>>> > MessageSend>>cull: >>>>> > MessageSend>>cull:cull: >>>>> > [ action cull: anAnnouncement cull: announcer ] in >>>>> AnnouncementSubscription>>deliver: >>>>> > BlockClosure>>on:do: >>>>> > [ Processor terminateActive ] in on: exception fork: handlerAction >>>>> > "Activate the receiver. In case of exception, fork a new >>>>> process, which will handle an error. >>>>> > An original process will continue running as if receiver >>>>> evaluation finished and answered nil, >>>>> > i.e., an expression like: >>>>> > >>>>> > [ self error: 'some error'] on: Error fork: [:ex | 123 ] >>>>> > >>>>> > will always answer nil for original process, not 123. >>>>> > >>>>> > The context stack , starting from context which sent this >>>>> message to receiver and >>>>> > up to the top of the stack will be transferred to forked >>>>> process, with handlerAction on top. >>>>> > (so when the forked process will be resuming, it will enter >>>>> the handlerAction) >>>>> > " >>>>> > >>>>> > ^ self >>>>> > on: exception >>>>> > do: [ :ex | >>>>> > | copy onDoCtx process handler bottom thisCtx | >>>>> > onDoCtx := thisContext. >>>>> > thisCtx := onDoCtx home. "find the >>>>> context on stack for which this method's is sender" >>>>> > [ onDoCtx sender == thisCtx ] >>>>> > whileFalse: [ >>>>> > onDoCtx := onDoCtx sender. >>>>> > onDoCtx >>>>> > ifNil: [ >>>>> > "Can't find >>>>> our home context. seems like we're already forked >>>>> > and handling another exception in new >>>>> thread. In this case, just pass it through handler." >>>>> > ^ >>>>> handlerAction cull: ex ] ]. >>>>> > bottom := [ Processor terminateActive ] >>>>> asContext. >>>>> > onDoCtx privSender: bottom. >>>>> > handler := [ handlerAction cull: ex ] >>>>> asContext. >>>>> > handler privSender: thisContext sender. >>>>> > (Process forContext: handler priority: >>>>> Processor activePriority) resume. "cut the stack of current process" >>>>> > thisContext privSender: thisCtx. >>>>> > nil ] in BlockClosure>>on:fork: >>>>> > >>>>> >> On 07 Jan 2015, at 14:15, Andrei Chis <chisvasileandrei(a)gmail.com> >>>>> wrote: >>>>> >> >>>>> >> Hi, >>>>> >> >>>>> >> There is one extra package that you need to load from the GToolkit >>>>> repository: GT-InspectorExtensions-CoreRoassal >>>>> >> It contains all the inspector extensions that depend on roassal and >>>>> thus cannot be integrated into Pharo. >>>>> >> >>>>> >> >>>>> >> Cheers, >>>>> >> Andrei >>>>> >> >>>>> >> On Wed, Jan 7, 2015 at 1:35 PM, Sven Van Caekenberghe <sven(a)stfx.eu> >>>>> wrote: >>>>> >> Hi, >>>>> >> >>>>> >> I just loaded Roassal2 in Pharo4 using the following expression: >>>>> >> >>>>> >> Gofer it >>>>> >> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; >>>>> >> configurationOf: 'Roassal2'; >>>>> >> loadStable. >>>>> >> >>>>> >> When I try one of the examples I see that I am missing some GT >>>>> presentations specific to Roassal. How should I load those ? >>>>> >> >>>>> >> <Screen Shot 2015-01-07 at 13.34.11.png> >>>>> >> >>>>> >> Thx, >>>>> >> >>>>> >> Sven >>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>>> > >>>>> > >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Every thing has its own flow" >>>> >>>> >>>> >>> >>> >>> -- >>> Javier PimÃ¡s >>> Ciudad de Buenos Aires >>> >> >> > > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires >

March 24, 2015

Re: [Pharo-users] Question about loading Roassal2 in Pharo4

by Javier PimÃ¡s

Loading Glamour-Tools was ok with: Gofer new smalltalkhubUser: 'Moose' project: 'GToolkit'; package: 'Glamour-Tools'; load Yet, I don't know where to find Glamour-Roassal2-Presentations package On Mon, Mar 23, 2015 at 5:17 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > You should also load the packages Glamour-Tools > and Glamour-Roassal2-Presentations from the Glamour repo. > > > Cheers, > Andrei > > On Mon, Mar 23, 2015 at 8:49 PM, Javier PimÃ¡s <elpochodelagente(a)gmail.com> > wrote: > >> Hi guys, I see the same problem with latest pharo4. I loaded gt >> extensions for roassal but now I get a message not understood when >> selecting the examples. I'm loading roassal and the extensions with >> >> Gofer it >> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; >> configurationOf: 'Roassal2'; >> loadStable. >> >> Gofer new >> smalltalkhubUser: 'Moose' project: 'GToolkit'; >> package: 'GT-InspectorExtensions-CoreRoassal'; >> load >> >> am I doing something wrong? >> >> Cheers >> >> On Thu, Jan 8, 2015 at 5:17 AM, stepharo <stepharo(a)free.fr> wrote: >> >>> You understand what I wrote in the Pharo vision document about the >>> process that we should get automated and in place before >>> really be fully modular. >>> >>> Stef >>> >>> Hi, >>> >>> Let's not panic :). >>> >>> The situation is like this: >>> - in Pharo 4, we have ConfigurationOfGlamourCore loaded which does not >>> have the Roassal2 presentation >>> - to get the Roassal2 presentation, you have to load >>> ConfigurationOfGlamour (so, the full Glamour) >>> - an extra problem can come from the configurations in the image not >>> being the latest versions so there can be loading incompatibilities due to >>> that. That is why, for the current Moose jobs we load manually the latest >>> versions of the ConfigurationOf* classes (fun). >>> - then you can use the GT-InspectorExtensions-CoreRoassal >>> >>> >>> This situation has to improve, but in the meantime, you can use the >>> gtoolkit or the moose 5.1 image which already has everything loaded >>> correctly. >>> >>> Cheers, >>> Doru >>> >>> >>> On Wed, Jan 7, 2015 at 2:26 PM, Alexandre Bergel < >>> alexandre.bergel(a)me.com> wrote: >>> >>>> You also need Glamour-Roassal2-Presentations. But the last version does >>>> not seem to load. >>>> >>>> Any idea how to fix this situation? >>>> >>>> Cheers, >>>> Alexandre >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> > On Jan 7, 2015, at 10:22 AM, Sven Van Caekenberghe <sven(a)stfx.eu> >>>> wrote: >>>> > >>>> > Thx. >>>> > >>>> > I loaded GT-InspectorExtensions-CoreRoassal-AndreiChis.25 >>>> > >>>> > but then I get >>>> > >>>> > Author: SvenVanCaekenberghe >>>> > Date: 2015-01-07T14:20:37.659713+01:00 >>>> > >>>> > GLMCompositePresentation(Object)>>doesNotUnderstand: #roassal2 >>>> > RTView>>gtInspectorViewIn: >>>> > [ :eachPragma | >>>> > (eachPragma selector findTokens: $:) size = 1 >>>> > ifTrue: [ self perform: eachPragma selector with: composite ]. >>>> > (eachPragma selector findTokens: $:) size = 2 >>>> > ifTrue: [ self perform: eachPragma selector with: composite >>>> with: aGTInspector ] ] in >>>> RTView(Object)>>gtInspectorPresentationsIn:inContext: >>>> > Array(SequenceableCollection)>>do: >>>> > RTView(Object)>>gtInspectorPresentationsIn:inContext: >>>> > [ :d | each gtInspectorPresentationsIn: d inContext: self ] in [ :x | >>>> (GLMCompositePresentation new with: [ :d | each gtInspectorPresentationsIn: >>>> d inContext: self ]) startOn: x ] in [ :a :each | >>>> > a title: [ self printObjectAsAnItem: each ]. >>>> > a dynamicActions: [ :aPresentation | each gtInspectorActions >>>> asOrderedCollection ]. >>>> > a titleAction: [ :aPresentation | self closeActionFor: aPresentation >>>> ]. >>>> > a dynamic >>>> > display: [ :x | (GLMCompositePresentation new with: [ :d | each >>>> gtInspectorPresentationsIn: d inContext: self ]) startOn: x ] ] in [ >>>> :browser | >>>> > browser fixedSizePanes: self class numberOfInspectorPanes. >>>> > browser >>>> > show: [ :a :each | >>>> > a title: [ self printObjectAsAnItem: each ]. >>>> > a dynamicActions: [ :aPresentation | each >>>> gtInspectorActions asOrderedCollection ]. >>>> > a titleAction: [ :aPresentation | self closeActionFor: >>>> aPresentation ]. >>>> > a dynamic >>>> > display: [ :x | (GLMCompositePresentation new >>>> with: [ :d | each gtInspectorPresentationsIn: d inContext: self ]) startOn: >>>> x ] ] ] in GTInspector>>compose >>>> > GLMCompositePresentation(GLMPresentation)>>with: >>>> > [ :x | (GLMCompositePresentation new with: [ :d | each >>>> gtInspectorPresentationsIn: d inContext: self ]) startOn: x ] in [ :a :each >>>> | >>>> > a title: [ self printObjectAsAnItem: each ]. >>>> > a dynamicActions: [ :aPresentation | each gtInspectorActions >>>> asOrderedCollection ]. >>>> > a titleAction: [ :aPresentation | self closeActionFor: aPresentation >>>> ]. >>>> > a dynamic >>>> > display: [ :x | (GLMCompositePresentation new with: [ :d | each >>>> gtInspectorPresentationsIn: d inContext: self ]) startOn: x ] ] in [ >>>> :browser | >>>> > browser fixedSizePanes: self class numberOfInspectorPanes. >>>> > browser >>>> > show: [ :a :each | >>>> > a title: [ self printObjectAsAnItem: each ]. >>>> > a dynamicActions: [ :aPresentation | each >>>> gtInspectorActions asOrderedCollection ]. >>>> > a titleAction: [ :aPresentation | self closeActionFor: >>>> aPresentation ]. >>>> > a dynamic >>>> > display: [ :x | (GLMCompositePresentation new >>>> with: [ :d | each gtInspectorPresentationsIn: d inContext: self ]) startOn: >>>> x ] ] ] in GTInspector>>compose >>>> > BlockClosure>>glamourValueWithArgs: >>>> > BlockClosure(Object)>>glamourValue: >>>> > GLMDynamicPresentation(GLMPresentation)>>displayValue >>>> > GLMDynamicPresentation>>currentPresentation >>>> > GLMMorphicDynamicRenderer>>render: >>>> > GLMMorphicDynamicRenderer class(GLMMorphicWidgetRenderer >>>> class)>>render:from: >>>> > GLMMorphicRenderer>>renderDynamicPresentation: >>>> > GLMDynamicPresentation>>renderGlamorouslyOn: >>>> > GLMMorphicRenderer(GLMRenderer)>>render: >>>> > GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderObject: >>>> > >>>> GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderWithTitleOrNil: >>>> > GLMMorphicTabbedRenderer>>render: >>>> > GLMMorphicTabbedRenderer class(GLMMorphicWidgetRenderer >>>> class)>>render:from: >>>> > GLMMorphicRenderer>>renderTabbedCompositePresentation: >>>> > GLMTabbedArrangement>>renderGlamorouslyOn: >>>> > GLMCompositePresentation>>renderGlamorouslyOn: >>>> > GLMMorphicRenderer(GLMRenderer)>>render: >>>> > GLMMorphicPaneRenderer(GLMMorphicWidgetRenderer)>>renderObject: >>>> > GLMMorphicPaneRenderer>>renderContainerFor: >>>> > GLMMorphicPaneRenderer>>render: >>>> > GLMMorphicPaneRenderer class(GLMMorphicWidgetRenderer >>>> class)>>render:from: >>>> > GLMMorphicRenderer>>renderPane: >>>> > GLMPane>>renderGlamorouslyOn: >>>> > GLMMorphicRenderer(GLMRenderer)>>render: >>>> > GLMMorphicPagerRenderer(GLMMorphicWidgetRenderer)>>renderObject: >>>> > GLMMorphicPagerRenderer>>actOnPaneReplaced: >>>> > MessageSend>>value: >>>> > MessageSend>>cull: >>>> > MessageSend>>cull:cull: >>>> > [ action cull: anAnnouncement cull: announcer ] in >>>> AnnouncementSubscription>>deliver: >>>> > BlockClosure>>on:do: >>>> > [ Processor terminateActive ] in on: exception fork: handlerAction >>>> > "Activate the receiver. In case of exception, fork a new >>>> process, which will handle an error. >>>> > An original process will continue running as if receiver >>>> evaluation finished and answered nil, >>>> > i.e., an expression like: >>>> > >>>> > [ self error: 'some error'] on: Error fork: [:ex | 123 ] >>>> > >>>> > will always answer nil for original process, not 123. >>>> > >>>> > The context stack , starting from context which sent this >>>> message to receiver and >>>> > up to the top of the stack will be transferred to forked >>>> process, with handlerAction on top. >>>> > (so when the forked process will be resuming, it will enter the >>>> handlerAction) >>>> > " >>>> > >>>> > ^ self >>>> > on: exception >>>> > do: [ :ex | >>>> > | copy onDoCtx process handler bottom thisCtx | >>>> > onDoCtx := thisContext. >>>> > thisCtx := onDoCtx home. "find the >>>> context on stack for which this method's is sender" >>>> > [ onDoCtx sender == thisCtx ] >>>> > whileFalse: [ >>>> > onDoCtx := onDoCtx sender. >>>> > onDoCtx >>>> > ifNil: [ >>>> > "Can't find our >>>> home context. seems like we're already forked >>>> > and handling another exception in new >>>> thread. In this case, just pass it through handler." >>>> > ^ handlerAction >>>> cull: ex ] ]. >>>> > bottom := [ Processor terminateActive ] >>>> asContext. >>>> > onDoCtx privSender: bottom. >>>> > handler := [ handlerAction cull: ex ] asContext. >>>> > handler privSender: thisContext sender. >>>> > (Process forContext: handler priority: >>>> Processor activePriority) resume. "cut the stack of current process" >>>> > thisContext privSender: thisCtx. >>>> > nil ] in BlockClosure>>on:fork: >>>> > >>>> >> On 07 Jan 2015, at 14:15, Andrei Chis <chisvasileandrei(a)gmail.com> >>>> wrote: >>>> >> >>>> >> Hi, >>>> >> >>>> >> There is one extra package that you need to load from the GToolkit >>>> repository: GT-InspectorExtensions-CoreRoassal >>>> >> It contains all the inspector extensions that depend on roassal and >>>> thus cannot be integrated into Pharo. >>>> >> >>>> >> >>>> >> Cheers, >>>> >> Andrei >>>> >> >>>> >> On Wed, Jan 7, 2015 at 1:35 PM, Sven Van Caekenberghe <sven(a)stfx.eu> >>>> wrote: >>>> >> Hi, >>>> >> >>>> >> I just loaded Roassal2 in Pharo4 using the following expression: >>>> >> >>>> >> Gofer it >>>> >> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; >>>> >> configurationOf: 'Roassal2'; >>>> >> loadStable. >>>> >> >>>> >> When I try one of the examples I see that I am missing some GT >>>> presentations specific to Roassal. How should I load those ? >>>> >> >>>> >> <Screen Shot 2015-01-07 at 13.34.11.png> >>>> >> >>>> >> Thx, >>>> >> >>>> >> Sven >>>> >> >>>> >> >>>> >> >>>> >> >>>> > >>>> > >>>> >>>> >>>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >>> >>> >>> >> >> >> -- >> Javier PimÃ¡s >> Ciudad de Buenos Aires >> > > -- Javier PimÃ¡s Ciudad de Buenos Aires

March 24, 2015

Settings browser

by Hilaire

Hello, >From the settings browser, I want a drop list populated with morph of my choice; for example coloured rectangle morphs: I want the user to select a colour from such a predefined set and not from a text list. I did not find it is possible. Did I miss something ? (aBuilder pickOne: #pointColor) label: 'Colour' translated; description: 'The default point colour.'; default: #red; domainValues: {#red->Color red asMorph . #black-> Color black asMorph}]. Thanks -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

March 24, 2015

Re: [Pharo-users] Using Google service discovery API's with Pharo Smalltalk by Richard J. Prinz

by Andy Burnett

Sven wrote <<< I hadn't seen this posted on the mailing list, but this is really cool stuff. Using Google service discovery API's with Pharo Smalltalk by Richard J. Prinz http://www.min.at/prinz/?x=entry:entry150318-104537 < http://www.min.at/prinz/?x=entry:entry150318-104537;comments:1#comments> >>> I totally agree with this. I have played with the code, and started writing some code which manipulates the Google services. It is really powerful. Also, Richard has developed a slick way of dealing with OAuth when running a client app. This is great!

March 24, 2015

Re: [Pharo-users] new link to query all projects in smalltalkhub

by Merwan Ouddane

Thanks for the instructions, I'll do it as soon as I can :) There is an issue that i'd like to report too, I have a team with a non-ascii character, and i can't remove team members nor delete the entire team, I'll try to fix it too. Merwan On 24/03/2015 11:55, Stephan Eggermont wrote: > On 24/03/15 11:18, Merwan Oud wrote: >> If the list is reduced it will be manageable, maybe not a mouseOver but >> a little arrow to show/hide the description under the project. > > We would love submissions of code for this. It is something that should > not be very difficult, but takes some time to get right. If you want > to try this: > - install and run mongodb > - download and run a smalltalkhub image from > https://ci.inria.fr/pharo-contribution/job/SmalltalkHub/ > (latest green 3.0 development version) > - add yourself as user on your local smalltalkhub > (http://localhost:8080/tools/hub) > - add some projects to test this with > - save some code to it from another image > - take a look in the image at the Hub and HubExtra > packages. You can see what was changed by browsing > changes with earlier versions on > http://smalltalkhub.com/mc/NicolasPetton/SmalltalkHub/main > - change the rendering code so it works as you like it. > Torsten suggested to use http://www.datatables.net/ > Please remember that we need a solution that works with > a large number of projects, so we might have to limit > sizes. > - you should be able to commit directly to the repo. > - please keep us posted on any problems and interesting > features/issues or questions. > - if you want to show us something that might not be ready, > you (or I) can add an extra build to the ci server. > > At the moment, Esteban is far too busy with higher priority work: > - Pharo 4 release; > - new Spur VM; > - making retina displays work. > (probably not a complete list...) > > Stephan > > > >

March 24, 2015

Re: [Pharo-users] USB in Pharo?

by kilon alios

If the library is big you can use TalkFFI (you will find it in smalltalkhub) that automates the wrapping with nativeboost. On Tue, Mar 24, 2015 at 4:58 PM, Udo Schneider <Udo.Schneider(a)homeaddress.de > wrote: > I guess not :-) > > I'll try to wrap libUSB then. > > I assume the future-proof way to use "a" FFI framework is to use the NB > notation? Do I remember correctly that the NB notation is supposed to > remain the same although the backend will change to something more like > traditional FFI? > So using NB notation w/o relying on the code generation is safe, correct? > > CU, > > Udo > > > > On 23.03.2015 16:15, Udo Schneider wrote: > >> All, >> >> does anybody have some code or plugin to access USB ports with Pharo? >> Maybe something using libUSB or OpenUSB? >> >> Thanks, >> >> Udo >> >> >> >> > > >

March 24, 2015

Re: [Pharo-users] Boardician (board game framework)

by kilon alios

Well done Laura. I really enjoyed your games and I definitely welcome your documentation. I will give it a try , thank you . On Tue, Mar 24, 2015 at 4:41 PM, Laura Risani <laura.risani(a)gmail.com> wrote: > Hi all, > > A time ago i posted two board games on the list and StÃ©phane said that he > would like to extract from these and other ones he has gathered a framework > for doing board games. So i developed a little one called 'Boardician' and > implemented four little example games through it. > > DOCUMENTATION > http://boardician.blogspot.com.ar/2015/03/boardician.html > > DOWNLOAD <https://www.blogger.com/null> > You can install configuration BgBoardician from Configuration Browser on > 3.0 and 4.0 . This will download packages of framework (BgBoardician) and > example games (BgBoxPush, BgEatBullet, BgDropPiece, BgEatElongating) > > To run example games send > > EDirector new play. > BPDirector new play. > DPDirector new play. > GDirector new play. > > > FEEDBACK <https://www.blogger.com/null> > If you like (i would really like you to) to send any feedback comments on > design / names / implementation / functionalities to add / questions you > can post a comment on the blog / mail me. > > Next i'll be adding tests and uploading development history to project's > repo. > > Best, > Laura >

March 24, 2015

woden-roassal view increase size?

by Lusa Nicolas

Hi, I am working with woden-roassal and I noticed that re-sizing the OpenGL view screws up things that are displayed. Though I really would love to have a bigger view, I checked if in RWView and WDApplication there was something to make the OpenGL view larger from the beginning (so no need of resizing would be required) but I didn't manage to find anything that does such thing. Anyone knows where to look at? Cheers, Nicolas

March 24, 2015

Re: [Pharo-users] USB in Pharo?

by Udo Schneider

I guess not :-) I'll try to wrap libUSB then. I assume the future-proof way to use "a" FFI framework is to use the NB notation? Do I remember correctly that the NB notation is supposed to remain the same although the backend will change to something more like traditional FFI? So using NB notation w/o relying on the code generation is safe, correct? CU, Udo On 23.03.2015 16:15, Udo Schneider wrote: > All, > > does anybody have some code or plugin to access USB ports with Pharo? > Maybe something using libUSB or OpenUSB? > > Thanks, > > Udo > > >

March 24, 2015