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

The Grapher charting engine
by Alexandre Bergel March 25, 2015

March 25, 2015

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: 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 3

Re: [Pharo-dev] Which one to use? [WAS: Re: GLMBrick whats next?]
by Thierry Goubier March 25, 2015

March 25, 2015

2015-03-24 16:03 GMT+01:00 Alain Plantec via Pharo-dev < pharo-dev(a)lists.pharo.org>: > > > ---------- Message transfÃ©rÃ© ---------- > From: Alain Plantec <alain.plantec(a)yahoo.com> > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Cc: > Date: Tue, 24 Mar 2015 16:02:56 +0100 > Subject: Re: [Pharo-dev] Which one to use? [WAS: Re: GLMBrick whats next?] > > Le 24 mars 2015 Ã 15:56, Thierry Goubier <thierry.goubier(a)gmail.com> a > Ã©crit : > > > > 2015-03-24 15:39 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > >> >> 2015-03-24 17:36 GMT+03:00 Thierry Goubier <thierry.goubier(a)gmail.com>: >> >>> IMHO, Rubrics, just from it's layout approach, is already a step >>> backward. >> >> >> >> What you mean by this? What's wrong with Rubric layouting? >> > > Padding -> resolved in Morphic by Morph composition: no need to add that > to the Layout engine of each widget > > Aligning -> resolved in Morphic by Morph composition: no need to add that > to the Layout engine of each widget > > > I don't get it sorry. > Padding by ten pixels to the left: | leftMargin aParserButton | leftMargin := Morph new width: 10; hResizing: #shrinkWrap; vResizing: #spaceFill. aParserButton := PluggableButtonMorph on: self getState: nil action: #parse. aParserButton hResizing: #spaceFill; vResizing: #shrinkWrap; label: 'Parse'. AlignmentMorph newRow vResizing: #shrinkWrap; hResizing: #spaceFill; layoutInset: 0; addMorph: aParserButton; addMorph: leftMargin; openInWorld Aligning to the center, horizontally: add a right and left morph, but hResizing: #spaceFill this time. Some type of constraints are hard to do with that system (*), but... LaTeX layout exclusively with that, so, maybe it works ;) ((*) And this is where someone knowing Rubricks could come with a few examples of those). > maybe one example would help > >From the SmaCC GUI :) > > > ZOrdering -> nothing says that submorphs in Morphic can't overlay each > other. > > > Bloc uses z-ordering exactly as Morphic (the code for adding/removing a > submorph are nearly the same) > Ok. But do you know why? There is a reason for that choice. Spec had a real issue with that ordering, so the pressure will be to get it 'corrected'. Mind you, I consider Bloc a very good choice, but I fear that we're not able to stress it enough with hard, very advanced GUIs to ensure we're not loosing power compared to Morphic. Thierry > > Cheers > Alain > > > One of the issue with Morphic as it stands today is that the API is fairly > complex if you want to carefully control placement and morph behavior under > container resizing / move. Oh, and it's very buggy too. Rubricks shows an > API which is even more complex, which isn't surprising if the inspiration > is CSS layout. > > Thierry > > > >

8 10

String>>howManyMatch: Bug or feature ?
by Noury Bouraqadi March 25, 2015

March 25, 2015

Hi, The normal behavior 'abc' howManyMatch: 'abd' --> 2. I got suprized the way Blanks and new lines are handled. '\**' withCRs howManyMatch: '\\**' withCRs. --> 2 instead of 1 'ab\ **' withCRs howManyMatch: 'ab\\**' withCRs. --> 4 instead of 3 '\ **' withCRs howManyMatch: '\\**' withCRs. --> 3 instead of 1 'ab\ **' withCRs howManyMatch: 'ab\\**' withCRs. --> 5 instead of 3 The behavior is the same in both Pharo 3 and Pharo 4. Reading the code of does not help me understand why it's this way String>>howManyMatch: string "Count the number of characters that match up in self and aString." | count shorterLength | count := 0. shorterLength := self size min: string size. 1 to: shorterLength do: [:index | (self at: index) = (string at: index ) ifTrue: [ count := count + 1 ]]. ^ count Noury Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de necessite Please consider the environment before you print

3 3

Re: [Pharo-dev] Which one to use? [WAS: Re: GLMBrick whats next?]
by stepharo March 25, 2015

March 25, 2015

Hi Alain thierry did not look at Bloc :) We see it :) Stef Le 24/3/15 16:13, Alain Plantec via Pharo-dev a Ã©crit :

1 0

GLMBrick whats next?
by Nicolai Hess March 25, 2015

March 25, 2015

I took a look at GLMBrick and I am wondering what is the intent: - a temporary solution until this functions/behavior are included in Morphic - a layer on top of morphic without the intent to do this in Morphic any time. - a temporary solution until this functions/behaviors are implemented with bloc nicolai

10 33

Re: [Pharo-dev] Morphs becoming unresponsive
by Henrik Johansen March 25, 2015

March 25, 2015

> On 24 Mar 2015, at 11:22 , Alain Plantec via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > Subject: Re: [Pharo-dev] Morphs becoming unresponsive > From: Alain Plantec <alain.plantec(a)yahoo.com> > Date: 24 Mar 2015 11:21:55 CET > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > Hello Henrik, > > I read > windowEvent: anEvent > .... > WorldState quitSession. > self removeProperty: #closeWorldDialogOpen ] > > but shouldn't it be > > windowEvent: anEvent > .... > WorldState quitSession. > self removeProperty: #canOpenCloseDialog ] > > Cheers > Alain You are right of course, thanks! Last minute renames are never a good idea, even when the method is 5 lines long :/ I submitted a new slice where the property name is consistent. Cheers, Henry

2 1

Monitoring spotter
by Alexandre Bergel March 25, 2015

March 25, 2015

Hi! The GT crew recently introduces in Pharo a way to keep track of what people are searching in the system. This is a highly valuable piece of information that could benefit everybody. For example, I would love to know which Roassal classes are looking the most often. Or which Roassal examples people are repeatedly searching. However, this is hard to know currently. The reason is because of anonymity. No strings are stored in what is being sent over. To me, this is _highly counter-productive_: if you are working with sensitive information (I donât personally), then do not send things over. But enforcing anonymity generate frustration. So, here is my call: If you care about letting us improving the tools everybody use, feel free to reveal your identity. Simply send the result of the following expression: GTSpotterEventRecorderSettings uniqueInstance secretUUID hash For me => 195966943 Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

GTSpotter initial notice on dark theme
by Yuriy Tymchuk March 25, 2015

March 25, 2015

Did you notice, that initial notice is not readable on dark theme?

3 3

[pharo-project/pharo-core]
by GitHub March 25, 2015

March 25, 2015

Branch: refs/tags/40582 Home: https://github.com/pharo-project/pharo-core

1 0

[pharo-project/pharo-core] 92dba9: 40582
by GitHub March 25, 2015

March 25, 2015

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 92dba9d435851555f71526d9005288e023fecad7 https://github.com/pharo-project/pharo-core/commit/92dba9d435851555f71526d9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-03-25 (Wed, 25 Mar 2015) Changed paths: M AST-Core.package/NumberParser.class/instance/parsing-private/makeIntegerOrScaledInteger.st A AST-Core.package/NumberParser.class/instance/parsing-private/makeIntegerOrScaledIntegerOrFloat.st M AST-Core.package/NumberParser.class/instance/parsing-public/nextNumber.st M AST-Core.package/NumberParser.class/instance/parsing-public/nextNumberBase_.st A AST-Tests-Core.package/NumberParserTest.class/instance/tests - Float/testIntegerWithNegExponentIsAFloat.st M Morphic-Core.package/PasteUpMorph.class/instance/event handling/windowEvent_.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script581.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script582.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40581.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40582.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40582 13761 Fraction floating pointer cannot be debugged https://pharo.fogbugz.com/f/cases/13761 15215 Prevent the World locking due to multiple modal dialogs open https://pharo.fogbugz.com/f/cases/15215 http://files.pharo.org/image/40/40582.zip

1 0