August 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Uniformizing Pharo

by StÃ©phane Ducasse

> Did you use the method categorizer that is already in the image? > > => MethodClassifier > > it implements already a lot of rules, so you should plug in your tool there or remove MethodClassifier and make it work with nautilus. otherwise we have a lot of duplicated functionality. I was not aware of it I will look at it. In fact there was a method categorizer in a nice package with tests and I took this one and adapted it. I will check the rules. Stef

Aug. 14, 2013

Re: [Pharo-dev] Uniformizing Pharo

by Camillo Bruni

Did you use the method categorizer that is already in the image? => MethodClassifier it implements already a lot of rules, so you should plug in your tool there or remove MethodClassifier and make it work with nautilus. otherwise we have a lot of duplicated functionality. On 2013-08-14, at 02:44, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > On Aug 14, 2013, at 4:38 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> i wonder, if we can modify the compiler, so that when it sees that >> method's selector has well known name, it categorizing method >> automatically under right category :) >> (dunno however, what to do about existing code, when you recompiling it) > > we will integrate the categorizer close to the code browser and may be later the compiler > > >> >> On 14 August 2013 04:32, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >>> StÃ©phane Ducasse wrote >>>> I started to be fed up about protocol inconsistencies >>> >>> Amen >>> >>> >>> StÃ©phane Ducasse wrote >>>> So I will propose a set of rules (and a tool - I'm working on it) to >>>> automatically categorize methods. >>>> ... >>>> Now we discussed today with esteban for initialize* we will use >>>> 'initialization' >>> >>> Yay! >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> View this message in context: http://forum.world.st/Uniformizing-Pharo-tp4703357p4703577.html >>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > >

Aug. 14, 2013

[update 3.0] #30336

by StÃ©phane Ducasse

Aug. 14, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/… 1 regressions found. Zinc.Zodiac.ZnHTTPSTests.testGetPharoVersion

Aug. 14, 2013

Re: [Pharo-dev] is there anyone who can use SimpleMIDIPort on Mac OSX 10.6.8?

by StÃ©phane Ducasse

Thanks for the feedback. Please let us know if you find problemsâ¦. because we could not find the original code which was probably never in the source management. So we really enjoy seeing your code running on Pharo :) Stef On Aug 14, 2013, at 1:06 PM, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: > I've just noticed github message > - added missing methods for SerialPlugin > https://github.com/pharo-project/pharovm/commit/f7c0b24ffde391c93fc479ab7ba… > > and tested MIDIPlugin with 214 VM and Pharo-20618.image. > IT WORKS! > > thank you!! > > > > 2013/8/5 Igor Stasenko <siguctua(a)gmail.com>: >> On 4 August 2013 18:35, laurent laffont <laurent.laffont(a)gmail.com> wrote: >>> Hi, >>> >>> I was looking about MIDI on Linux today, and may be that's related. On >>> Linux, for the MIDI plugin, there's 2 files: >>> - sqUnixMIDIALSA.inc >>> - sqUnixMIDINone.inc >>> >>> it seems sqUnixMIDINone is build, and not ALSA one. In >>> /platforms/unix/plugins/MIDIPlugin/sqUnixMIDI.c: >>> #if defined(USE_MIDI_ALSA) >>> # include "sqUnixMIDIALSA.inc" >>> #else >>> # include "sqUnixMIDINone.inc" >>> #endif >>> >>> USE_MIDI_ALSA is set in a configure script, and if I understand correctly, >>> it is not used with the cmake process ? Anyway, I've changed to: >>> #include "sqUnixMIDIALSA.inc" >>> >>> and the file compile, but fail to link. It seems gcc doesn't have the needed >>> -l flag to link to alsa lib, but I don't know where to specify this (I >>> suppose somewhere in VMMaker ?) >>> >> Look for CPlatformConfig and its descendants. >> >>> Cheers, >>> >>> Laurent >>> >>> >>> >>> >>> >>> On Sun, Aug 4, 2013 at 5:09 PM, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: >>>> >>>> is there anyone who can use SimpleMIDIPort on Mac OSX 10.6.8? >>>> >>>> StÃ©phane Ducasse san told me that it can use MIDIPlugin in Pharo 2.0 >>>> on Mac 10.8.3. >>>> but I can't use MIDIPlugin on Mac OSX 10.6.8. >>>> >>>> SimpleMIDIPort>>#midiIsSupported >>>> -> false >>>> SimpleMIDIPort>>#primPortCount >>>> -> 0 >>>> >>>> vm: >>>> Pharo.app(13/03/13) >>>> Pharo-126.app(13/05/04) >>>> Pharo-145.app(13/05/31) >>>> Pharo-169.app(13/07/10) >>>> Pharo-186.app(13/07/15) >>>> Pharo-187.app(13/07/19) >>>> Pharo-188.app(13/07/31) >>>> >>>> I would like to know whether it is a problem of all those that are >>>> using 10.6.8 or personal trouble. >>>> >>>> -p.s.- >>>> >>>> On Eliot Miranda san's CogMT.r2761.app and Cog.r2761.app, >>>> SimpleMIDIPort>>#midiIsSupported >>>> -> true >>>> SimpleMIDIPort>>#primPortCount >>>> -> 1 >>>> >>>> regards. >>>> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > > > -- > -- > "NISHIHARA Satoshi" > [:goonsh :nsh | ^ nishis perform: goonsh with: nsh] > <System Reporter2.png>

Aug. 14, 2013

Re: [Pharo-dev] is there anyone who can use SimpleMIDIPort on Mac OSX 10.6.8?

by Esteban Lorenzano

Ah yes... I forget to send a mail to the list, but I spent monday fixing the MIDI plugin :P cool to know that it worked! Esteban On Aug 14, 2013, at 1:06 PM, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: > I've just noticed github message > - added missing methods for SerialPlugin > https://github.com/pharo-project/pharovm/commit/f7c0b24ffde391c93fc479ab7ba… > > and tested MIDIPlugin with 214 VM and Pharo-20618.image. > IT WORKS! > > thank you!! > > > > 2013/8/5 Igor Stasenko <siguctua(a)gmail.com>: >> On 4 August 2013 18:35, laurent laffont <laurent.laffont(a)gmail.com> wrote: >>> Hi, >>> >>> I was looking about MIDI on Linux today, and may be that's related. On >>> Linux, for the MIDI plugin, there's 2 files: >>> - sqUnixMIDIALSA.inc >>> - sqUnixMIDINone.inc >>> >>> it seems sqUnixMIDINone is build, and not ALSA one. In >>> /platforms/unix/plugins/MIDIPlugin/sqUnixMIDI.c: >>> #if defined(USE_MIDI_ALSA) >>> # include "sqUnixMIDIALSA.inc" >>> #else >>> # include "sqUnixMIDINone.inc" >>> #endif >>> >>> USE_MIDI_ALSA is set in a configure script, and if I understand correctly, >>> it is not used with the cmake process ? Anyway, I've changed to: >>> #include "sqUnixMIDIALSA.inc" >>> >>> and the file compile, but fail to link. It seems gcc doesn't have the needed >>> -l flag to link to alsa lib, but I don't know where to specify this (I >>> suppose somewhere in VMMaker ?) >>> >> Look for CPlatformConfig and its descendants. >> >>> Cheers, >>> >>> Laurent >>> >>> >>> >>> >>> >>> On Sun, Aug 4, 2013 at 5:09 PM, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: >>>> >>>> is there anyone who can use SimpleMIDIPort on Mac OSX 10.6.8? >>>> >>>> StÃ©phane Ducasse san told me that it can use MIDIPlugin in Pharo 2.0 >>>> on Mac 10.8.3. >>>> but I can't use MIDIPlugin on Mac OSX 10.6.8. >>>> >>>> SimpleMIDIPort>>#midiIsSupported >>>> -> false >>>> SimpleMIDIPort>>#primPortCount >>>> -> 0 >>>> >>>> vm: >>>> Pharo.app(13/03/13) >>>> Pharo-126.app(13/05/04) >>>> Pharo-145.app(13/05/31) >>>> Pharo-169.app(13/07/10) >>>> Pharo-186.app(13/07/15) >>>> Pharo-187.app(13/07/19) >>>> Pharo-188.app(13/07/31) >>>> >>>> I would like to know whether it is a problem of all those that are >>>> using 10.6.8 or personal trouble. >>>> >>>> -p.s.- >>>> >>>> On Eliot Miranda san's CogMT.r2761.app and Cog.r2761.app, >>>> SimpleMIDIPort>>#midiIsSupported >>>> -> true >>>> SimpleMIDIPort>>#primPortCount >>>> -> 1 >>>> >>>> regards. >>>> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > > > -- > -- > "NISHIHARA Satoshi" > [:goonsh :nsh | ^ nishis perform: goonsh with: nsh] > <System Reporter2.png>

Aug. 14, 2013

Re: [Pharo-dev] is there anyone who can use SimpleMIDIPort on Mac OSX 10.6.8?

by NISHIHARA Satoshi

I've just noticed github message - added missing methods for SerialPlugin https://github.com/pharo-project/pharovm/commit/f7c0b24ffde391c93fc479ab7ba… and tested MIDIPlugin with 214 VM and Pharo-20618.image. IT WORKS! thank you!! 2013/8/5 Igor Stasenko <siguctua(a)gmail.com>: > On 4 August 2013 18:35, laurent laffont <laurent.laffont(a)gmail.com> wrote: >> Hi, >> >> I was looking about MIDI on Linux today, and may be that's related. On >> Linux, for the MIDI plugin, there's 2 files: >> - sqUnixMIDIALSA.inc >> - sqUnixMIDINone.inc >> >> it seems sqUnixMIDINone is build, and not ALSA one. In >> /platforms/unix/plugins/MIDIPlugin/sqUnixMIDI.c: >> #if defined(USE_MIDI_ALSA) >> # include "sqUnixMIDIALSA.inc" >> #else >> # include "sqUnixMIDINone.inc" >> #endif >> >> USE_MIDI_ALSA is set in a configure script, and if I understand correctly, >> it is not used with the cmake process ? Anyway, I've changed to: >> #include "sqUnixMIDIALSA.inc" >> >> and the file compile, but fail to link. It seems gcc doesn't have the needed >> -l flag to link to alsa lib, but I don't know where to specify this (I >> suppose somewhere in VMMaker ?) >> > Look for CPlatformConfig and its descendants. > >> Cheers, >> >> Laurent >> >> >> >> >> >> On Sun, Aug 4, 2013 at 5:09 PM, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: >>> >>> is there anyone who can use SimpleMIDIPort on Mac OSX 10.6.8? >>> >>> StÃ©phane Ducasse san told me that it can use MIDIPlugin in Pharo 2.0 >>> on Mac 10.8.3. >>> but I can't use MIDIPlugin on Mac OSX 10.6.8. >>> >>> SimpleMIDIPort>>#midiIsSupported >>> -> false >>> SimpleMIDIPort>>#primPortCount >>> -> 0 >>> >>> vm: >>> Pharo.app(13/03/13) >>> Pharo-126.app(13/05/04) >>> Pharo-145.app(13/05/31) >>> Pharo-169.app(13/07/10) >>> Pharo-186.app(13/07/15) >>> Pharo-187.app(13/07/19) >>> Pharo-188.app(13/07/31) >>> >>> I would like to know whether it is a problem of all those that are >>> using 10.6.8 or personal trouble. >>> >>> -p.s.- >>> >>> On Eliot Miranda san's CogMT.r2761.app and Cog.r2761.app, >>> SimpleMIDIPort>>#midiIsSupported >>> -> true >>> SimpleMIDIPort>>#primPortCount >>> -> 1 >>> >>> regards. >>> >> > > > > -- > Best regards, > Igor Stasenko. > -- -- "NISHIHARA Satoshi" [:goonsh :nsh | ^ nishis perform: goonsh with: nsh]

Aug. 14, 2013

Re: [Pharo-dev] inria jenkins got much faster

by Tudor Girba

Yes, we are always using the latest :). I just saw now the report about #20619. http://permalink.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/81515 Wow, this is a phenomenal boost! Thank you very much. Doru On Wed, Aug 14, 2013 at 11:46 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > if you are using latest 2.0, that's probably because the integration of > the RPackageSet cache. > the previous slowdown was exponential, so big projects like moose took > *really* much time to load. > > Esteban > > > On Aug 14, 2013, at 11:43 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > I just noticed that the Jenkins jobs got much faster. For example, the > Moose job went from 36 minutes to 6 minutes. Or the Glamour job went from > 11 minutes to 3 minutes. This is fantastic, but I do not know why the > difference occurs. > > It seems that the difference started yesterday before 15:00: > https://ci.inria.fr/moose/job/moose-latest-dev-4.8/871/ (15:49 -- 6 min) > https://ci.inria.fr/moose/job/moose-latest-dev-4.8/870/ (02:49 -- 36 min) > > As it affected multiple jobs, I suspect it has to do with the > infrastructure. > > Anyone has any idea as to why this happens? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 14, 2013

Re: [Pharo-dev] Updating the Pharo Contributors listing

by Sven Van Caekenberghe

Many people already submitted their details and I edited a couple of entries manually to add at least an email address, so the list is already looking better: http://contributors.pharo.org Please spread the word and convince everyone to step in and update their info. On 12 Aug 2013, at 17:12, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Dear Fellow Pharoers, > > As some of you may know, we have a page listing Pharo Contributors > > http://www.pharo-project.org/community/contributors > > This page was manually constructed and urgently needs an update. > Based on the code behind the Pharo Consultants page > > http://consultants.pharo.org > > we want a similar data driven, statically generated page for Pharo Contributors > > http://contributors.pharo.org > > the new page is based on some of the old data, but needs updating. Many people are missing as well. So please, please, edit the template and send me your new or up to date information. > > PharoContributor new > name: 'StÃ©phane Ducasse'; > id: 'stephaneducasse'; > email: 'stephane.ducasse(a)inria.fr'; > website: 'http://stephane.ducasse.free.fr/'; > description: 'Research director at INRIA Lille leading the RMoD Team. Pharo board member and president of ESUG.'; > image: 'http://stephane.ducasse.free.fr/StefFingerOnNose128.jpg'; > yourself > > PharoContributor new > name: 'Camillo Bruni'; > email: 'camillobruni(a)gmail.com'; > description: 'Cosmopolitan Swiss Hacker, currently at INRIA'; > yourself > > Some notes: > > - id is only needed when your name contains non-ascii characters > - email will default to pharo-dev(a)lists.pharo.org if missing > - website will default to a Google search for your name if a URL is missing > - image can be omitted if you have a Gravatar, else it becomes a smiley > - images will be rescaled to fit in 128x128, the URL needs to remain accessible > - description is a pure text String, no markup is allowed > - the description does not have to be too formal > - the page is statically generated, only then do changes take effect > > Regards, > > Sven, on behalf of the Pharo Board. > > PS: If you are curious, the code for generating this page can be found at > > http://www.smalltalkhub.com/#!/~Pharo/PharoPeople >

Aug. 14, 2013

Re: [Pharo-dev] inria jenkins got much faster

by Esteban Lorenzano

if you are using latest 2.0, that's probably because the integration of the RPackageSet cache. the previous slowdown was exponential, so big projects like moose took *really* much time to load. Esteban On Aug 14, 2013, at 11:43 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I just noticed that the Jenkins jobs got much faster. For example, the Moose job went from 36 minutes to 6 minutes. Or the Glamour job went from 11 minutes to 3 minutes. This is fantastic, but I do not know why the difference occurs. > > It seems that the difference started yesterday before 15:00: > https://ci.inria.fr/moose/job/moose-latest-dev-4.8/871/ (15:49 -- 6 min) > https://ci.inria.fr/moose/job/moose-latest-dev-4.8/870/ (02:49 -- 36 min) > > As it affected multiple jobs, I suspect it has to do with the infrastructure. > > Anyone has any idea as to why this happens? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Aug. 14, 2013