- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [update 3.0] #30003

by Esteban Lorenzano

infrastructure is working :) On Mar 19, 2013, at 12:45 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Does it make sense to make updates when we have no working infrastructure? :-) > > -- Pavel > > On Tue, Mar 19, 2013 at 12:38 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> 30003 >> ----- >> >> 10046 Spec new version >> https://pharo.fogbugz.com/f/cases/10046 >> >> Diff information: >> http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Spec-Layout-EstebanLorenzano… >> http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Spec-Core-EstebanLorenzano.90 >> >> >

March 19, 2013

Re: [Pharo-project] [update 3.0] #30003

by Pavel Krivanek

Does it make sense to make updates when we have no working infrastructure? :-) -- Pavel On Tue, Mar 19, 2013 at 12:38 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > 30003 > ----- > > 10046 Spec new version > https://pharo.fogbugz.com/f/cases/10046 > > Diff information: > http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Spec-Layout-EstebanLorenzano… > http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Spec-Core-EstebanLorenzano.90 > >

March 19, 2013

[Pharo-project] [update 3.0] #30003

by Esteban Lorenzano

30003 ----- 10046 Spec new version https://pharo.fogbugz.com/f/cases/10046 Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Spec-Layout-EstebanLorenzano… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Spec-Core-EstebanLorenzano.90

March 19, 2013

Re: [Pharo-project] some little aif files

by Martin Dias

Hi I don't have any idea about how Sound library works. I did the following: 1) In Squeak 4.3 one click: FLSerializer serialize: SampledSound soundLibrary toFileNamed: 'soundLibrary.fuel'. 2) In Pharo 2.0: Gofer it url: 'http://smalltalkhub.com/mc/PharoExtras/Sound/main'; package: 'ConfigurationOfPharoSound'; load. (Smalltalk at: #ConfigurationOfPharoSound) project lastVersion load. SampledSound assimilateSoundsFrom: (FLMaterializer materializeFromFileNamed: 'soundLibrary.fuel'). SampledSound soundNames. "---> #('click' 'laugh' 'silence' 'chirp' 'splash' 'scratch' 'coyote' 'chomp' 'clink' 'scritch' 'meow' 'peaks' 'horn' 'camera' 'croak' 'warble' 'motor' 'scrape')." SampledSound soundNames do: [ :each | SampledSound playSoundNamed: each ]. ---> so it seemed to work, but I can't hear anything. I attach the fuel file, so to reproduce you can just put it in the image directory and evaluate my code above. Best, MartÃn On Tue, Mar 12, 2013 at 4:52 PM, stephane ducasse <stephane.ducasse(a)free.fr>wrote: > Simple > > they are in the SoundLibrary class variable of SampledSound > > Stef > > On Mar 12, 2013, at 4:23 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > > > There are creative commons sounds here: > > http://soundbible.com/free-sound-effects-3.html > > > > but they should be converted to aiff > > > > > > In other hand, seems like a good way of trying if Fuel can transfer > > objects from Squeak to Pharo. How can I find the instances in squeak, > > to try? > > > > On Tue, Mar 12, 2013 at 3:23 PM, StÃ©phane Ducasse > > <stephane.ducasse(a)inria.fr> wrote: > >> Hi guys > >> > >> the sound system requires to have some sounds loaded in the sound > library. > >> Befre it was croak, swirlâ¦. > >> Now since the files used to create the objects are probably gone from > age, I would like to find some little > >> aif files that we can load in the system. > >> does anybody have an idea of where I can find such aif free files? > >> > >> I could serialize the objects from the squeak image but I do not know > if this is a good idea. > >> > >> Stef > > > > >

March 19, 2013

[Pharo-project] Answering my own question on debugging the VM... Article by mariano

by phil＠highoctane.be

http://marianopeck.wordpress.com/2011/04/23/how-to-debug-the-vm/

March 19, 2013

Re: [Pharo-project] updated webdoc for 2.0

by Benjamin

Can't you use the seaside jenkins job ? Ben On Mar 19, 2013, at 9:23 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > still some bugs left, especially with selectors with "strange" characters > such as $: ;): > > http://pharo.gforge.inria.fr/doc/1.4/ > http://pharo.gforge.inria.fr/doc/2.0/ > > Once the configuration for seaside is released I can update the config of > webdoc to load everything under 2.0. Currently it will fail due to the > dependency to seaside. >

March 19, 2013

[Pharo-project] Next steps of the Pharo Kernel

by Pavel Krivanek

Hi, this is the list of things that should be done for at start of the Pharo 3.0 release: - make KeyChain package (UsersManager) standalone package or at least clean Kernel and MC dependencies. - include RPackage, probably will require to include the next Ring parts. - SoundSystem cleanup - rename Morphic package to Morphic-Base Cheers, -- Pavel

March 19, 2013

[Pharo-project] iOS VM > debugging flags

by phil＠highoctane.be

Hello, I am working on things at the VM level and the CMake files aren't including flags for debugging (I do end up in ARM assembly on bugs etc, which is interesting but not that much my cup of tea). Where/what should I use in order to get those flags set for the compilation and link? Somewhere in the CMake files I guess. I am currently looking around but if you know how, telling me would be sweet! TIA Phil

March 19, 2013

Re: [Pharo-project] 3.0 started

by Marcus Denker

On Mar 19, 2013, at 10:30 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Great, > > I created the new set of jobs for Pharo Kernel 3.0: > https://ci.inria.fr/pharo-contribution/view/Pharo-Kernel-3.0/ > > I created the new trigger on contribution server: > Pharo-3.0-Update-Trigger, it depends on > https://ci.inria.fr/pharo/view/3.0/job/Pharo-3.0-Update-Step-4-Publish > > Please create the copy of scripts named > http://pharo.gforge.inria.fr/ci/script/ciPharo30PharoVM.sh > > One note to the start of the 3.0 release. Last year when the version > 2.0 was started, the process at the beginning was very mythical, the > initial important commits were done without previous announcements and > it took quite long time before the derived projects like Pharo Kernel > were able be synchronized so a lot of integrations that went against > better modularization were integrated. And it is always better if such > issues can be seen as soon as possible. > We could try to pre-announce any change that is more than trivialâ¦ Marcus

March 19, 2013

Re: [Pharo-project] Pharo 3

by Esteban Lorenzano

yes, it is not so easy... and it does not worth it. Also, if you see, the removal of PackageInfo is scheduled for "june", more or less... and that's because I want all the time from now to there to remove all possible bugs in RPackage and be sure that the removal does not break the system :) anyway we have a summer release and we can include some changes (but not important ones, the idea is to include bugfixes) Esteban On Mar 19, 2013, at 7:29 AM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > > On Mar 19, 2013, at 12:48 AM, Ben Coman <btc(a)openInWorld.com> wrote: > >> I wonder.... If the March/April integrations don't break any existing API, and the new debugger runs in parallel with the old one, then maybe that might be a 2.x release, and move to 3.0 only when PackageInfo and the old debugger are ripped out. (of course all dependent on additional load and human resource availability) > > :) > > No doing a real release takes a lot of time. Now we are experimenting with been focused and chunking actions. > There will be tons of enh and fixes that are waiting for us also and many other actions that we do not list. > > Stef

March 19, 2013