- Pharo-users - lists.pharo.org

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

by Sven Van Caekenberghe

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 > > > >

Jan. 7, 2015

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

by Alexandre Bergel

Hi Andrei, Iâve just checked, and the version Glamour-Roassal2-Presentations-TudorGirba.33 cannot be loaded in Pharo 4. Apparently in Pharo 4 Glamour is not updated. Glamour-Tools is missing in Pharo 4. But, Glamour is not updated in Roassal4 when there are some commit in the Glamour repository? How that can be? Glamour has been forked? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jan 7, 2015, at 10:15 AM, 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 <mailto:sven@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 > > > >

Jan. 7, 2015

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

by Andrei Chis

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 ? > > > Thx, > > Sven > > > >

Jan. 7, 2015

Re: [Pharo-users] Charting graphs

by Alexandre Bergel

Stef, I have updated the Grapher chapter in Agilevisualization: https://dl.dropboxusercontent.com/u/31543901/AgileVisualization/Grapher/020… You are now ready to blog :-) Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jan 6, 2015, at 2:49 PM, stepharo <stepharo(a)free.fr> wrote: > > Really really nice. > Continue to push Grapher and trying to reproduce "stupid" charts is the way to stress its design! > Do you have this description somewhere so that I can blog on it? > > Stef > > Le 5/1/15 00:22, Alexandre Bergel a Ã©crit : >> Hi! >> >> RTGraphBuilder went through major improvements. >> >> - min and max may be specified. >> >> - plugins to add some decoration (average line, standard deviation range, ticks lines, â¦) >> >> Here are some examples, with some examples, which should illustrate these points: >> <Mail Attachment.png> >> Is obtained with: >> -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= >> | b ds | >> b := RTGrapherBuilder new. >> >> ds := RTDataSet new. >> ds points: (0 to: 100 by: 0.1). >> ds y: [ :x | (0.1 * x) sin ]. >> ds noDot. >> ds interaction popupText: 'sinus'. >> ds connectColor: Color blue. >> b add: ds. >> >> ds := RTDataSet new. >> ds points: (0 to: 100 by: 0.1). >> ds y: [ :x | (0.2 * x) cos * 2 ]. >> ds noDot. >> ds interaction popupText: 'cosinus'. >> ds connectColor: Color red. >> b add: ds. >> >> b minY: -4. >> b maxY: 4. >> b minX: -25. >> >> b build. >> -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= >> >> >> <Mail Attachment.png> >> -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= >> >> b := RTGrapherBuilder new. >> >> ds := RTStackedDataSet new. >> ds interaction popup. >> ds points: #(600 470 170 430 300). >> ds barShape width: 20; color: Color lightGreen. >> b add: ds. >> >> b axisX noLabel; noTick. >> b axisY noDecimals. >> >> b addPlugin: RTMeanDevVarPlugin new. >> b build >> -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= >> >> Another example: >> <Mail Attachment.png> >> -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= >> b := RTGrapherBuilder new. >> b extent: 300 @ 200. >> >> 5 timesRepeat: [ >> ds := RTStackedDataSet new. >> ds noDot. >> ds points: ((1 to: 500) collect: [ :i | 50 atRandom - 25 ]) cumsum. >> ds connectColor: Color green. >> b add: ds. >> ]. >> >> b addPlugin: RTMeanDevVarPlugin new. >> b build. >> -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= >> >> The plugin framework exposes to a plugin all the necessary to define a whole range of decorations. For example, variable average lines, linear regression should be trivial to add... >> >> Happy new year! >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >

Jan. 7, 2015

Question about loading Roassal2 in Pharo4

by Sven Van Caekenberghe

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 ? Thx, Sven

Jan. 7, 2015

Re: [Pharo-users] [Moose-dev] [Pharo-dev] Charting graphs

by Alexandre Bergel

Hi Doru, > The API is interesting. As I see it, this will be limited to things like bar, plots or line graphs. For example, a spider chart will not work with this one, but it will use a builder of its own, right? Yes. Currently, spider chart shares very little from what we have. This is why it deserves its own builder. Maybe this will change in the future, but for now it works well. But the way, we call Kiviat what you call Spider chart. Just have a look at RTKiviatBuilder. Here is a screenshot for people who do not understand what we are talking about :-) > Some feedback: > - I would rename Plugin to Decorator. From your statement, "The plugin framework exposes to a plugin all the necessary to define a whole range of decorations" it seems to me that "Decorator" fits better. Yes! Done! > - I would just call the class RTGrapher Yes, done! > - I do not quite understand how to distinguish the difference between DataSet and StackedDataSet. Yeah, not easy to grasp. Consider an histogram and a scatter plot. You will define an histogram as a list of values, e.g,. 4, 5, 6, 7 You will define a scatterplot as a list of points, e.g., 2 @ 3, 5 @ 6, â¦ An histogram is obtained from a list of objects, and a function Y to obtain the values. A scatter plot is obtained from a list of objects, and _two_ functions X and Y to obtain the points. When you do not need to specify an X, e.g., an histogram, then you need a RTStackedDataSet. When you need to specify an X, e.g., a scatter plot, then you need a RTDataSet. Is it clear? Maybe the vocabulary we use is not obvious. Cheers, Alexandre > > Cheers, > Doru > > > > On Mon, Jan 5, 2015 at 12:22 AM, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: > Hi! > > RTGraphBuilder went through major improvements. > - min and max may be specified. > - plugins to add some decoration (average line, standard deviation range, ticks lines, â¦) > > Here are some examples, with some examples, which should illustrate these points: > <Screen Shot 2015-01-04 at 8.08.05 PM.png> > Is obtained with: > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > | b ds | > b := RTGrapherBuilder new. > > ds := RTDataSet new. > ds points: (0 to: 100 by: 0.1). > ds y: [ :x | (0.1 * x) sin ]. > ds noDot. > ds interaction popupText: 'sinus'. > ds connectColor: Color blue. > b add: ds. > > ds := RTDataSet new. > ds points: (0 to: 100 by: 0.1). > ds y: [ :x | (0.2 * x) cos * 2 ]. > ds noDot. > ds interaction popupText: 'cosinus'. > ds connectColor: Color red. > b add: ds. > > b minY: -4. > b maxY: 4. > b minX: -25. > > b build. > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > > <Screen Shot 2015-01-04 at 8.13.51 PM.png> > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > b := RTGrapherBuilder new. > > ds := RTStackedDataSet new. > ds interaction popup. > ds points: #(600 470 170 430 300). > ds barShape width: 20; color: Color lightGreen. > b add: ds. > > b axisX noLabel; noTick. > b axisY noDecimals. > > b addPlugin: RTMeanDevVarPlugin new. > b build > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > Another example: > <Screen Shot 2015-01-04 at 8.17.51 PM.png> > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > b := RTGrapherBuilder new. > b extent: 300 @ 200. > > 5 timesRepeat: [ > ds := RTStackedDataSet new. > ds noDot. > ds points: ((1 to: 500) collect: [ :i | 50 atRandom - 25 ]) cumsum. > ds connectColor: Color green. > b add: ds. > ]. > > b addPlugin: RTMeanDevVarPlugin new. > b build. > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > The plugin framework exposes to a plugin all the necessary to define a whole range of decorations. For example, variable average lines, linear regression should be trivial to add... > > Happy new year! > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > > "Every thing has its own flow" > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Jan. 6, 2015

Re: [Pharo-users] [Pharo-dev] Charting graphs

by Tudor Girba

Pretty cool. The API is interesting. As I see it, this will be limited to things like bar, plots or line graphs. For example, a spider chart will not work with this one, but it will use a builder of its own, right? Some feedback: - I would rename Plugin to Decorator. From your statement, "The plugin framework exposes to a plugin all the necessary to define a whole range of decorations" it seems to me that "Decorator" fits better. - I would just call the class RTGrapher - I do not quite understand how to distinguish the difference between DataSet and StackedDataSet. Cheers, Doru On Mon, Jan 5, 2015 at 12:22 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > RTGraphBuilder went through major improvements. > - min and max may be specified. > - plugins to add some decoration (average line, standard deviation range, > ticks lines, â¦) > > Here are some examples, with some examples, which should illustrate these > points: > Is obtained with: > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > | b ds | > b := RTGrapherBuilder new. > > ds := RTDataSet new. > ds points: (0 to: 100 by: 0.1). > ds y: [ :x | (0.1 * x) sin ]. > ds noDot. > ds interaction popupText: 'sinus'. > ds connectColor: Color blue. > b add: ds. > > ds := RTDataSet new. > ds points: (0 to: 100 by: 0.1). > ds y: [ :x | (0.2 * x) cos * 2 ]. > ds noDot. > ds interaction popupText: 'cosinus'. > ds connectColor: Color red. > b add: ds. > > b minY: -4. > b maxY: 4. > b minX: -25. > > b build. > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > b := RTGrapherBuilder new. > > ds := RTStackedDataSet new. > ds interaction popup. > ds points: #(600 470 170 430 300). > ds barShape width: 20; color: Color lightGreen. > b add: ds. > > b axisX noLabel; noTick. > b axisY noDecimals. > > b addPlugin: RTMeanDevVarPlugin new. > b build > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > Another example: > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > b := RTGrapherBuilder new. > b extent: 300 @ 200. > > 5 timesRepeat: [ > ds := RTStackedDataSet new. > ds noDot. > ds points: ((1 to: 500) collect: [ :i | 50 atRandom - 25 ]) cumsum. > ds connectColor: Color green. > b add: ds. > ]. > > b addPlugin: RTMeanDevVarPlugin new. > b build. > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > The plugin framework exposes to a plugin all the necessary to define a > whole range of decorations. For example, variable average lines, linear > regression should be trivial to add... > > Happy new year! > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 6, 2015

Re: [Pharo-users] Charting graphs

by Alexandre Bergel

Give me a couple of days, and I will update the Agilevisualization chapter. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jan 6, 2015, at 2:49 PM, stepharo <stepharo(a)free.fr> wrote: > > Really really nice. > Continue to push Grapher and trying to reproduce "stupid" charts is the way to stress its design! > Do you have this description somewhere so that I can blog on it? > > Stef > > Le 5/1/15 00:22, Alexandre Bergel a Ã©crit : >> Hi! >> >> RTGraphBuilder went through major improvements. >> >> - min and max may be specified. >> >> - plugins to add some decoration (average line, standard deviation range, ticks lines, â¦) >> >> Here are some examples, with some examples, which should illustrate these points: >> <Mail Attachment.png> >> Is obtained with: >> -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= >> | b ds | >> b := RTGrapherBuilder new. >> >> ds := RTDataSet new. >> ds points: (0 to: 100 by: 0.1). >> ds y: [ :x | (0.1 * x) sin ]. >> ds noDot. >> ds interaction popupText: 'sinus'. >> ds connectColor: Color blue. >> b add: ds. >> >> ds := RTDataSet new. >> ds points: (0 to: 100 by: 0.1). >> ds y: [ :x | (0.2 * x) cos * 2 ]. >> ds noDot. >> ds interaction popupText: 'cosinus'. >> ds connectColor: Color red. >> b add: ds. >> >> b minY: -4. >> b maxY: 4. >> b minX: -25. >> >> b build. >> -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= >> >> >> <Mail Attachment.png> >> -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= >> >> b := RTGrapherBuilder new. >> >> ds := RTStackedDataSet new. >> ds interaction popup. >> ds points: #(600 470 170 430 300). >> ds barShape width: 20; color: Color lightGreen. >> b add: ds. >> >> b axisX noLabel; noTick. >> b axisY noDecimals. >> >> b addPlugin: RTMeanDevVarPlugin new. >> b build >> -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= >> >> Another example: >> <Mail Attachment.png> >> -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= >> b := RTGrapherBuilder new. >> b extent: 300 @ 200. >> >> 5 timesRepeat: [ >> ds := RTStackedDataSet new. >> ds noDot. >> ds points: ((1 to: 500) collect: [ :i | 50 atRandom - 25 ]) cumsum. >> ds connectColor: Color green. >> b add: ds. >> ]. >> >> b addPlugin: RTMeanDevVarPlugin new. >> b build. >> -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= >> >> The plugin framework exposes to a plugin all the necessary to define a whole range of decorations. For example, variable average lines, linear regression should be trivial to add... >> >> Happy new year! >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >

Jan. 6, 2015

Re: [Pharo-users] Metacello does not load the expected version from ConfigOf

by Dale Henrichs

On 1/6/15 7:16 AM, Usman Bhatti wrote: > Dale, > > I couldn't make it work with the upgraded Metacello and the script you > provided. > > Steps I did: > > 1. Download moose image: > https://ci.inria.fr/moose/job/moose-5.0/ > > 2. Update my Metacello to the 'full' version: > Metacello new > baseline: 'Metacello'; > repository: 'github://dalehenrich/metacello-work:master/repository'; > get. > Metacello new > baseline: 'Metacello'; > repository: 'github://dalehenrich/metacello-work:master/repository'; > onConflict: [:ex | ex allow]; > load > > 3. File in the ConfigurationOfDummyParser (see the first message in > the thread). > > 4. Run this script to downgrade to PetitParser version 1.51 > > Metacello new > configuration: 'DummyParser'; > version: '1.0'; > repository: '???'; > onDowngradeUseIncoming: #('PetitParser'); > load. > > The desired version is still not loaded, am I missing something here? Good question, I don't have a lot of time today to spend time trying to reproduce your problem, but if you send me a copy of the Transcript produced while doing the load I might be able to spot the problem ... > > regards, > > A question: I always use Metacello with ConfigOf and have never used > the scripting API myself or saw it being used elsewhere. > Can you provide a link that describes the use cases for both: ConfigOf > vs. Scripting API? I've noticed the same thing:) My "elevator pitch" for the script api goes like this: 1. The scripting api maintains a registry of the actual project versions loaded into the image, making #currentVersion obsolete. #currentVersion is bad because it does a calculation of the current version that can be very slow and sometimes completely incorrect. 2. The old api has rules that it follows when loading projects (i.e., newer projects always win) and there is no mechanism for altering those rules. The scripting api provides mechanisms for for bending those rules to fit your needs ... like allowing a downgrade of a project. Part of the reason that people haven't changed has to do with how incredibly difficult it is to change the existing inertia. Another part of it is that I continue to support the old way of doing things, so there is no explicit motivation to change. If you look back 2-3 years in the archives of the Metacello mailing list[1] you should be able to find a number of posts where I make a more detailed cases for the scripting api:) At the end of the day, it isn't important to me to "get people to use the scripting api," as I said, I continue to support using the old api. I figure that when enough people start asking questions about how to "bend the Metacello rules" that folks will begin to use the "new" scripting api:) Dale [1] https://groups.google.com/forum/#!forum/metacello

Jan. 6, 2015

Re: [Pharo-users] Charting graphs

by stepharo

Really really nice. Continue to push Grapher and trying to reproduce "stupid" charts is the way to stress its design! Do you have this description somewhere so that I can blog on it? Stef Le 5/1/15 00:22, Alexandre Bergel a Ã©crit : > Hi! > > RTGraphBuilder went through major improvements. > - min and max may be specified. > - plugins to add some decoration (average line, standard deviation > range, ticks lines, â¦) > > Here are some examples, with some examples, which should illustrate > these points: > Is obtained with: > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > | b ds | > b := RTGrapherBuilder new. > > ds := RTDataSet new. > ds points: (0 to: 100 by: 0.1). > ds y: [ :x | (0.1 * x) sin ]. > ds noDot. > ds interaction popupText: 'sinus'. > ds connectColor: Color blue. > b add: ds. > > ds := RTDataSet new. > ds points: (0 to: 100 by: 0.1). > ds y: [ :x | (0.2 * x) cos * 2 ]. > ds noDot. > ds interaction popupText: 'cosinus'. > ds connectColor: Color red. > b add: ds. > > b minY: -4. > b maxY: 4. > b minX: -25. > > b build. > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > b := RTGrapherBuilder new. > > ds := RTStackedDataSet new. > ds interaction popup. > ds points: #(600 470 170 430 300). > ds barShape width: 20; color: Color lightGreen. > b add: ds. > > b axisX noLabel; noTick. > b axisY noDecimals. > > b addPlugin: RTMeanDevVarPlugin new. > b build > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > Another example: > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > b := RTGrapherBuilder new. > b extent: 300 @ 200. > > 5 timesRepeat: [ > ds := RTStackedDataSet new. > ds noDot. > ds points: ((1 to: 500) collect: [ :i | 50 atRandom - 25 ]) cumsum. > ds connectColor: Color green. > b add: ds. > ]. > > b addPlugin: RTMeanDevVarPlugin new. > b build. > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > The plugin framework exposes to a plugin all the necessary to define a > whole range of decorations. For example, variable average lines, > linear regression should be trivial to add... > > Happy new year! > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > >

Jan. 6, 2015