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

[Pharo-project] <deprecated> annotation?

by Igor Stasenko

Hello, i know that we're already having #deprecated: , #deprecated: on: in: etc but one thing what i think useful about annotations that it is a way to indicate that method is deprecated without showing a warning. The problem with using messages, that if you deprecate something which used quite often by code, you will be spammed with deprecation warnings all the time. So, i think that in addition to messages, we can use these annotations, to indicate deprecated methods, in places where showing warning(s) are not feasible (for instance you cannot deprecate Deprecation>>showWarning, because it will lead to infinite recurtion) There could be variations in same way as with messages: <deprecated> <deprecated: '...' on: '..' in: '..'> etc. What you think? -- Best regards, Igor Stasenko AKA sig.

Aug. 16, 2011

Re: [Pharo-project] [Vm-dev] building Cog on 64 bits debian

by Igor Stasenko

On 16 August 2011 19:25, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 15 August 2011 15:38, laurent laffont <laurent.laffont(a)gmail.com> wrote: >> >> Hi Igor, >> now it works well. I've created CogOnDebian64Config but I cannot commit to VMMaker repository. So you can get it on: >> Gofer it >> Â squeaksource: 'LaurentLSandbox'; >> Â version: 'CMakeVMMaker-LaurentLaffont.135'; >> Â load >> InÂ CogOnDebian64Config comment: >> Used to build 32 bit Cog on Debian 64 bits. >> You need to prepare Debian this way: >> apt-get install ia32-libs libc6-dev-i386 gcc-multilib g++-multilib >> ln -s /usr/lib32/libSM.so.6 /usr/lib32/libSM.so >> ln -s /usr/lib32/libICE.so.6 /usr/lib32/libICE.so >> ln -s /usr/lib32/libGL.so.1 /usr/lib32/libGL.so >> ln -s /usr/lib32/libX11.so.6 /usr/lib32/libX11.so >> Then you can go on CogOnDebian64Config generateWithSources. >> >> Laurent. > > Laurent, please put these instructions on class comment, > so they won't get lost and buried in mailing list :) > This is what i did with windows configs, because memory is short and i > can even forget myself , what i need to install to build VM(s). > > And thanks for contribution! > Ehehe... you already did that. i should read mail more carefully! :) > > -- > Best regards, > Igor Stasenko AKA sig. > -- Best regards, Igor Stasenko AKA sig.

Aug. 16, 2011

Re: [Pharo-project] [Vm-dev] building Cog on 64 bits debian

by Igor Stasenko

On 15 August 2011 15:38, laurent laffont <laurent.laffont(a)gmail.com> wrote: > > Hi Igor, > now it works well. I've created CogOnDebian64Config but I cannot commit to VMMaker repository. So you can get it on: > Gofer it > Â squeaksource: 'LaurentLSandbox'; > Â version: 'CMakeVMMaker-LaurentLaffont.135'; > Â load > InÂ CogOnDebian64Config comment: > Used to build 32 bit Cog on Debian 64 bits. > You need to prepare Debian this way: > apt-get install ia32-libs libc6-dev-i386 gcc-multilib g++-multilib > ln -s /usr/lib32/libSM.so.6 /usr/lib32/libSM.so > ln -s /usr/lib32/libICE.so.6 /usr/lib32/libICE.so > ln -s /usr/lib32/libGL.so.1 /usr/lib32/libGL.so > ln -s /usr/lib32/libX11.so.6 /usr/lib32/libX11.so > Then you can go on CogOnDebian64Config generateWithSources. > > Laurent. Laurent, please put these instructions on class comment, so they won't get lost and buried in mailing list :) This is what i did with windows configs, because memory is short and i can even forget myself , what i need to install to build VM(s). And thanks for contribution! -- Best regards, Igor Stasenko AKA sig.

Aug. 16, 2011

Re: [Pharo-project] Phexample integrated with Autotest and OB (was ConfigurationOfPhexample (was #assert:equals: feels backwards))

by Sean P. DeNigris

Niko Schwarz-2 wrote: > > Phexample doesn't duplicate the logic of what is a change method, it > changes it. The rational is to allow the user to choose a speaking test > name, that accurately describes the test: > Yes, quite nicely in fact! The issue was that the "testXxx" was hardcoded in OB and Autotest, so Phexample tests were not picked up by Autotest, and couldn't be run through OB (because "shouldXxx" was not recognized as test methods). The patch was to OB and Autotest, integrating Phexample into the tools. Sean -- View this message in context: http://forum.world.st/Phexample-integrated-with-Autotest-and-OB-was-Configu… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Aug. 16, 2011

Re: [Pharo-project] Phexample integrated with Autotest and OB (was ConfigurationOfPhexample (was #assert:equals: feels backwards))

by niko.schwarz＠googlemail.com

Hi Sean! Phexample doesn't duplicate the logic of what is a change method, it changes it. The rational is to allow the user to choose a speaking test name, that accurately describes the test: shouldNicelyHandleNotifications And the like. Is this really in conflict with OB? Niko On 24.06.2011, at 21:01, Sean P. DeNigris wrote: > You can now have Phexample playing nicely with OB and Autotest... > * Autotest - I uploaded a new package (Autotest-Core-SeanDeNigris.5) that > will pick up Phexample and any other framework that defines tests > differently (it uses the class's #allTestSelectors method). > * OB - I uploaded a slice to the Pharo inbox that does the same for OB > (SLICE-Issue-4449-Feature-OB-can-handle-arbitrarily-defined-test-selectors-SeanDeNigris.1). > > All it took was removing some duplication in the system - TestCase, > Autotest, and OB were all repeating the "what is a test method" logic. > > HTH, > Sean > > -- > View this message in context: http://forum.world.st/Phexample-integrated-with-Autotest-and-OB-was-Configu… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- http://scg.unibe.ch/staff/Schwarz twitter.com/nes1983 Tel: +41786126354

Aug. 16, 2011

Re: [Pharo-project] Quicktime and MP3 harvested from Sophie

by Sean P. DeNigris

Marcus Denker-4 wrote: > > As soon as we add Sophie code, we need to add the Sophie license to the > license of Pahro. > I assumed we were just talking about making in loadable and useful, not adding it to the image. -- View this message in context: http://forum.world.st/Quicktime-and-MP3-harvested-from-Sophie-tp3747203p374… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Aug. 16, 2011

Re: [Pharo-project] Quicktime and MP3 harvested from Sophie

by StÃ©phane Ducasse

yes exactly Stef On Aug 16, 2011, at 1:49 PM, Frank Shearar wrote: > Surely the Smalltalk part's covered by _this_ licence? > > http://www.futureofthebook.org/sophie/about/license/ > > As opposed to the licence for Sophie 2.0. > > frank

Aug. 16, 2011

Re: [Pharo-project] Quicktime and MP3 harvested from Sophie

by StÃ©phane Ducasse

it is different from www.opensophie.org oops does not exist anymore.... http://www.ip-adress.com/whois/opensophie.org Stef On Aug 16, 2011, at 1:45 PM, Johannes Rasche wrote: > as you may know Sophie project is now rewritten in Java > > the license is: http://www.sophie2.org/users/licensing.html > > I would ask them, whether the same conditions apply for the Smalltalk code > > > Am 16.08.2011 um 12:24 schrieb Marcus Denker: > >> >> On Aug 16, 2011, at 11:02 AM, Johannes Rasche wrote: >> >>> Hi all, especially Sean >>> >>> assume my recent posting has been overseen, therefore again: >>> >>> I'm referring to Sean's harvesting of Sophie. >>> >>> Is somebody going to finalize this Quicktime harvesting ? >>> >> >> What is the license? >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> >

Aug. 16, 2011

Re: [Pharo-project] Quicktime and MP3 harvested from Sophie

by Johannes Rasche

Am 16.08.2011 um 15:27 schrieb Sean P. DeNigris: > > Johannes Rasche wrote: >> >> Is somebody going to finalize this Quicktime harvesting ? >> > Yes, you are apparently, lol! > OK, that's what I wanted to know > Here are the relevant discussions, some of which may help: > http://forum.world.st/Sophie-MPEG-Player-td2341744.html > http://forum.world.st/Playing-Flash-movies-in-image-was-Sophie-MPEG-Player-… > http://forum.world.st/ANN-SqueakMovieMorph-Alpha-plays-any-video-file-playa… > http://forum.world.st/How-I-can-do-SWF-files-playing-in-pharo-td3161269.html > http://forum.world.st/Playing-Flash-movies-in-image-td3167383i20.html I knew that stuff (except that last item) > Johannes Rasche wrote: >> >> mp3... didn't work for me... I assume it's due to less maintenance of the >> mpeg3 plugin >> > Are you using the Quicktime code to play them, or the other mp3 code I > posted about? IIRC, the mp3 plugin is not used for the Qt stuff, and the > other player was very old. Try Qt. I made a first attempt last week with Qt with and m4a file and failed - anyway I'll keep on > > HTH, > Sean > yes it helped for the moment - thanks so far Johannes > -- > View this message in context: http://forum.world.st/Quicktime-and-MP3-harvested-from-Sophie-tp3746691p374… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Aug. 16, 2011

Re: [Pharo-project] latest filesystem is unloadable

by StÃ©phane Ducasse

sorry 2.0.1 Now what I want to say is that I make sure that 2.0.1 is working. Now I did not check the other files. Camillo did a pass to clean a bit. For 1.4, I guess that we should integrate your changes in 1.4 Now I have no idea what colin did and it this is this change that broke something. BTW for Moose I would like to know if the latest version of RPackage is working. I got no news from my mail. Stef On Aug 16, 2011, at 12:03 AM, Tudor Girba wrote: > Hi, > > Continuous integration is there to test continuously. I was not complaining :). I just reported this issue, especially given that it is a critical one (not being able to load the code). The problem appeared today, because yesterday it worked fine. > > But, where is 2.2.1? I load the code from the Configuration from the official www.squeaksource.com/fs.html repository, and there the latest version is 2.0.2. > > Cheers, > Doru > > > On 15 Aug 2011, at 23:52, StÃ©phane Ducasse wrote: > >> Why do you want to load the bleeding edge since 2.2.1 is fully tagged for reproduceability. I never used loadBleedingEdge and I did not garantee that it would work. >> >> Stef >> >> >> On Aug 15, 2011, at 11:31 PM, Tudor Girba wrote: >> >>> Hi, >>> >>> The bleeding edge version of Filesystem is unloadable in Pharo 1.3 (see the attached debug log). >>> >>> To test it, try: >>> >>> Gofer new >>> squeaksource: 'fs'; >>> package: 'ConfigurationOfFilesystem'; >>> load. >>> (Smalltalk at: #ConfigurationOfFilesystem) loadBleedingEdge >>> >>> Cheers, >>> Doru >>> >>> -- >>> www.tudorgirba.com >>> >>> "From an abstract enough point of view, any two things are similar." >>> >>> >>> <PharoDebug.log.zip> >> >> > > -- > www.tudorgirba.com > > "Live like you mean it." > >

Aug. 16, 2011