- Pharo-dev - lists.pharo.org

Re: [Pharo-project] about morphicSoundEventtcbkss0

by StÃ©phane Ducasse

Ok I will soon - merge all the polymorph override extensions - sort and put some classes in the correct package (morphicMouseWheel). > >> >>> I can't figure out what these methods have been used for exactly (probably for some conversion, > > I think they where used to migrate instances in old Projects / ImageSegments when you load them in a newer > system where the class layout was changed? Something like that... > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

March 5, 2011

Re: [Pharo-project] Pharo on Apple App Store

by Hilaire Fernandes

Le 04/03/2011 14:52, Esteban Lorenzano a Ã©crit : > There is also "design guidelines" for OSX, which you'll need to follow. But I'm uncertain on how this will affect pharo applications. > At the image there are some work to have good UI infrastructure matching a bit the design guideline. First job will be to work on a dedicated Polymoprh theme, I can help but I will not do it alone. Hilaire -- Education 0.2 -- http://blog.ofset.org/hilaire

March 5, 2011

Re: [Pharo-project] about morphicSoundEventtcbkss0

by Marcus Denker

> >> I can't figure out what these methods have been used for exactly (probably for some conversion, I think they where used to migrate instances in old Projects / ImageSegments when you load them in a newer system where the class layout was changed? Something like that... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 5, 2011

Re: [Pharo-project] Kernel

by StÃ©phane Ducasse

> If it's still a tracer when do you think you'll have a creator and what are you calling it? > > I do not understand your question :( > > I mean what are your plans regarding recompiling from source. What's the name of this step and when are you planning to start work on it? It's the step I'm really waiting for :) We do not know. We should continue to clean the system and the problem with source bootstrapping is that this is static in the sense that until the moment where we get a usable system we will have to trace changes in the kernel and push them back in the source bootstrap. So we want it too :) but I think that there is also a space for generating specific image based on dynamic collection. May be this one will be pineKernel :) http://uktv.co.uk/food/ingredient/aid/503745 "pignon" Stef

March 5, 2011

Re: [Pharo-project] Kernel

by StÃ©phane Ducasse

> Woot!!!!! Is this still a tracer or does it create a new kernel from source? If it's still a tracer when do you think you'll have a creator and what are you calling it? >From source may be a way to go but only for the smallest core. I would like to play with a source bootstrap. For now we use a tracer and we should learn also how to build dynamically cores (like aljandro nurturing) Stef

March 5, 2011

Re: [Pharo-project] Kernel

by StÃ©phane Ducasse

pavel consider hazel as a first end to end process. The contents is and will vary. We have to learn and understand what we want to put in and how we rebuild everything. Stef >>>>> >> -- Pavel >> > > I see, the base content of this image is defined as: > > (each category beginsWith: 'Kernel') or: > [(each category beginsWith: 'Collection') or: > [(each category = 'Exceptions-Kernel') or: > [(each category = 'Announcements-Core') or: > [(each category = 'System-Pools') or: > [(each category = 'System-Support') or: > [(each name == #EncodedCharSet) or: > [(each category == 'Multilingual-Encodings') or: > [(each category == 'Multilingual-Languages') or: > [(each name) == #Unicode]]]]]]]]]]. > > That is really radical shrinking :-) But it has great potential. I'll > try to play with it... > > -- Pavel >

March 5, 2011

Re: [Pharo-project] Kernel

by StÃ©phane Ducasse

On Mar 4, 2011, at 2:36 PM, Pavel Krivanek wrote: > On Fri, Mar 4, 2011 at 2:26 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> On Mar 4, 2011, at 2:24 PM, Pavel Krivanek wrote: >> >>> Great! >>> >>> does it have the same code base as the current Pharo-Kernel? >>> >> >> Yes. 1.3 latest Core. (I am just integrating the printon fix) >> >> Marcus > > So if we will be able to run startup scripts in this image, we be able > to use the Pharo-Kernel scripts for loading all the content of the > PharoCore back. Perfect! yes!!! > > -- Pavel > > >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> >

March 5, 2011

Re: [Pharo-project] Kernel

by StÃ©phane Ducasse

yes!!! The idea is that we have no a process where we can produce a core and in parallel continue to improve it. We should integrate all the seed bug entries and move on :) Great day today. I'm happy Stef On Mar 4, 2011, at 2:23 PM, Pavel Krivanek wrote: > Great! > > does it have the same code base as the current Pharo-Kernel? > > Cheers, > -- Pavel > > On Fri, Mar 4, 2011 at 1:51 PM, Benjamin > <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> Hello guys, >> >> >> I finally success (with the help of Igor) to trace and create a new Smalltalk kernel based on Pharo. The new born weight 2.2Mb and includes 230 classes ;) >> >> You can try it here: >> >> Gofer new >> squeaksource: 'PharoTaskForces'; >> package: 'SystemTracing'; >> load. >> >> Gofer new >> squeaksource: 'Seed'; >> package: 'Seed-HazelBuilder'; >> load. >> >> HazelTracer2 writeImage: 'hazel.image'. >> >> >> If you have an error in Point>>#printOn: , you can use this fix >> >> >> >> >> >> I want to thank Igor again, because he helps me a lot :) >> >> >> >> Ben >> >

March 5, 2011

Re: [Pharo-project] Kernel

by StÃ©phane Ducasse

COOOOL And I missed the birth, shit! Monday you have to tell me what you did to fix the last meters of the run. I see that it was boring to write slides :))) Stef On Mar 4, 2011, at 1:51 PM, Benjamin wrote: > Hello guys, > > > I finally success (with the help of Igor) to trace and create a new Smalltalk kernel based on Pharo. The new born weight 2.2Mb and includes 230 classes ;) > > You can try it here: > > Gofer new > squeaksource: 'PharoTaskForces'; > package: 'SystemTracing'; > load. > > Gofer new > squeaksource: 'Seed'; > package: 'Seed-HazelBuilder'; > load. > > HazelTracer2 writeImage: 'hazel.image'. > > > If you have an error in Point>>#printOn: , you can use this fix > <FixPointPrintOn.1.cs> > > > > I want to thank Igor again, because he helps me a lot :) > > > > Ben

March 5, 2011

Re: [Pharo-project] about morphicSoundEventtcbkss0

by StÃ©phane Ducasse

;) On Mar 4, 2011, at 10:35 PM, Adrian Lienhard wrote: > I can't figure out what these methods have been used for exactly (probably for some conversion, there are more such methods with weird names like layoutMorphbosfcepcbbochvimol0). They have no senders, and they have been in the image since at least 1998 (I checked in a 3.2 image). I don't think anybody will miss them ;) > > Cheers, > Adrian > > On Mar 4, 2011, at 21:22 , stephane ducasse wrote: > >> Hi guys >> >> does anybody have an idea why SmartRefStream would need to refer to MorphicUnknownEvent? >> >> morphicSoundEventtcbkss0 >> ^ MorphicUnknownEvent >> >> Stef (the Ultimate Random Refactorer) > >

March 5, 2011