- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Nautilus for Pharo 2.0?

by Noury Bouraqadi

Strange. I can't find it :-( Nautilus points to Nautilus 1.4. And I can't figure out the link. Noury On 25 avr. 2012, at 19:14, Mariano Martinez Peck wrote: > > > On Wed, Apr 25, 2012 at 6:20 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Since a couple of minutes, Nautilus is part of Nautilus 2.0 > > > s/Nautilus 2.0/Pharo 2.0 > > ;) > > > Ben > > On Apr 25, 2012, at 6:17 PM, Noury Bouraqadi wrote: > > > Any plans to have an auto-build on Jenkins? > > > > Noury > > -- > > http://twitter.com/#!/NouryBouraqadi > > http://www.kroobe.com/profile/noury > > > > > > Afin de contribuer au respect de l'environnement, > > merci de n'imprimer ce courriel qu'en cas de necessite > > > > Please consider the environment before you print > > > > > > > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com > Noury -- http://twitter.com/#!/NouryBouraqadi http://www.kroobe.com/profile/noury Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de necessite Please consider the environment before you print

April 26, 2012

Re: [Pharo-project] [ANN] ImageWriter, the SystemTracer's son

by Guillermo Polito

On Thu, Apr 26, 2012 at 1:52 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com>wrote: > Great news! > > I tried it on fresh 1.4 and I got: > SmalltalkImage(Object)>>doesNotUnderstand: #shutDownImage: > HzImageWriter>>writeImage: > Oups, bad packaging :). Will fix that asap. > > Do you plan to create a loader too? To be able to load objects from > different image file. > Hmm it's kind of the inverse operation :P. Don't think it's an important path for the project, but I can do it after for the lulz :). > > -- Pavel > > > On Thu, Apr 26, 2012 at 1:00 PM, Guillermo Polito > <guillermopolito(a)gmail.com> wrote: > > First public push of the first step of the hazelnut GSoC project :) > > > > In a nutshell > > > > For those who didn't know SystemTracer (the father): > > It is a tool that traces a graph of objects and writes an image from it. > > > > ImageWriter is a refactored, renamed and repackaged version of > SystemTracer2 > > with the following changes: > > - The image format can be provided as a parameter. > > - You have to provide an SmalltalkImage object as root to write the image > > (so in the future we can write bootstrap with this). > > - The object format was reified in objects. So the code is easier to > > understand + change, and people can learn how are our objects in memory > > easily :D. > > > > Right now, only 32 bit image format is supported. > > > > Structure > > > > - ImageWriter-Core has the image formats and the image writer in itself > > - ImageWriter-ObjectFormats contains objects that represent the memory > > layout of the objects and it's headers. > > - ImageWriter-Tests has some tests. > > > > Tests done > > > > - Only tested in Pharo-1.4 > > - There are specific tests written for the size and headers of the > objects > > - Also, I've written a Pharo-1.4 image and then run the tests in the > copied > > image. Only one failure compared to the original :) > > > > Known Bugs :) > > > > - WeakRegistryTest>>#testFinalizationWithOnFork is failing, and when I > run > > it manually it works :/. In the image I use to write, it does not > happen, > > only in the clone. > > - When opening the new image, the window is too small. It is not > > respecting the original image size. Don't know yet what is the problem. > > > > How To Download > > > > Gofer it > > squeaksource3: 'ImageWriter'; > > package: 'ImageWriter-Core'; > > package: 'ImageWriter-ObjectFormats'; > > package: 'ImageWriter-Tests'; > > load > > > > How to Use it > > > > HzImageWriter new > > format: HzCogImageFormat new; "or HzInterpreterImageFormat new" > > imageFileName: 'someFile.image'; > > onInitializeDo: [ "Some initialization?" ]; "this is optional, > > probably the same as an startup script, probably nonsense" > > writeImage: Smalltalk "Yes, we provide the our lovely global > Smalltak, > > but any SmalltalkImage instance could be" > > > > Next steps on this direction > > > > - support to write an isolated image different from the host one (I'll > know > > what I need later, hehe) > > - class comments! > > - metacello configuration > > - better api :) > > > > Links > > > > http://ss3.gemstone.com/ss/ImageWriter.html > > > > > > Cheers, > > Guille > >

April 26, 2012

Re: [Pharo-project] Pharo and the rest of the ecosystem

by Edgar De Cleene

El 4/26/12 5:19 AM, "Pavel Krivanek" <pavel.krivanek(a)gmail.com> escribiÃ³: > Hi Chris, > > the planed changes in Pharo are not autotelic but in most cases they > are replacements of current buggy and unmaintainable subsytems. > We also use automatic or semiautomatic tools for shrinking and > modularization of the image. For example uMorphic is generated moslty > automatically with subsequent hand-made cleanup. The original Squeak > KernelImage was generated in the similar way. But we use the results > of this tools only as the supporting experimental sources of > information. > The goals of Cuis, Spoon and Pharo are very very similar. Everyone > wants to have the "small, clean, understandable Smalltalk system". But > Pharo development is more evolutional and modularity is more valuable > than small size. > In Smalltalk it is easy to dive into the system and create something > like Cuis, Spoon or KernelImage. But this projects were created by a > single person and the degree of adoption of this forks is low. You may > for example to take the current PharoKernel and withing few days to > create a perfect small and clean kernel. It is cool intelectual > adventure but to make it generally used stuff is another story. > > -- Pavel Again i ask to fellows on all forks adopt the great work of years from Pavel. We should not waste valuable time and instead take PharoKernel and build our beloved pet on top of it. Edgar

April 26, 2012

Re: [Pharo-project] Nautilus for Pharo 2.0?

by Casimiro de Almeida Barreto

On 25-04-2012 20:18, Esteban Lorenzano wrote: > (...) > is: > > Gofer new > squeaksource3: 'Nautilus'; > package: 'ConfigurationOfNautilus'; > load. > > . > Thanks CdAB

April 26, 2012

Re: [Pharo-project] Confused about #isDirectory

by Sven Van Caekenberghe

Hi Alexis, On 26 Apr 2012, at 13:49, Alexis Parseghian wrote: > On Thu, Apr 26, 2012 at 12:47 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: >> '/tmp' asReference isDirectory. false >> '/private/tmp' asReference isDirectory. false >> >> '/Users/sven' asReference isDirectory. true >> '/Users/sven/Desktop' asReference isDirectory. true >> >> on Pharo 1.4 Mac OS X Cog VM. > > For what it's worth, working as expected on Linux (using either > deprecated asReference or asFileReference) : > > /tmp true > /home/alexisp true > /nosuchpath false > > Pharo 1.4-14438 > 'CoInterpreter VMMaker-oscog-EstebanLorenzano.139 uuid: > 5aa53979-d7d8-4ca3-91fe-cfc3b4109c33 Jan 26 2012, > StackToRegisterMappingCogit VMMaker-oscog-EstebanLorenzano.139 uuid: > 5aa53979-d7d8-4ca3-91fe-cfc3b4109c33 Jan 26 2012, > https://git.gitorious.org/cogvm/blessed.git Commit: > e49a136ea9fe909dd5ba3cdeffac8f61cce27c9f Date: Thu Jan 26 17:38:06 > 2012 +0100 By: Camillo Bruni <camillobruni(a)gmail.com>' I was afraid of that ;-) I don't have #asFileReference in my Pharo 1.4 image and #asReference is not deprecated, is that new ? Sven

April 26, 2012

Re: [Pharo-project] [ANN] ImageWriter, the SystemTracer's son

by Pavel Krivanek

Great news! I tried it on fresh 1.4 and I got: SmalltalkImage(Object)>>doesNotUnderstand: #shutDownImage: HzImageWriter>>writeImage: Do you plan to create a loader too? To be able to load objects from different image file. -- Pavel On Thu, Apr 26, 2012 at 1:00 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > First public push of the first step of the hazelnut GSoC project :) > > In a nutshell > > For those who didn't know SystemTracer (the father): > It is a tool that traces a graph of objects and writes an image from it. > > ImageWriter is a refactored, renamed and repackaged version of SystemTracer2 > with the following changes: > - The image format can be provided as a parameter. > - You have to provide an SmalltalkImage object as root to write the image > (so in the future we can write bootstrap with this). > - The object format was reified in objects.Â So the code is easier to > understand + change, and people can learn how are our objects in memory > easily :D. > > Right now, only 32 bit image format is supported. > > Structure > > - ImageWriter-Core has the image formats and the image writer in itself > - ImageWriter-ObjectFormats contains objects that represent the memory > layout of the objects and it's headers. > - ImageWriter-Tests has some tests. > > Tests done > > Â - Only tested in Pharo-1.4 > Â - There are specific tests written for the size and headers of the objects > Â - Also, I've written a Pharo-1.4 image and then run the tests in the copied > image.Â Only one failure compared to the original :) > > Known Bugs :) > > Â - WeakRegistryTest>>#testFinalizationWithOnFork is failing, and when I run > it manually it works :/.Â In the image I use to write, it does not happen, > only in the clone. > Â - When opening the new image, the window is too small.Â It is not > respecting the original image size.Â Don't know yet what is the problem. > > How To Download > > Gofer it > Â Â Â squeaksource3: 'ImageWriter'; > Â Â Â package: 'ImageWriter-Core'; > Â Â Â package: 'ImageWriter-ObjectFormats'; > Â Â Â package: 'ImageWriter-Tests'; > Â Â Â load > > How to Use it > > Â HzImageWriter new > Â Â Â format: HzCogImageFormat new; "or HzInterpreterImageFormat new" > Â Â Â imageFileName: 'someFile.image'; > Â Â Â onInitializeDo: [ "Some initialization?" ];Â Â "this is optional, > probably the same as an startup script, probably nonsense" > Â Â Â writeImage: SmalltalkÂ "Yes, we provide the our lovely global Smalltak, > but any SmalltalkImage instance could be" > > Next steps on this direction > > Â - support to write an isolated image different from the host one (I'll know > what I need later, hehe) > Â - class comments! > Â - metacello configuration > Â - better api :) > > Links > > http://ss3.gemstone.com/ss/ImageWriter.html > > > Cheers, > Guille

April 26, 2012

Re: [Pharo-project] Confused about #isDirectory

by Alexis Parseghian

On Thu, Apr 26, 2012 at 12:47 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > '/tmp' asReference isDirectory. false > '/private/tmp' asReference isDirectory. false > > '/Users/sven' asReference isDirectory. true > '/Users/sven/Desktop' asReference isDirectory. true > > on Pharo 1.4 Mac OS X Cog VM. For what it's worth, working as expected on Linux (using either deprecated asReference or asFileReference) : /tmp true /home/alexisp true /nosuchpath false Pharo 1.4-14438 'CoInterpreter VMMaker-oscog-EstebanLorenzano.139 uuid: 5aa53979-d7d8-4ca3-91fe-cfc3b4109c33 Jan 26 2012, StackToRegisterMappingCogit VMMaker-oscog-EstebanLorenzano.139 uuid: 5aa53979-d7d8-4ca3-91fe-cfc3b4109c33 Jan 26 2012, https://git.gitorious.org/cogvm/blessed.git Commit: e49a136ea9fe909dd5ba3cdeffac8f61cce27c9f Date: Thu Jan 26 17:38:06 2012 +0100 By: Camillo Bruni <camillobruni(a)gmail.com>'

April 26, 2012

[Pharo-project] Athens & SVG (was: Re: new icon set )

by Torsten Bergmann

Fernando wrote >Thanks! I wasnt aware of that projec. Also look at Pastell which allows for easy XPath like access to XML. See http://astares.blogspot.de/2010/01/pharosqueak-and-xml.html for an example. Bye T. -- NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a

April 26, 2012

[Pharo-project] Pharo Kernel 1.4 Reload Tests-Unix - Build # 86 - Still unstable!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

April 26, 2012

[Pharo-project] [ANN] ImageWriter, the SystemTracer's son

by Guillermo Polito

First public push of the first step of the hazelnut GSoC project :) *In a nutshell* For those who didn't know SystemTracer (the father): It is a tool that traces a graph of objects and writes an image from it. ImageWriter is a refactored, renamed and repackaged version of SystemTracer2 with the following changes: - The image format can be provided as a parameter. - You have to provide an SmalltalkImage object as root to write the image (so in the future we can write bootstrap with this). - The object format was reified in objects. So the code is easier to understand + change, and people can learn how are our objects in memory easily :D. Right now, only 32 bit image format is supported. *Structure* - ImageWriter-Core has the image formats and the image writer in itself - ImageWriter-ObjectFormats contains objects that represent the memory layout of the objects and it's headers. - ImageWriter-Tests has some tests. *Tests done* - Only tested in Pharo-1.4 - There are specific tests written for the size and headers of the objects - Also, I've written a Pharo-1.4 image and then run the tests in the copied image. Only one failure compared to the original :) *Known Bugs :)* - WeakRegistryTest>>#testFinalizationWithOnFork is failing, and when I run it manually it works :/. In the image I use to write, it does not happen, only in the clone. - When opening the new image, the window is too small. It is not respecting the original image size. Don't know yet what is the problem. *How To Download* Gofer it squeaksource3: 'ImageWriter'; package: 'ImageWriter-Core'; package: 'ImageWriter-ObjectFormats'; package: 'ImageWriter-Tests'; load *How to Use it* HzImageWriter new format: HzCogImageFormat new; "or HzInterpreterImageFormat new" imageFileName: 'someFile.image'; onInitializeDo: [ "Some initialization?" ]; "this is optional, probably the same as an startup script, probably nonsense" writeImage: Smalltalk "Yes, we provide the our lovely global Smalltak, but any SmalltalkImage instance could be" *Next steps on this direction* - support to write an isolated image different from the host one (I'll know what I need later, hehe) - class comments! - metacello configuration - better api :) *Links* http://ss3.gemstone.com/ss/ImageWriter.html Cheers, Guille

April 26, 2012