- Pharo-users - lists.pharo.org

MongoTalk and Replica Sets

by phil＠highoctane.be

For serious use of MongoDB, there is a need to support replica sets. At this point, the MongoClient doesn't appear to support much more than a simple mongod instance. Is there support for that anywhere ? (leaving behind the requirements for supporting GridFS and bulk operations). Python and Node drivers do have support for these. Maybe someone ported parts of them to Pharo? TIA Phil

March 25, 2015

Re: [Pharo-users] Settings browser

by Alain Plantec

Hello Hilaire, I will have a look, I donât remember why. btw, I have to check because the #respondsTo: is not very sexy. Cheers Alain > As I wrote previously, the Settings browser let me complete almost > successfully what I need. See attached screenshot. I am only stuck with > widget model explicitly set to the SettingDeclaration. > > Thanks > > -- > Dr. Geo - http://drgeo.eu <http://drgeo.eu/> > iStoa - http://istoa.drgeo.eu <http://istoa.drgeo.eu/> > > <Capture.png>

March 25, 2015

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

by Alexandre Bergel

Thanks! Alexandre > Le 25 mars 2015 Ã 17:53, Tudor Girba <tudor(a)tudorgirba.com> a Ã©crit : > > Hi Alex, > > After the Pharo and Moose release I will get back to you with feedback. > > Cheers, > Doru > > >> On Fri, Mar 20, 2015 at 10:18 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> 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: >> <Screen Shot 2015-03-20 at 6.12.22 PM.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 >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

March 25, 2015

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

by Tudor Girba

Hi Alex, After the Pharo and Moose release I will get back to you with feedback. Cheers, Doru On Fri, Mar 20, 2015 at 10:18 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > 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 > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- www.tudorgirba.com "Every thing has its own flow"

March 25, 2015

Re: [Pharo-users] Settings browser

by Hilaire

Le 25/03/2015 15:04, Hilaire a Ã©crit : > Le 25/03/2015 12:39, Alain Plantec via Pharo-users a Ã©crit : >>> settingInputWidgetForNode: aSettingDeclaration >>> ^ (aSettingDeclaration name, 'Widget') asSymbol value: self. >>> >> strange that you send the #value: message to a Symbol here. >> Alain > It is tricky indeed, but it is the only way I found to by-pass the > limitation for customized widget: > as I understood it, settings browser expects one class (a type) per > dedicated widget. I can latter create a dedicated class for each drop > list morph I need in the settings browser, then remove this strange > by-pass, I am still exploring. > Nevertheless, it does not seem related to the model problem I exposed > previously. > > Thanks > > Hilaire > As I wrote previously, the Settings browser let me complete almost successfully what I need. See attached screenshot. I am only stuck with widget model explicitly set to the SettingDeclaration. Thanks -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

March 25, 2015

Re: [Pharo-users] GRNumberPrinter

by Sven Van Caekenberghe

According to GRPrinterTest>>#testIntegerPrinter this is expected behaviour ;-) There is also a GRSignPrinter, but since there are no class comments ... > On 25 Mar 2015, at 20:14, Cameron Sanders via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > Date: 25 Mar 2015 20:13:59 CET > Subject: GRNumberPrinter > From: Cameron Sanders <camsanders(a)aol.com> > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > > What am i doing wrong here with my usage? > > (GRNumberPrinter new separator: $,; precision: 2; yourself) > print: -300. > > when inspected i get '300.00'. > > Thanks in advance. > > -Cam > >

March 25, 2015

GRNumberPrinter

by Cameron Sanders

What am i doing wrong here with my usage? (GRNumberPrinter new separator: $,; precision: 2; yourself) print: -300. when inspected i get '300.00'. Thanks in advance. -Cam

March 25, 2015

Re: [Pharo-users] USB in Pharo?

by stepharo

Le 24/3/15 15:58, Udo Schneider a Ã©crit : > 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? Yes > So using NB notation w/o relying on the code generation is safe, correct? Yes! > > 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 25, 2015

Re: [Pharo-users] Collection with memory?

by stepharo

Le 25/3/15 09:32, Sven Van Caekenberghe a Ã©crit : > OK, I get your point now, #read and #read: are a better combination than #get and #read: > > About #++ and friends, yes I think they are so uncommon that they do not warrant a special selector, what is the point ? do not let creep in bad ideas! I can tell you from a dyslexic point of view i++ ++i and all cryptic things that makes a programmer feels like a real men is not fun. Let us use them carefully not as "look mum I can do it" Stef >> On 25 Mar 2015, at 09:12, stepharo <stepharo(a)free.fr> wrote: >> >>> Stef, >>> >>> Like Denis said, there is no #next: in Xtreams, AFIACT. >> Yes but this is the same >> we should get read and read: and not get and read: >> This is my point. >>> There are >>> >>> XTReadStream>>#get >>> "Read an object from self. >>> If there aren't any elements left in the stream, the Incomplete exception is raised." >>> >>> and >>> >>> XTReadStream>>#read: anInteger >>> "Read anInteger's worth of elements from self and return them in a collection. >>> If full anInteger number of elements cannot be read from the source, the Incomplete exception is raised." >>> >>> Like I said, these selector names were chosen to prevent confusion, on purpose. I think that is good. I also think that a lot of though went into the design. >> I personally think that >> get and read: are bad and irregular. >> >> XTReadStream>>#read >> "Read an object from self. >> If there aren't any elements left in the stream, the Incomplete exception is raised." >> >> XTReadStream>>#read: anInteger >> "Read anInteger's worth of elements from self and return them in a collection. >> If full anInteger number of elements cannot be read from the source, the Incomplete exception is raised." >> >> >> funny how the comments are good. No need to change them. This is a sign. > >

March 25, 2015

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

by stepharo

+ 1 and it is on pharo weekly :) Le 23/3/15 22:17, Sven Van Caekenberghe a Ã©crit : > 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> > Nice work, Richard ! > > Sven >

March 25, 2015