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

Re: [Pharo-users] Package dependencies

by stepharo

Mmmm, since the project is just one package and the additional packages are examples, i'm writing for the moment a Gofer script instead. this means that it will not be loadable from the MetacelloBrowser, that it will not appear in the catalog..... Stef > Thank you! > > On Sun, Mar 22, 2015 at 1:53 PM, Thierry Goubier > <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: > > Le 22/03/2015 17:41, stepharo a Ã©crit : > > Defining a configuration for your project. > > > Even easier: define a BaselineOf for your project (a configuration > will have you write a baseline anyway). And use Metacello to load it. > > Thierry > > > You can have a look for example in the Mines configuration it > depends on > LedMorph > > Le 22/3/15 16:25, Laura Risani a Ã©crit : > > Hi all, > > What's the easiest way at the moment to make a package > when downloaded > from a repo automatically download others (which depend > only on core > system classes)? > > Best, > Laura > > > > > > >

March 23, 2015

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

by stepharo

> Hi Esteban, > > I don't know if you want to spend some time on it, but what would be > great is for the projects to choose if they want to appear or not in > this list, and have a little description of the project on mouse over :) :)

March 23, 2015

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

by Merwan Ouddane

Hi Esteban, I don't know if you want to spend some time on it, but what would be great is for the projects to choose if they want to appear or not in this list, and have a little description of the project on mouse over :) Merwan On 23/03/2015 14:01, Esteban Lorenzano wrote: >> On 22 Mar 2015, at 22:26, Julien Delplanque <julien(a)tamere.eu> wrote: >> >> Oh, yes i missed it sorry! >> >> It would be good to have a link somewhere on smalltalkhub that inform >> the existence of this resource :) > yes, you are rightâ¦ but I started the list as a side project precisely because I do not want to touch smalltalkhub :P > Anyway, I will see how to give some visibility somewayâ¦ but not this week, Iâm running with the release :) > > Esteban > >> Julien >> >> On 22/03/15 21:41, Esteban Lorenzano wrote: >>> yesâ¦ it is no more. >>> >>> now is http://smalltalkhub.com/list <http://smalltalkhub.com/list> >>> >>> sorry for the mess, but I announced the changeâ¦ you just missed it :P >>> >>> Esteban >>> >>>> On 22 Mar 2015, at 21:25, Julien Delplanque <julien(a)tamere.eu> wrote: >>>> >>>> Hi Esteban, >>>> >>>> Seems that the link is dead now? >>>> >>>> Regards, >>>> >>>> Julien >>>> >>>> >>>> >>>> -- >>>> View this message in context: http://forum.world.st/new-link-to-query-all-projects-in-smalltalkhub-tp4810… >>>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>>> >> >

March 23, 2015

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

by Andrei Chis

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 >

March 23, 2015

Re: [Pharo-users] [vwnc] The Grapher charting engine

by Alexandre Bergel

Hi! > If you're heading to make "Roassal the best visualizing engine of the Universe" then what are your intentions with connecting it to the outer world ? This is a rather broad question :-) While our visualizations are meant to run in a standard Smalltalk environment, they are exportable to HTML. Interaction are also preserved. Here are two simple examples: https://dl.dropboxusercontent.com/u/31543901/TMP/memoryBlueprintExample.html <https://dl.dropboxusercontent.com/u/31543901/TMP/memoryBlueprintExample.html> https://dl.dropboxusercontent.com/u/31543901/online/WebReport/seisms.html <https://dl.dropboxusercontent.com/u/31543901/online/WebReport/seisms.html> And a larger and more complex example is in the file https://dl.dropboxusercontent.com/u/31543901/TMP/ExampleReport.zip <https://dl.dropboxusercontent.com/u/31543901/TMP/ExampleReport.zip> check the file Example.pillar.html > Will it remain a multiplatform toolbox ? Or are you heading towards a BI desktop or Web app ? Roassal will remain closely linked to Smalltalk (VisualWorks & Pharo). Cheers, Alexandre > > Regards, > > Maarten MOSTERT > > > > 28 Av Alphonse Denis > 83400 HyÃ¨res, France > +33 676411296 > http://stakepoint.com/ <http://stakepoint.com/> > > > > > "Alexandre Bergel" <alexandre.bergel(a)me.com> | > > Dear all, > > As many of you know, Grapher is a Ã¼ber-cool charting engine, part of Roassal. > For people who do not know what Grapher is, here is a (compelling we hope) example: > <855A292C-DE42-4FF5-83ED-49477CDAA250.png> > Which is obtained by the following script: > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > | b colors points ds pts dec lb | > b := RTGrapher new. > colors := Array with: Color red with: Color blue. > points := OrderedCollection new. > > colors do: [ :c | > ds := RTStackedDataSet new. > pts := ((1 to: 100) collect: [ :i | 50 atRandom - 25 ]) cumsum. > points add: pts. > ds points: pts. > dec := RTDevVarDecorator new. > dec moveBehind; > desviation: 0.5; > color: (c alpha: 0.3); > points: pts. > ds connectUsing: (RTLine new color: (c alpha: 0.5); width: 1 ). > b add: ds. > b addDecorator: dec. > ]. > > b axisX; axisY. > b build. > > lb := RTLegendBuilder new. > lb view: b view. > colors doWithIndex: [ :c :i | > lb addColor: c text: 'Series ', i printString ]. > lb build. > b view @ RTZoomableView. > b view > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > > In our grand vision of making Roassal the best visualizing engine of the Universe (we also know to be modest time to time, but not today :-), Grapher will play a very important role. We would like to stabilize Grapher and make it sure it happily fits everybody needs. You can help on it: > > - When you are tempted to look at the dark side of the planet (this is where R, JFreeChart, gnuplot, D3 and all their friends live), let us know. We will make sure to make you are happy again. > > - Share your wishlist with us. We already have a long todo list, but your opinion does matter and will take it seriously > > - we are open to contributions, which could be financial, bug fixe, enhancement, or simply encouragement. > > I am very happy to be surrounded by very smart engineers. Your encouragement are making them happy :-) > > Cheers, > Alexandre, in the name of the Object Profile Team > NB: sorry for the cross-list posting, but this email is very important for us, and for you we hope. > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > <855A292C-DE42-4FF5-83ED-49477CDAA250.png>

March 23, 2015

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

by Javier PimÃ¡s

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

March 23, 2015

Re: [Pharo-users] [Moose-dev] loading Glamour in Pharo 4

by Johan Fabry

I think it is pretty telling that 2 different persons basically had the same issue in 3 days. Should this issue be considered as something to have fixed for the Pharo 4 release? > On Mar 23, 2015, at 14:53, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > There are several tools in Pharo that depend on Glamour. > If you update glamour to the latest version you also need to update the tools that depend on it. > > This script updated everything: > > { { 'ConfigurationOfRubric'. 'AlainPlantec'. 'Rubric' }. > { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. > { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. > { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. > { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. > { 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }. > } do: [ :spec | > Gofer new > smalltalkhubUser: spec second project: spec third; > package: spec first; > load ]. > ConfigurationOfGToolkitCore loadDevelopment. > > If you are interested just in the Roassal presented you could try and only load the package Glamour-Roassal2-Presentations + Roassal. > However, depending on what changes you might need to also update glamour. > > > Cheers, > Andrei > > > > On Mon, Mar 23, 2015 at 6:47 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>> wrote: > After loading Glamour dev in Pharo 40 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Gofer new > smalltalkhubUser: 'Moose' project: 'Glamour'; > package: 'ConfigurationOfGlamour'; > load. > (Smalltalk at: #ConfigurationOfGlamour) > perform: #loadDevelopment > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > when I try opening Playground I get > AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic: > > And Spotter throws > GLMHintableActionButtonBrick(Object)>>doesNotUnderstand: #addUpAction: > > Am I missing some extra dependency? > > Thanks, > Peter > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

March 23, 2015

Re: [Pharo-users] Package dependencies

by Laura Risani

Mmmm, since the project is just one package and the additional packages are examples, i'm writing for the moment a Gofer script instead. Thank you! On Sun, Mar 22, 2015 at 1:53 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Le 22/03/2015 17:41, stepharo a Ã©crit : > >> Defining a configuration for your project. >> > > Even easier: define a BaselineOf for your project (a configuration will > have you write a baseline anyway). And use Metacello to load it. > > Thierry > > > You can have a look for example in the Mines configuration it depends on >> LedMorph >> >> Le 22/3/15 16:25, Laura Risani a Ã©crit : >> >>> Hi all, >>> >>> What's the easiest way at the moment to make a package when downloaded >>> from a repo automatically download others (which depend only on core >>> system classes)? >>> >>> Best, >>> Laura >>> >> >> >> >> > >

March 23, 2015

Re: [Pharo-users] loading Glamour in Pharo 4

by Andrei Chis

There are several tools in Pharo that depend on Glamour. If you update glamour to the latest version you also need to update the tools that depend on it. This script updated everything: { { 'ConfigurationOfRubric'. 'AlainPlantec'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer new smalltalkhubUser: spec second project: spec third; package: spec first; load ]. ConfigurationOfGToolkitCore loadDevelopment. If you are interested just in the Roassal presented you could try and only load the package Glamour-Roassal2-Presentations + Roassal. However, depending on what changes you might need to also update glamour. Cheers, Andrei On Mon, Mar 23, 2015 at 6:47 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > After loading Glamour dev in Pharo 40 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Gofer new > smalltalkhubUser: 'Moose' project: 'Glamour'; > package: 'ConfigurationOfGlamour'; > load. > (Smalltalk at: #ConfigurationOfGlamour) > perform: #loadDevelopment > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > when I try opening Playground I get > AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic: > > And Spotter throws > GLMHintableActionButtonBrick(Object)>>doesNotUnderstand: #addUpAction: > > Am I missing some extra dependency? > > Thanks, > Peter >

March 23, 2015

Re: [Pharo-users] loading Glamour in Pharo 4

by Peter UhnÃ¡k

Also I am interested only in presenter for Roassal, is there separate configuration for that? On Mon, Mar 23, 2015 at 6:47 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > After loading Glamour dev in Pharo 40 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Gofer new > smalltalkhubUser: 'Moose' project: 'Glamour'; > package: 'ConfigurationOfGlamour'; > load. > (Smalltalk at: #ConfigurationOfGlamour) > perform: #loadDevelopment > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > when I try opening Playground I get > AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic: > > And Spotter throws > GLMHintableActionButtonBrick(Object)>>doesNotUnderstand: #addUpAction: > > Am I missing some extra dependency? > > Thanks, > Peter >

March 23, 2015