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

Color arithmetical operations are broken

by Aliaksei Syrel

Hi, I played with colors and found out, that arithmetical operations with colors are completely broken. https://pharo.fogbugz.com/f/cases/15188/Color-ariphmetical-operations-are-b… Result is not a valid Color - just garbage. It happens because alpha is not being initialized and stays nil. It seems that operation were implemented before alpha support was added. So I propose the following solution: Color red - Color red = Color transparent (Color white alpha: 1) - (Color white alpha: 0.5) = (Color white alpha: > 0.5) R,G,B are subtracted as before. Alpha channels are subtracted too. Color red + Color blue = Color magenta Color red + Color transparent = Color red (Color white alpha: 0.5) + (Color white alpha: 0.5) = (Color white alpha: 1) > R,G,B are added as before. Alpha channels are added too. Multiplication and division by number doesn't change alpha channel. Cheers, Alex

March 20, 2015

Re: [Pharo-dev] The Grapher charting engine

by phil＠highoctane.be

Grapher is indeed nice! Especially now that can get it to give me an SVG rendering with popups etc in my Seaside app. Phil Le 20 mars 2015 22:19, "Alexandre Bergel" <alexandre.bergel(a)me.com> a Ã©crit : > 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 > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

March 20, 2015

The Grapher charting engine

by Alexandre Bergel

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

March 20, 2015

Re: [Pharo-dev] Who maintains Aconcagua & Chalten?

by Hernan Wilkinson

Hi Sean, I answer you in the morning, contact me directly if you did not get the answer Hernan. On Fri, Mar 20, 2015 at 10:11 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Hernan probably missed your emails, try to contact him directly. > Done, thanks. > > Cheers, > Sean > > ------------------------------ > View this message in context: Re: Who maintains Aconcagua & Chalten? > <http://forum.world.st/Who-maintains-Aconcagua-Chalten-tp4813575p4813594.html> > > Sent from the Pharo Smalltalk Developers mailing list archive > <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> at > Nabble.com. > -- *HernÃ¡n WilkinsonAgile Software Development, Teaching & Coaching* *Phone: +54 - 011* - 6091 - 3125 *Mobile: +54 - 911 - 4470 - 7207* *email: hernan.wilkinson(a)10Pines.comsite: http://www.10Pines.com <http://www.10pines.com/>* Address: Alem 693, Floor 5 B, Buenos Aires, Argentina

March 20, 2015

Re: [Pharo-dev] PharoLauncher: Great Tool, Confusing Name

by Sean P. DeNigris

> There is some kind of "cache". The "local" template (at the top of the right pane > lists all local (downloaded) templates. I did see that, but my understanding was that we currently have two options: 1. the same image that was last downloaded via the local template 2. and downloading the latest version from files.pharo.org If thatâs correct, Iâm proposing a third option: download the latest from files.pharo.org unless itâs the same as the local template version. ----- Cheers, Sean -- View this message in context: http://forum.world.st/PharoLauncher-Great-Tool-Confusing-Name-tp4813698p481… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 20, 2015

Re: [Pharo-dev] Validation failur ZnImageExampleDelegateTests>>#testDefaultImage

by Nicolai Hess

Is it possible to see the result of the failing test 2015-03-05 10:40 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > All Zn tests that run local servers work like that, using a random port > from a range of 32. > > With fixed ports, we would get many more conflicts because tests and/or CI > jobs are running concurrently on slaves. > > We could increase the range. > > We could pass some small unique ID to each image and use that to compute a > unique port. > > Testing if a port is available is a total mess because the different > socket plugins behave slightly different. > > Maybe starting servers and letting the OS give out a next available port > could work, I should try that. > > In any case, unless this is a persistent problem I would not do it now. > > > On 05 Mar 2015, at 10:29, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > Anyone has an idea why this test fails so often? > > > > In > > ZnImageExampleDelegateTests>>withServerDo: block > > we use > > ZnServer on: 1700 + 32 atRandom. > > > > I don't know if this is related to the validation failure, but > > the randomly generated portnumber makes it hard get reliable results. > > > > > > > > nicolai > >

March 20, 2015

Re: [Pharo-dev] PharoLauncher: Great Tool, Confusing Name

by Nicolai Hess

2015-03-20 20:25 GMT+01:00 Sean P. DeNigris <sean(a)clipperadams.com>: > PharoLauncher is cool!! Once I realized I could specify the image folder > with > "PhLDirectoryBasedImageRepository location: aFileReference", I was very > happy (I won't start the "images don't belong in ApplicationSupport thread > again, promise ;)). > > There is however one thing that I think could be very confusing... the > build > artifact is called "Pharo_0.2.4.dmg". Now I understand the rationale that > for a new user we are trying for "PharoLauncher = Pharo", but even I was a > little confused seeing version 0.2.4. Since it's only an installer, if we > really need its version number in the artifact, how about > "Pharo_Installer_0.2.4.dmg" or even the more verbose but perhaps clearer > "Pharo_4.0_ Installer_0.2.4.dmg"? The application ultimately gets installed > as "Pharo" anyway. > > Some cool things: > - the fullscreen UI is neat > - dropping down into developer mode is seemless and works well > > One other suggestion: I'm sure this must have been brought up before, but > it > seems to download a fresh image every time (e.g. even if two images are > created from the same template within a few seconds). It seems like it > should be possible to do some caching here... > There is some kind of "cache". The "local" template (at the top of the right pane lists all local (downloaded) templates. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/PharoLauncher-Great-Tool-Confusing-Name-tp4813698.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

March 20, 2015

Re: [Pharo-dev] LabelModel>>#text: Deprecation

by Marcus Denker

> On 20 Mar 2015, at 20:35, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Nicolai Hess wrote >>> We can use text: I should put it back. >> If so, hurry up! > > It seems like several of the rename issues have been fixed to send #label: > already. I guess we keep it? > Yes, the community is starting to react to a deprecation very fastâ¦ it feels even biological. The deprecation triggered everything to be fixed faster than we could decide to revert :-) This is actually amazing. Marcus

March 20, 2015

Re: [Pharo-dev] LabelModel>>#text: Deprecation

by Sean P. DeNigris

Nicolai Hess wrote >> We can use text: I should put it back. > If so, hurry up! It seems like several of the rename issues have been fixed to send #label: already. I guess we keep it? ----- Cheers, Sean -- View this message in context: http://forum.world.st/LabelModel-text-Deprecation-tp4809424p4813706.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 20, 2015

Re: [Pharo-dev] PharoLauncher: Great Tool, Confusing Name

by Sean P. DeNigris

Sean P. DeNigris wrote > One other suggestion Also the matrix build hasn't run in almost a month and the 4.0, stable Mac image is an out-of-date #40511 image. I kicked off the build manually. Let's see what happens... ----- Cheers, Sean -- View this message in context: http://forum.world.st/PharoLauncher-Great-Tool-Confusing-Name-tp4813698p481… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 20, 2015