December 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] GetOpt

by Ben Coman

phil(a)highoctane.be wrote: > > > > > On Tue, Dec 2, 2014 at 4:06 PM, Sean P. DeNigris <sean(a)clipperadams.com > <mailto:sean@clipperadams.com>> wrote: > > EstebanLM wrote > > is cool. > > I would like to explore the possibility to replace our command > line parser > > with getopt. You knowâ¦ is more compatible at the end :) > > I find the implementation of our command line handlers very > confusing. It > seems like it grew organically from a smaller idea and the design > got out of > control. There are many assumptions that can make it hard to extend, > especially to combine multiple options, as Ben and I discovered when > implementing the "don't run startup scripts" handler. It would be > nice to > revisit starting from a behavioral specification. > > > Well, what makes you say that? > The core CommandLineHandler itself is pretty generic and can do a lot of > things. > > Then, yeah, what is under is quite varied. But that's to be expected > when trying out "new tech". > > I've been making one of my own here for a given project with about 20-30 > commands and I had to put in some structure indeed. Is that part available somewhere that can be reviewed ? cheers -ben

Dec. 2, 2014

Re: [Pharo-dev] GetOpt

by phil＠highoctane.be

On Tue, Dec 2, 2014 at 4:06 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > EstebanLM wrote > > is cool. > > I would like to explore the possibility to replace our command line > parser > > with getopt. You knowâ¦ is more compatible at the end :) > > I find the implementation of our command line handlers very confusing. It > seems like it grew organically from a smaller idea and the design got out > of > control. There are many assumptions that can make it hard to extend, > especially to combine multiple options, as Ben and I discovered when > implementing the "don't run startup scripts" handler. It would be nice to > revisit starting from a behavioral specification. > Well, what makes you say that? The core CommandLineHandler itself is pretty generic and can do a lot of things. Then, yeah, what is under is quite varied. But that's to be expected when trying out "new tech". I've been making one of my own here for a given project with about 20-30 commands and I had to put in some structure indeed. Phil > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/GetOpt-tp4793474p4793621.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Dec. 2, 2014

12854 TestRunner>>categorySelected hard coded zero

by Ben Coman

Anyone know why TestRunner>>categorySelected was hard coded to return zero? It breaks shift-click multiple selection in TestRunner. Seems we've lived with it a long time... * Version info --> "lr 10/31/2005 15:11" btw, SystemReporter>>categorySelected method is identical * Hardcoded to return zero * Version info --> "lr 10/31/2005 15:11" maybe one class was copied to the other? cheers -ben Fix submitted... https://pharo.fogbugz.com/default.asp?12854

Dec. 2, 2014

Re: [Pharo-dev] GetOpt

by Sean P. DeNigris

EstebanLM wrote > is cool. > I would like to explore the possibility to replace our command line parser > with getopt. You knowâ¦ is more compatible at the end :) I find the implementation of our command line handlers very confusing. It seems like it grew organically from a smaller idea and the design got out of control. There are many assumptions that can make it hard to extend, especially to combine multiple options, as Ben and I discovered when implementing the "don't run startup scripts" handler. It would be nice to revisit starting from a behavioral specification. ----- Cheers, Sean -- View this message in context: http://forum.world.st/GetOpt-tp4793474p4793621.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Dec. 2, 2014

Re: [Pharo-dev] WhatsUp from: 2014-12-01 until: 2014-12-14

by Mariano Martinez Peck

On Tue, Dec 2, 2014 at 11:52 AM, Ben Coman <btc(a)openinworld.com> wrote: > Mariano Martinez Peck wrote: > >> >> >> On Mon, Dec 1, 2014 at 2:00 AM, <seaside(a)rmod.lille.inria.fr <mailto: >> seaside(a)rmod.lille.inria.fr>> wrote: >> >> Hi! We're sending this automatic email twice a month, to give the >> community an opportunity to easily know what's happening and to >> coordinate efforts. Just answer informally, and feel free to spawn >> discussions thereafter! >> >> ### Here's what I've been up to since the last WhatsUp: >> >> >> >> - I gave 3 Smalltalk/Pharo related presentations (Web Development with >> Smalltalk, Smalltalk and Business, and Marea) at >> http://ilas.memi.umss.edu.bo/ (sponsored by ESUG). Slides: >> >> http://www.slideshare.net/MarianoMartinezPeck/web- >> development-with-smalltalk >> > > > I am curious to learn why Seaside "scalability is a bit different" ? > The most immediate reason is that session affinity is a requirement, not an option, as with other stateless frameworks. Unless you are in GemStone, where sessions are persisted and hence session affinity is not a requirement. Another would be memory requirements. Depending on your app, if you use the statefull side of the framework a lot (#states and friends) and you do keep large graphs in there, the system itself will obviously consume more memory. So that's another thing to consider that may not be the same when dealing with stateless framworks. Maybe there were more reasons that I cannot remember now. > cheers -ben > > > http://www.slideshare.net/MarianoMartinezPeck/smalltalk-and-business >> http://www.slideshare.net/MarianoMartinezPeck/thesis- >> presentation-14987645 >> >> I hope at least to get some guys involved! >> >> >> ### What's next, until 2014-12-14 (*): >> >> >> >> Back to work and update CV. >> >> >> (*) we'll be expecting results by then ;) >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > > -- Mariano http://marianopeck.wordpress.com

Dec. 2, 2014

Re: [Pharo-dev] tests coverage of minimal Pharo

by Luc Fabresse

> The idea is to integrate it with the VM (to some extend) via Sista next > year. > Meanwhile, you can already play with this idea thanks to Nick that implemented the Reflectogram idea. However, it requires a modified VM. It is explained in Nick's PhD but a paper will be published soon about that. Now, it will be much better using Reflexivity + VM support. #Luc > > Alexandre > > > > On Mon, Dec 1, 2014 at 2:34 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > >> Right. Some tests ended with out-of-memory errors or vm crash. One >> problem was in a trait so I had to put all users of it on the >> blacklist. >> >> Cheers, >> -- Pavel >> >> 2014-12-01 14:21 GMT+01:00 Alejandro Infante < >> alejandroinfante91(a)gmail.com>: >> > Hapao works using method wrappers, and do some stuff for every method >> > execution. If Hapao use something you are instrumenting, you are start >> > looping endlessly. So blacklisted classes are classes you are not going >> to >> > instrument. >> > >> > But, I was trying to understand all the classes you blacklisted, and I >> donât >> > understand why you have some tests blacklisted, any reason for them? >> > >> > Cheers, >> > Alejandro >> > >> > On Dec 1, 2014, at 7:57 AM, Guillermo Polito <guillermopolito(a)gmail.com >> > >> > wrote: >> > >> > ignorant question: What is a black listed class? :) >> > >> > On Sun, Nov 30, 2014 at 7:21 PM, Pavel Krivanek < >> pavel.krivanek(a)gmail.com> >> > wrote: >> >> >> >> Hi, >> >> >> >> I set the job for tests coverage testing of the mimimal Pharo using >> Hapao: >> >> >> >> >> >> >> https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo-4.0-Bootstrap-Step-2… >> >> >> >> To load results you should load ConfigurationOfSUnit and >> >> ConfigurationOfKernelTests from Pharo/SystemConfigurations repository >> >> into an image with Hapao. Then inspect: >> >> >> >> FLMaterializer materializeFromFileNamed: 'hapao.fuel'. >> >> >> >> Do not try to visualise it ;-) >> >> >> >> Currently blacklisted classes are: >> >> >> >> Array Association ArrayedCollection Behavior BlockClosure ByteSymbol >> >> ByteString ClassDescription CompiledMethod Class Dictionary >> >> Hapao2Package HashedCollection IdentityDictionary Integer LookupKey >> >> FileStream Magnitude Object ProtoObject Process ProcessLocalVariable >> >> ProcessorScheduler ProcessSpecificVariable RPackageOrganizer RPackage >> >> SmalltalkImage SequenceableCollection Set Semaphore SmallInteger >> >> Symbol String SourceFileArray VirtualMachine OCCompilerTest >> >> SortedCollectionTest DictionaryTest SetTest ArrayTest SymbolTest >> >> BagTest StringTest HeapTest FloatArrayTest OrderedCollectionTest >> >> LinkedListTest S2BasicNewStub S2BasicNewStubClass S2BasicNewStubMethod >> >> S2BasicNewStubPackage S2BasicNewTest S2C S2CClass S2CMethod S2CPackage >> >> S2Class S2ClassPlugin S2Context S2InsertBehaviorPlugin S2Lock S2Method >> >> S2MethodPlugin S2Package S2Plugin S2PluginTest S2PointNewPlugin >> >> S2Profiler S2ProfilerPlugin S2ProfilerTest S2SenderTest S2SpyStack >> >> S2StringNewPlugin S2TestException S2Tester S2TesterClass >> >> S2TesterMethod S2TesterPackage S2TesterSpy S2py S2pyA S2pyB >> >> S2pyDummyTest S2pySenderStub S2pySenderStubClass S2pySenderStubMethod >> >> S2pySenderStubPackage >> >> >> >> Cheers, >> >> -- Pavel >> >> >> > >> > >> >> > > >

Dec. 2, 2014

Re: [Pharo-dev] Scale in 3.0 (kind of ANN)

by Ben Coman

phil(a)highoctane.be wrote: > On Tue, Dec 2, 2014 at 1:47 PM, Norbert Hartl <norbert(a)hartl.name > <mailto:norbert@hartl.name>> wrote: > > > > Am 02.12.2014 um 13:31 schrieb Ben Coman <btc(a)openinworld.com > <mailto:btc@openinworld.com>>: > > > > phil(a)highoctane.be <mailto:phil@highoctane.be> wrote: > >> I've put Guille's Scale thing > (http://guillep.github.io/blog/2014/01/23/replacing-bash-with-pharo/) > into Pharo 3.0 > >> Details on how to use here: > >> http://smalltalkhub.com/#!/~philippeback/Scale > >> Enjoy, > >> Phil > > > > > > > We named the command we needed scale, because scales are in shells, > > > it sounded nice. > > > > Nice lateral thinking, but it seems like a stretch :) > > > > For making a shell, why not something simple in the tradition of > sh, bash, csh, ksh, psh? e.g. pharosh or phsh? > > > +1 > > > Scale is what it was. There is also Coral, so, well, marine names are > staying. okay. > > If we want a 'sh', what about: > > phish > phash > phosh > > psh is not too bad after all. Unfortunately taken by perl. http://gnp.github.io/psh/ > pharosh looks cool too. > > With "phish" we can say, "I am phishing" in the same vein as "I am bashing". phishing has negative connotations wrt IT security scams > > Phil > > > > > Norbert > > >

Dec. 2, 2014

Re: [Pharo-dev] WhatsUp from: 2014-12-01 until: 2014-12-14

by Ben Coman

Mariano Martinez Peck wrote: > > > On Mon, Dec 1, 2014 at 2:00 AM, <seaside(a)rmod.lille.inria.fr > <mailto:seaside@rmod.lille.inria.fr>> wrote: > > Hi! We're sending this automatic email twice a month, to give the > community an opportunity to easily know what's happening and to > coordinate efforts. Just answer informally, and feel free to spawn > discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > > > > - I gave 3 Smalltalk/Pharo related presentations (Web Development with > Smalltalk, Smalltalk and Business, and Marea) > at http://ilas.memi.umss.edu.bo/ (sponsored by ESUG). Slides: > > http://www.slideshare.net/MarianoMartinezPeck/web-development-with-smalltalk I am curious to learn why Seaside "scalability is a bit different" ? cheers -ben > http://www.slideshare.net/MarianoMartinezPeck/smalltalk-and-business > http://www.slideshare.net/MarianoMartinezPeck/thesis-presentation-14987645 > > I hope at least to get some guys involved! > > > > ### What's next, until 2014-12-14 (*): > > > > Back to work and update CV. > > > > > (*) we'll be expecting results by then ;) > > > > > -- > Mariano > http://marianopeck.wordpress.com

Dec. 2, 2014

Re: [Pharo-dev] tests coverage of minimal Pharo

by Marcus Denker

> On 01 Dec 2014, at 15:58, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> Would Hapao benefit from using reflectivity as it's intercession framework instead of using method wrappers? Maybe in such a way it can also instrument classes such as Array, Objectâ¦ > > May be. But I am wondering whether it will really solve the problem. I guess reflectivity is using the same kind of transformation as we do. What we do is to model recursionâ¦ a link is active at a certain âmeta levelâ, calling the meta object switches the meta level, which means that it will not take the link again â> meta recursion is stopped. > In Java, the JVM provides an interface, to which you can connect a debugger. With such interface, you can literally profile anything. > The idea is to integrate it with the VM (to some extend) via Sista next year. > Alexandre > > >> >> On Mon, Dec 1, 2014 at 2:34 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: >> Right. Some tests ended with out-of-memory errors or vm crash. One >> problem was in a trait so I had to put all users of it on the >> blacklist. >> >> Cheers, >> -- Pavel >> >> 2014-12-01 14:21 GMT+01:00 Alejandro Infante <alejandroinfante91(a)gmail.com <mailto:alejandroinfante91@gmail.com>>: >> > Hapao works using method wrappers, and do some stuff for every method >> > execution. If Hapao use something you are instrumenting, you are start >> > looping endlessly. So blacklisted classes are classes you are not going to >> > instrument. >> > >> > But, I was trying to understand all the classes you blacklisted, and I donât >> > understand why you have some tests blacklisted, any reason for them? >> > >> > Cheers, >> > Alejandro >> > >> > On Dec 1, 2014, at 7:57 AM, Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> >> > wrote: >> > >> > ignorant question: What is a black listed class? :) >> > >> > On Sun, Nov 30, 2014 at 7:21 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> >> > wrote: >> >> >> >> Hi, >> >> >> >> I set the job for tests coverage testing of the mimimal Pharo using Hapao: >> >> >> >> >> >> https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo-4.0-Bootstrap-Step-2… <https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo-4.0-Bootstrap-Step-2…> >> >> >> >> To load results you should load ConfigurationOfSUnit and >> >> ConfigurationOfKernelTests from Pharo/SystemConfigurations repository >> >> into an image with Hapao. Then inspect: >> >> >> >> FLMaterializer materializeFromFileNamed: 'hapao.fuel'. >> >> >> >> Do not try to visualise it ;-) >> >> >> >> Currently blacklisted classes are: >> >> >> >> Array Association ArrayedCollection Behavior BlockClosure ByteSymbol >> >> ByteString ClassDescription CompiledMethod Class Dictionary >> >> Hapao2Package HashedCollection IdentityDictionary Integer LookupKey >> >> FileStream Magnitude Object ProtoObject Process ProcessLocalVariable >> >> ProcessorScheduler ProcessSpecificVariable RPackageOrganizer RPackage >> >> SmalltalkImage SequenceableCollection Set Semaphore SmallInteger >> >> Symbol String SourceFileArray VirtualMachine OCCompilerTest >> >> SortedCollectionTest DictionaryTest SetTest ArrayTest SymbolTest >> >> BagTest StringTest HeapTest FloatArrayTest OrderedCollectionTest >> >> LinkedListTest S2BasicNewStub S2BasicNewStubClass S2BasicNewStubMethod >> >> S2BasicNewStubPackage S2BasicNewTest S2C S2CClass S2CMethod S2CPackage >> >> S2Class S2ClassPlugin S2Context S2InsertBehaviorPlugin S2Lock S2Method >> >> S2MethodPlugin S2Package S2Plugin S2PluginTest S2PointNewPlugin >> >> S2Profiler S2ProfilerPlugin S2ProfilerTest S2SenderTest S2SpyStack >> >> S2StringNewPlugin S2TestException S2Tester S2TesterClass >> >> S2TesterMethod S2TesterPackage S2TesterSpy S2py S2pyA S2pyB >> >> S2pyDummyTest S2pySenderStub S2pySenderStubClass S2pySenderStubMethod >> >> S2pySenderStubPackage >> >> >> >> Cheers, >> >> -- Pavel >> >> >> > >> > >> >> >

Dec. 2, 2014

Re: [Pharo-dev] default fonts changed in Pharo 4.0

by Esteban Lorenzano

:) looks like I fixed itâ¦ weâll see in next integrations. Esteban > On 02 Dec 2014, at 13:31, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Thanks, Esteban. This kind of work is too under appreciated. > > Cheers, > Doru > > On Tue, Dec 2, 2014 at 1:10 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > â¦ and I lost fonts again :( > I made an integration and fonts got lostâ¦ Iâm reviving issue, and working on it :( > > Esteban > >> On 02 Dec 2014, at 12:47, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: >> >>> >>> On 02 Dec 2014, at 12:12, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >>> >>>> >>>> On 02 Dec 2014, at 12:02, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: >>>> >>>> >>>>> On 02 Dec 2014, at 11:46, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >>>>> >>>>> There is no Source Code Sans :). There is only "Source Sans Pro" or "Source Code Pro". >>>> >>>> Yes, right now in the latest 4.0. >>>> >>>> But there used to be a different one, that is the one I am using, see screenshot (http://www.google.com/fonts/specimen/Open+Sans <http://www.google.com/fonts/specimen/Open+Sans>). I don't remember where I got it from (Igor is the author), but I have been using it for months. >>> >>> no, it was me the authorâ¦ and it was a mistake I made first time thatâs why I removed it (but I can package it and put it somewhere anywayâ¦ I was even thinking on create a âFont Repositoryâ where put different fonts, until I found this: http://smalltalkhub.com/#!/~girba/FreeFonts <http://smalltalkhub.com/#!/~girba/FreeFonts> which is a cool repo, but does not works completely along our versionâ¦ we will need to merge :P) >> >> Maybe it would be even better if there was code in the image to make these embedded fonts yourself (or a comment). >> >>>> My question was, why choose one above the other ? >>> >>> I replaced it with the Source Sans Pro because same family fonts works better together (Source * Pro) >> >> OK. It seems to have a smaller width, we'll see. >> >>> cheers, >>> Esteban >>> >>>> >>>> <Screen Shot 2014-12-02 at 11.57.13.png> >>>> >>>>> >>>>> Doru >>>>> >>>>> On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: >>>>> What is the difference between 'Open Sans' and 'Source Code Sans' ? >>>>> >>>>> I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider. >>>>> >>>>>> On 02 Dec 2014, at 11:27, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >>>>>> >>>>>> Great! >>>>>> >>>>>> Doru >>>>>> >>>>>> p.s. Finally :) >>>>>> >>>>>> >>>>>> On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >>>>>> Hi, >>>>>> >>>>>> We changed the default fonts in Pharo for the ones that are used normally in Moose. >>>>>> They are: Source Sans Pro and Source Code Pro. >>>>>> We needed to do it for several reasons: >>>>>> >>>>>> 1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) >>>>>> 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told) >>>>>> >>>>>> So, well, thatâ¦ you will see âsomething differentâ when you download latest image version :) >>>>>> >>>>>> cheers, >>>>>> Esteban >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> www.tudorgirba.com <http://www.tudorgirba.com/> >>>>>> >>>>>> "Every thing has its own flow" >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com <http://www.tudorgirba.com/> >>>>> >>>>> "Every thing has its own flow" > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > > "Every thing has its own flow"

Dec. 2, 2014