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

Re: [Pharo-project] ***HIGHLY IMPORTANT*** call for Configuration of Browsers and infrastructure

by Alexandre Bergel

I would love to have this running. I am ready to work on this next month when we will meet. Cheers, Alexandre On 16 May 2011, at 02:20, StÃ©phane Ducasse wrote: > Miguel, torsten, alexandre, mariano, dale and others > > This is *****REALLY***** important that we put in place an infrastructure and process + browser (already done) > to publish configurations for each projects. > We nearly have everything. > > Alexandre could we have a menu to freeze a configuration in a particular distribution repository? > > Guys could you take action on this point? > > > Stef -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 19, 2011

Re: [Pharo-project] Wishes for new ClassBuilder (toon?)

by Tudor Girba

We should organize a Sprint :) Cheers, Doru On 18 May 2011, at 23:01, StÃ©phane Ducasse wrote: > I'm planning to be at bern the friday 30 of june after tools so I would be happy to do that. > > Stef > > On May 18, 2011, at 10:31 PM, Toon Verwaest wrote: > >> Nope. That needs to be added. Sorry. If you have tests for the old classbuilder we can port them. Otherwise I can take the time at the next print I attend to do it; maybe together with somebody else. >> >> Toon >> >> On 05/18/2011 09:38 PM, StÃ©phane Ducasse wrote: >>> toon I looked at the code but do you have tests for the new class builder? >>> I could not find them. >>> >>> Stef >>> On May 18, 2011, at 6:17 PM, Toon Verwaest wrote: >>> >>>> The PlayOut classbuilder indeed separates this nicely. We have the distinction between the "installer" and the "builder". The builder uses an "installer" as a client and notifies it about stuff that happens. >>>> >>>> For example we have an "anonymous subclass builder" that's implemented like that. It basically just ignores most of the notifications of the builder since it doesn't really do anything. >>>> >>>> ... but of course this means that you need PlayOut ;) You can get an image at http://pinocchio.unibe.ch/~tverwaes/PlayOut.tar.gz >>>> >>>> caveats: >>>> - At the moment that system doesn't validate everything yet like the old classbuilder (since I wanted to freely change classes with any name) >>>> - it doesn't handle obsolete subclasses yet. Oh well ;) >>>> - it's still intertwined with our slots implementation, so it relies on Helvetia. But that can/should/will be fixed without changing the API. >>>> >>>> cheers, >>>> Toon >>>> >>>> On 05/18/2011 03:18 PM, Mariano Martinez Peck wrote: >>>>> Hi guys. As part of the Fuel project, one of the things we want to do (in fact, it is done) is to serialize classes. There want to have 3 possibilities: >>>>> 1) Do something like DiskProxy where you only save its global name and some selector to run when deserialing it >>>>> 2) Really searialize the whole class (following method dictionary, compiled methods, class pools and friend, etc) so that you can deserialize it in another image where such class is not present. >>>>> 3) Do the same as 2 but validating and installing the class in the system. >>>>> >>>>> For 2) what we want to do is just to serialize the class as any other object. As a result, we get a Class instance. Nothing is validated, nothing is added in Smalltalk globals, nothing is compiled. We do not use ClassBuilder at all. >>>>> >>>>> For 3) we want to do 2) plus validating and installing the class in the system. For validating I mean ALL the validations that the class builder does when creating or modifying a class. And for "installing in the system" I mean notify, put in Smalltalk globals, re compile what is needed, etc... >>>>> >>>>> ClassBuilder seems to do 2) and 3) together. So, what I would love to have in a new class builder is to have those two things separated. So that I can say to an object ClassManager validate: aClass or ClassManager installClassOnSystem: aClass. >>>>> >>>>> Do you think such thing is possible? Right now going through ClassBuilder and understand all the validations it does is really complicated :( >>>>> >>>>> Thanks in advance, >>>>> >>>>> -- >>>>> Mariano >>>>> http://marianopeck.wordpress.com >>>>> >>>> >>> >> >> > > -- www.tudorgirba.com "Value is always contextual."

May 18, 2011

Re: [Pharo-project] Problem with Pharo 1.3 in Windows

by Santiago Vidal

Thanks. The problem was the VM. I was trying with https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/lastSuccessfulBuild/…. It works after installing the Windows Installer Cheers 2011/5/18 Torsten Bergmann <astares(a)gmx.de> > How old is your Squeak.exe? > > It could also be that your Squeak.exe is a standard VM and the image > was saved with the faster Cog VM. Then it is not possible to reopen > it with a (slower) standard VM. > > Best solution to run Pharo is the Windows Installer, it includes > anything you need and is on the download page > http://www.pharo-project.org/pharo-download > > Currently for Pharo 1.2.1 and it includes both VM version (standard > and the faster Cog). > > Direct URL is > http://gforge.inria.fr/frs/download.php/28467/setup_pharo1.2.1-12345-releas… > > After that download the Pharo 1.3 or Pharo Core 1.3 image ZIP from > https://pharo-ic.lille.inria.fr/hudson/view/Pharo/ > > and put the image+changes into the same directory as the image > installed by the installer. > > If in doubt just ask. > > Bye > T. > > -- > NEU: FreePhone - kostenlos mobil telefonieren und surfen! > Jetzt informieren: http://www.gmx.net/de/go/freephone > > -- Ing. Santiago A. Vidal ISISTAN Research Institute UNICEN University Paraje Arroyo Seco Campus Universitario (B7001BBO) Tandil, Bs. As. - Argentina Phone: 54 2293 439840 Ext. 42 Fax: 54 2293 439681 Email: svidal(a)exa.unicen.edu.ar http://www.exa.unicen.edu.ar/~svidal

May 18, 2011

Re: [Pharo-project] Wishes for new ClassBuilder (toon?)

by StÃ©phane Ducasse

I'm planning to be at bern the friday 30 of june after tools so I would be happy to do that. Stef On May 18, 2011, at 10:31 PM, Toon Verwaest wrote: > Nope. That needs to be added. Sorry. If you have tests for the old classbuilder we can port them. Otherwise I can take the time at the next print I attend to do it; maybe together with somebody else. > > Toon > > On 05/18/2011 09:38 PM, StÃ©phane Ducasse wrote: >> toon I looked at the code but do you have tests for the new class builder? >> I could not find them. >> >> Stef >> On May 18, 2011, at 6:17 PM, Toon Verwaest wrote: >> >>> The PlayOut classbuilder indeed separates this nicely. We have the distinction between the "installer" and the "builder". The builder uses an "installer" as a client and notifies it about stuff that happens. >>> >>> For example we have an "anonymous subclass builder" that's implemented like that. It basically just ignores most of the notifications of the builder since it doesn't really do anything. >>> >>> ... but of course this means that you need PlayOut ;) You can get an image at http://pinocchio.unibe.ch/~tverwaes/PlayOut.tar.gz >>> >>> caveats: >>> - At the moment that system doesn't validate everything yet like the old classbuilder (since I wanted to freely change classes with any name) >>> - it doesn't handle obsolete subclasses yet. Oh well ;) >>> - it's still intertwined with our slots implementation, so it relies on Helvetia. But that can/should/will be fixed without changing the API. >>> >>> cheers, >>> Toon >>> >>> On 05/18/2011 03:18 PM, Mariano Martinez Peck wrote: >>>> Hi guys. As part of the Fuel project, one of the things we want to do (in fact, it is done) is to serialize classes. There want to have 3 possibilities: >>>> 1) Do something like DiskProxy where you only save its global name and some selector to run when deserialing it >>>> 2) Really searialize the whole class (following method dictionary, compiled methods, class pools and friend, etc) so that you can deserialize it in another image where such class is not present. >>>> 3) Do the same as 2 but validating and installing the class in the system. >>>> >>>> For 2) what we want to do is just to serialize the class as any other object. As a result, we get a Class instance. Nothing is validated, nothing is added in Smalltalk globals, nothing is compiled. We do not use ClassBuilder at all. >>>> >>>> For 3) we want to do 2) plus validating and installing the class in the system. For validating I mean ALL the validations that the class builder does when creating or modifying a class. And for "installing in the system" I mean notify, put in Smalltalk globals, re compile what is needed, etc... >>>> >>>> ClassBuilder seems to do 2) and 3) together. So, what I would love to have in a new class builder is to have those two things separated. So that I can say to an object ClassManager validate: aClass or ClassManager installClassOnSystem: aClass. >>>> >>>> Do you think such thing is possible? Right now going through ClassBuilder and understand all the validations it does is really complicated :( >>>> >>>> Thanks in advance, >>>> >>>> -- >>>> Mariano >>>> http://marianopeck.wordpress.com >>>> >>> >> > >

May 18, 2011

[Pharo-project] Problem with Pharo 1.3 in Windows

by Torsten Bergmann

How old is your Squeak.exe? It could also be that your Squeak.exe is a standard VM and the image was saved with the faster Cog VM. Then it is not possible to reopen it with a (slower) standard VM. Best solution to run Pharo is the Windows Installer, it includes anything you need and is on the download page http://www.pharo-project.org/pharo-download Currently for Pharo 1.2.1 and it includes both VM version (standard and the faster Cog). Direct URL is http://gforge.inria.fr/frs/download.php/28467/setup_pharo1.2.1-12345-releas… After that download the Pharo 1.3 or Pharo Core 1.3 image ZIP from https://pharo-ic.lille.inria.fr/hudson/view/Pharo/ and put the image+changes into the same directory as the image installed by the installer. If in doubt just ask. Bye T. -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone

May 18, 2011

Re: [Pharo-project] Wishes for new ClassBuilder (toon?)

by Toon Verwaest

Nope. That needs to be added. Sorry. If you have tests for the old classbuilder we can port them. Otherwise I can take the time at the next print I attend to do it; maybe together with somebody else. Toon On 05/18/2011 09:38 PM, StÃ©phane Ducasse wrote: > toon I looked at the code but do you have tests for the new class builder? > I could not find them. > > Stef > On May 18, 2011, at 6:17 PM, Toon Verwaest wrote: > >> The PlayOut classbuilder indeed separates this nicely. We have the distinction between the "installer" and the "builder". The builder uses an "installer" as a client and notifies it about stuff that happens. >> >> For example we have an "anonymous subclass builder" that's implemented like that. It basically just ignores most of the notifications of the builder since it doesn't really do anything. >> >> ... but of course this means that you need PlayOut ;) You can get an image at http://pinocchio.unibe.ch/~tverwaes/PlayOut.tar.gz >> >> caveats: >> - At the moment that system doesn't validate everything yet like the old classbuilder (since I wanted to freely change classes with any name) >> - it doesn't handle obsolete subclasses yet. Oh well ;) >> - it's still intertwined with our slots implementation, so it relies on Helvetia. But that can/should/will be fixed without changing the API. >> >> cheers, >> Toon >> >> On 05/18/2011 03:18 PM, Mariano Martinez Peck wrote: >>> Hi guys. As part of the Fuel project, one of the things we want to do (in fact, it is done) is to serialize classes. There want to have 3 possibilities: >>> 1) Do something like DiskProxy where you only save its global name and some selector to run when deserialing it >>> 2) Really searialize the whole class (following method dictionary, compiled methods, class pools and friend, etc) so that you can deserialize it in another image where such class is not present. >>> 3) Do the same as 2 but validating and installing the class in the system. >>> >>> For 2) what we want to do is just to serialize the class as any other object. As a result, we get a Class instance. Nothing is validated, nothing is added in Smalltalk globals, nothing is compiled. We do not use ClassBuilder at all. >>> >>> For 3) we want to do 2) plus validating and installing the class in the system. For validating I mean ALL the validations that the class builder does when creating or modifying a class. And for "installing in the system" I mean notify, put in Smalltalk globals, re compile what is needed, etc... >>> >>> ClassBuilder seems to do 2) and 3) together. So, what I would love to have in a new class builder is to have those two things separated. So that I can say to an object ClassManager validate: aClass or ClassManager installClassOnSystem: aClass. >>> >>> Do you think such thing is possible? Right now going through ClassBuilder and understand all the validations it does is really complicated :( >>> >>> Thanks in advance, >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >>> >> >

May 18, 2011

Re: [Pharo-project] Problem with Pharo 1.3 in Windows

by StÃ©phane Ducasse

Hi Santiago which VM are you using. Did you try with the VM shipped with the one-click image of 1.2.2? Stef > I downloaded the latest Pharo 1.3 image version (Core) but it doesn't work on windows 7. After the execution of the file squeak.exe (of Oneclick ) the Pharo window is suddenly closed. > Has anyone experienced the same problem? yes if you try to open the image with the wrong VM. > Cheers > Santiago > > -- > Ing. Santiago A. Vidal > ISISTAN Research Institute > UNICEN University > Paraje Arroyo Seco > Campus Universitario > (B7001BBO) Tandil, > Bs. As. - Argentina > Phone: 54 2293 439840 Ext. 42 > Fax: 54 2293 439681 > Email: svidal(a)exa.unicen.edu.ar > http://www.exa.unicen.edu.ar/~svidal

May 18, 2011

Re: [Pharo-project] Circle is gone

by Tudor Girba

Hi, We need it to represent the logic of paths in EyeSee and Mondrian. It's like Rectangle, only it's a Circle :). Cheers, Doru On 18 May 2011, at 21:03, StÃ©phane Ducasse wrote: >> What Circle? >>> >> >> Circle, from ST80... I think you removed it ;-) > > ahhhh that one? > :) > Doru why do you need that file? > >>> CircleMorph? >>> I do not see why it would be removed? -- www.tudorgirba.com "When people care, great things can happen."

May 18, 2011

[Pharo-project] Problem with Pharo 1.3 in Windows

by Santiago Vidal

I downloaded the latest Pharo 1.3 image version (Core) but it doesn't work on windows 7. After the execution of the file squeak.exe (of Oneclick ) the Pharo window is suddenly closed. Has anyone experienced the same problem? Cheers Santiago -- Ing. Santiago A. Vidal ISISTAN Research Institute UNICEN University Paraje Arroyo Seco Campus Universitario (B7001BBO) Tandil, Bs. As. - Argentina Phone: 54 2293 439840 Ext. 42 Fax: 54 2293 439681 Email: svidal(a)exa.unicen.edu.ar http://www.exa.unicen.edu.ar/~svidal

May 18, 2011

Re: [Pharo-project] Wishes for new ClassBuilder (toon?)

by StÃ©phane Ducasse

toon I looked at the code but do you have tests for the new class builder? I could not find them. Stef On May 18, 2011, at 6:17 PM, Toon Verwaest wrote: > The PlayOut classbuilder indeed separates this nicely. We have the distinction between the "installer" and the "builder". The builder uses an "installer" as a client and notifies it about stuff that happens. > > For example we have an "anonymous subclass builder" that's implemented like that. It basically just ignores most of the notifications of the builder since it doesn't really do anything. > > ... but of course this means that you need PlayOut ;) You can get an image at http://pinocchio.unibe.ch/~tverwaes/PlayOut.tar.gz > > caveats: > - At the moment that system doesn't validate everything yet like the old classbuilder (since I wanted to freely change classes with any name) > - it doesn't handle obsolete subclasses yet. Oh well ;) > - it's still intertwined with our slots implementation, so it relies on Helvetia. But that can/should/will be fixed without changing the API. > > cheers, > Toon > > On 05/18/2011 03:18 PM, Mariano Martinez Peck wrote: >> Hi guys. As part of the Fuel project, one of the things we want to do (in fact, it is done) is to serialize classes. There want to have 3 possibilities: >> 1) Do something like DiskProxy where you only save its global name and some selector to run when deserialing it >> 2) Really searialize the whole class (following method dictionary, compiled methods, class pools and friend, etc) so that you can deserialize it in another image where such class is not present. >> 3) Do the same as 2 but validating and installing the class in the system. >> >> For 2) what we want to do is just to serialize the class as any other object. As a result, we get a Class instance. Nothing is validated, nothing is added in Smalltalk globals, nothing is compiled. We do not use ClassBuilder at all. >> >> For 3) we want to do 2) plus validating and installing the class in the system. For validating I mean ALL the validations that the class builder does when creating or modifying a class. And for "installing in the system" I mean notify, put in Smalltalk globals, re compile what is needed, etc... >> >> ClassBuilder seems to do 2) and 3) together. So, what I would love to have in a new class builder is to have those two things separated. So that I can say to an object ClassManager validate: aClass or ClassManager installClassOnSystem: aClass. >> >> Do you think such thing is possible? Right now going through ClassBuilder and understand all the validations it does is really complicated :( >> >> Thanks in advance, >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > >

May 18, 2011