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

loading Glamour in Pharo 4

by Peter UhnÃ¡k

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

USB in Pharo?

by Udo Schneider

All, does anybody have some code or plugin to access USB ports with Pharo? Maybe something using libUSB or OpenUSB? Thanks, Udo

March 23, 2015

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

by Alexandre Bergel

Yes. Although RTDevVarDecorator is not rooted into strong maths. It was more an experiment. If you look at the class RTDevVarDecorator, you will see it is quite simple. Adding decoration in a chart made with Grapher is very simple. Alexandre > On Mar 23, 2015, at 12:55 AM, HwaJong Oh <daliot.oh(a)gmail.com> wrote: > > is desviation a typo of deviation? > > HwaJong > >> 2015. 3. 21., ìì¹¨ 6:18, 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: >> <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 >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 23, 2015

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

by Esteban Lorenzano

> 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] Collection with memory?

by Denis Kudriashov

2015-03-23 0:40 GMT+03:00 stepharo <stepharo(a)free.fr>: > Le 22/3/15 22:05, Sven Van Caekenberghe a Ã©crit : > >> On 22 Mar 2015, at 21:44, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >>> >>> Hi >>> >>> It is another perfect task for XStreams: >>> >>> r := #('a12' 'b12' 'a13' 'a14' 'c23' 'a16') reading selecting: [:each | >>> each first = $a]. >>> r get > a12 >>> r get > a13 >>> >> Beautiful ! >> > > Yes but with > r next. > r next > > I was reading the XTreams API recently but this is forbidden for me to > open another project before finishing > what I started. Now if somebody else would like to help pushing Xtreams in > Pharo 50. > I think it is important to have XStreams in pharo by default. Because current streams (from Smalltalk 80) are too powerfull. And when XStreams not in image or can't be loaded easilly people can prefer to use existed streams solution. I was such man when I was need quickly solve some parsing and analizing data task but I can't load XStreams. And I was solve my task with classic streams. It was simple solution. But with XStreams it will be much compact and intuitive implementation.

March 23, 2015

Re: [Pharo-users] Collection with memory?

by Denis Kudriashov

2015-03-23 9:57 GMT+03:00 stepharo <stepharo(a)free.fr>: > Le 22/3/15 23:01, Sven Van Caekenberghe a Ã©crit : > >> On 22 Mar 2015, at 22:40, stepharo <stepharo(a)free.fr> wrote: >>> >>> >>> >>> Le 22/3/15 22:05, Sven Van Caekenberghe a Ã©crit : >>> >>>> On 22 Mar 2015, at 21:44, Denis Kudriashov <dionisiydk(a)gmail.com> >>>>> wrote: >>>>> >>>>> Hi >>>>> >>>>> It is another perfect task for XStreams: >>>>> >>>>> r := #('a12' 'b12' 'a13' 'a14' 'c23' 'a16') reading selecting: [:each >>>>> | each first = $a]. >>>>> r get > a12 >>>>> r get > a13 >>>>> >>>> Beautiful ! >>>> >>> Yes but with >>> r next. >>> r next >>> >> The choice for different selector names was intentional, by design. To >> avoid confusion, because #next and #get are not 100% identical >> (semantically). This is an important point. >> > No I asked martin personally. This is the real reason. There were also > experimenting to offer an API closer to other language. > So that we have > r get. > r next: 4 > But in original docs from https://code.google.com/p/xtreams there are only #get and #read: messages.

March 23, 2015

Re: [Pharo-users] Collection with memory?

by Sven Van Caekenberghe

> On 23 Mar 2015, at 07:57, stepharo <stepharo(a)free.fr> wrote: > > > > Le 22/3/15 23:01, Sven Van Caekenberghe a Ã©crit : >>> On 22 Mar 2015, at 22:40, stepharo <stepharo(a)free.fr> wrote: >>> >>> >>> >>> Le 22/3/15 22:05, Sven Van Caekenberghe a Ã©crit : >>>>> On 22 Mar 2015, at 21:44, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >>>>> >>>>> Hi >>>>> >>>>> It is another perfect task for XStreams: >>>>> >>>>> r := #('a12' 'b12' 'a13' 'a14' 'c23' 'a16') reading selecting: [:each | each first = $a]. >>>>> r get > a12 >>>>> r get > a13 >>>> Beautiful ! >>> Yes but with >>> r next. >>> r next >> The choice for different selector names was intentional, by design. To avoid confusion, because #next and #get are not 100% identical (semantically). This is an important point. > No I asked martin personally. This is the real reason. There were also experimenting to offer an API closer to other language. > So that we have > r get. > r next: 4 IIRC, one difference between #get and #next is that get cannot return nil and will throw an Incomplete exception when EOF next can return nil and might throws an Exception Changing the meaning of an existing selector will cause many problems and discussions. People will think they do not have to change anything and they will be wrong. > superb inconsistencet >> >>> I was reading the XTreams API recently but this is forbidden for me to open another project before finishing >>> what I started. Now if somebody else would like to help pushing Xtreams in Pharo 50. >>> :) >> Well, it does/did load OK in Pharo 3 and probably will in 4 too. >> >> https://ci.inria.fr/pharo-contribution/job/Xtreams/ > Yes loading is just a part of the story :) > We should remove the old ones. > > And we should revise the API because > I **hate ++, -=, += Yeah, but is not because it looks a bit like C++ that it is no longer Smalltalk, these are still normal messages. But yes, some API discussions are possible. >> >>>> Thx Denis. >>>> >>>>> 2015-03-22 20:47 GMT+03:00 stepharo <stepharo(a)free.fr>: >>>>> Hi >>>>> >>>>> I need a collection that does the following: >>>>> >>>>> col := #('a12' 'b12' 'a13' 'a14' 'c23' 'a16') asMyNewCollection. >>>>> col findFirst: [:each | each first = $a] >>>>> > a12 >>>>> col findFirst: [:each | each first = $a] >>>>> > a13 >>>>> >>>>> Do you know a collection that would work? >>>>> So I have the impression that such behavoir could be defined with a kind of methods wrapper. >>>>> >>>>> Stef >> >> > >

March 23, 2015

Re: [Pharo-users] Collection with memory?

by stepharo

Le 22/3/15 23:10, Alain Rastoul a Ã©crit : > Le 22/03/2015 22:39, stepharo a Ã©crit : >> This is like the Iterator Design pattern and this is interesting. > Yes, usually in dotnet IQueryable is implemented by (or on top of) a > IEnumerable. It is one of the key elements of Linq that makes Linq > very user friendly for developers >> Why don't you give a try to see how it grows? > I did a small try . it works, and there was not too much errors in my > suggestion . sometimes I surprise myself ... ;-) > I think it could be cool not only for collections, but with Glorp for > example (translate predicates to sql, some kind of "Linq for > smalltalk"). I think I'll dig a bit in that direction > May be time for some explorations with Glorp. Excellent! Improve our lives :)

March 23, 2015

Re: [Pharo-users] Collection with memory?

by stepharo

Le 22/3/15 23:01, Sven Van Caekenberghe a Ã©crit : >> On 22 Mar 2015, at 22:40, stepharo <stepharo(a)free.fr> wrote: >> >> >> >> Le 22/3/15 22:05, Sven Van Caekenberghe a Ã©crit : >>>> On 22 Mar 2015, at 21:44, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >>>> >>>> Hi >>>> >>>> It is another perfect task for XStreams: >>>> >>>> r := #('a12' 'b12' 'a13' 'a14' 'c23' 'a16') reading selecting: [:each | each first = $a]. >>>> r get > a12 >>>> r get > a13 >>> Beautiful ! >> Yes but with >> r next. >> r next > The choice for different selector names was intentional, by design. To avoid confusion, because #next and #get are not 100% identical (semantically). This is an important point. No I asked martin personally. This is the real reason. There were also experimenting to offer an API closer to other language. So that we have r get. r next: 4 superb inconsistencet > >> I was reading the XTreams API recently but this is forbidden for me to open another project before finishing >> what I started. Now if somebody else would like to help pushing Xtreams in Pharo 50. >> :) > Well, it does/did load OK in Pharo 3 and probably will in 4 too. > > https://ci.inria.fr/pharo-contribution/job/Xtreams/ Yes loading is just a part of the story :) We should remove the old ones. And we should revise the API because I **hate ++, -=, += > >>> Thx Denis. >>> >>>> 2015-03-22 20:47 GMT+03:00 stepharo <stepharo(a)free.fr>: >>>> Hi >>>> >>>> I need a collection that does the following: >>>> >>>> col := #('a12' 'b12' 'a13' 'a14' 'c23' 'a16') asMyNewCollection. >>>> col findFirst: [:each | each first = $a] >>>> > a12 >>>> col findFirst: [:each | each first = $a] >>>> > a13 >>>> >>>> Do you know a collection that would work? >>>> So I have the impression that such behavoir could be defined with a kind of methods wrapper. >>>> >>>> Stef > >

March 23, 2015

Re: [Pharo-users] A Pillar language package for Atom editor?

by HernÃ¡n Morales Durand

Hi Doru, This happens with the following files: https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… HernÃ¡n 2015-03-22 10:05 GMT-03:00 Tudor Girba <tudor(a)tudorgirba.com>: > Could you send me the file you are using? Given that the parser is just an > approximate one, it can be that your specific constructs are not supported. > > Cheers, > Doru > > On Fri, Mar 20, 2015 at 8:59 PM, HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: > >> Ok, alternatively, is someone generating Pillar chapters in Windows? >> >> My problem is GT-InspectorExtensions-Pillar highlights the syntax but not >> properly (see attachment). Could I be using a wrong syntax? >> >> I also figured out a command line to execute pdflatex passing a modified >> PFTE.tex, but latex errors are cryptic (and I don't want to follow there). >> >> HernÃ¡n >> >> >> >> >> 2015-03-17 17:57 GMT-03:00 HernÃ¡n Morales Durand < >> hernan.morales(a)gmail.com>: >> >> Is this working? >>> How to preview a .pier file? >>> >>> https://github.com/pillar-markup/language-pillar >>> >>> Cheers, >>> >>> HernÃ¡n >>> >>> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

March 23, 2015