- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Updating Pharo kernel

by Andrei Stebakov

Where can I get 1.2 from? On the web page it says "not available yet." On Fri, Aug 20, 2010 at 12:19 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > yes :) > If you take an unstable image you can always select software update. > Now this is disable in dev images. > I suggest to use 1.2 if you want to fix the system > > Stef > > On Aug 20, 2010, at 5:46 PM, Andrei Stebakov wrote: > >> Is there a procedure similar to Squeak for updating to the latest kernel? >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 20, 2010

Re: [Pharo-project] Updating Pharo kernel

by Mariano Martinez Peck

pharo kernel or pharo core? they are different things ;) On Fri, Aug 20, 2010 at 6:49 PM, Andrei Stebakov <lispercat(a)gmail.com>wrote: > But let's say I already have an image with a bunch of libraries > installed and tweaked so they work. > Is it possible to update only Pharo kernel so I can later use it with > CogVM (which needs some latest updates)? > > On Fri, Aug 20, 2010 at 12:19 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > yes :) > > If you take an unstable image you can always select software update. > > Now this is disable in dev images. > > I suggest to use 1.2 if you want to fix the system > > > > Stef > > > > On Aug 20, 2010, at 5:46 PM, Andrei Stebakov wrote: > > > >> Is there a procedure similar to Squeak for updating to the latest > kernel? > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 20, 2010

Re: [Pharo-project] Updating Pharo kernel

by Miguel Enrique CobÃ¡ MartÃnez

El vie, 20-08-2010 a las 12:49 -0400, Andrei Stebakov escribiÃ³: > But let's say I already have an image with a bunch of libraries > installed and tweaked so they work. > Is it possible to update only Pharo kernel so I can later use it with > CogVM (which needs some latest updates)? The problem with this is that carries the old squeak way to work. That is, a image is used and modified everywhere without a way to reliably reproduce the steps to rebuild the image. That's even worse when you accidentally destroy or render your image unusable. The modern way or the pharo way is to have everything in monticello packages. >From there you can reload your code in any new image by just loading your monticello packages in the new image. Now, you can automate this procedure either: - writing a script to evaluate in a workspace that uses Gofer or Installer to fetch and install the set of packages - (recommended) write your Metacello ConfigurationOfMyPackage where you put the packages that comprise your application, plus any other dependency that is needed for it to work. Metacello then uses gofer to load all your code and its dependencies from anywhere, either locally or remotely and build your image from a given new image. This way, you can load your code in new images with just a do-it in a workspace and to check if works correctly on newer images. Cheers. > > On Fri, Aug 20, 2010 at 12:19 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > yes :) > > If you take an unstable image you can always select software update. > > Now this is disable in dev images. > > I suggest to use 1.2 if you want to fix the system > > > > Stef > > > > On Aug 20, 2010, at 5:46 PM, Andrei Stebakov wrote: > > > >> Is there a procedure similar to Squeak for updating to the latest kernel? > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Aug. 20, 2010

Re: [Pharo-project] Updating Pharo kernel

by Andrei Stebakov

But let's say I already have an image with a bunch of libraries installed and tweaked so they work. Is it possible to update only Pharo kernel so I can later use it with CogVM (which needs some latest updates)? On Fri, Aug 20, 2010 at 12:19 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > yes :) > If you take an unstable image you can always select software update. > Now this is disable in dev images. > I suggest to use 1.2 if you want to fix the system > > Stef > > On Aug 20, 2010, at 5:46 PM, Andrei Stebakov wrote: > >> Is there a procedure similar to Squeak for updating to the latest kernel? >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 20, 2010

Re: [Pharo-project] Updating Pharo kernel

by StÃ©phane Ducasse

yes :) If you take an unstable image you can always select software update. Now this is disable in dev images. I suggest to use 1.2 if you want to fix the system Stef On Aug 20, 2010, at 5:46 PM, Andrei Stebakov wrote: > Is there a procedure similar to Squeak for updating to the latest kernel? > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 20, 2010

[Pharo-project] methods being overridden

by Robert Sirois

What could cause methods to be overridden with code from other methods when copying classes (right click > copy)? Either that, or something went wrong when I imported an image via the config portal in the dispatcher (seaside). It looks like everything subclassing from WAComponent had all their methods overridden with byte code. Is this a better topic for the seaside list? Thanks,RS

Aug. 20, 2010

[Pharo-project] Updating Pharo kernel

by Andrei Stebakov

Is there a procedure similar to Squeak for updating to the latest kernel?

Aug. 20, 2010

Re: [Pharo-project] FW: [Seaside] Changes file too big

by Sven Van Caekenberghe

Robert, On 20 Aug 2010, at 16:19, Robert Sirois wrote: > Adding an image to a WAFileLibrary (100 - 150kb) increases the changes file size by 0.5 mb consistently. That is perfectly normal: the textual representation of your binary image ( ^ #( 34 34 4 3 23 ... 34 2 2) asByteArray ) is many times larger than the bytes themselves. This representation is in a method's source code. All method source code is written to the changes file, every time it changes. WAFileLibrary is great because it is super easy, flexible and convenient, but it is not meant for heavy use. Sven

Aug. 20, 2010

Re: [Pharo-project] Fwd: [Esug-list] The SOM Family

by Michael Haupt

... thanks. ;-) On Fri, Aug 20, 2010 at 4:29 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > > Begin forwarded message: > >> From: Michael Haupt <mhaupt(a)gmail.com> >> Date: September 17, 2009 5:48:57 PM GMT+02:00 >> To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org>, ESUG Mailing list <esug-list(a)lists.esug.org> >> Subject: [Esug-list] The SOM Family >> Reply-To: ESUG Mailing list <esug-list(a)lists.esug.org> >> >> Hi, >> >> apologies for cross-posting ... >> >> At ESUG, I gave a short presentation on the SOM family of virtual >> machine implementations (in Java, C, C++, and Squeak), and also said >> that the VMs were not yet available. >> >> Well, *that* has changed now. They're available. They're MIT licensed. >> They're fun. They're there for youse to use. ;-) >> >> I have one request: if you use them, please let me know. I'm curious >> in what scenarios they're deployed. Also, please let me know about any >> problems, suggestions for improvement, and such. >> >> Oh, ere I forget: http://www.hpi.uni-potsdam.de/swa/projects/som :-) >> >> Best, >> >> Michael >> _______________________________________________ >> Esug-list mailing list >> Esug-list(a)lists.esug.org >> http://lists.esug.org/listinfo/esug-list > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 20, 2010

[Pharo-project] Fwd: [Esug-list] The SOM Family

by StÃ©phane Ducasse

Begin forwarded message: > From: Michael Haupt <mhaupt(a)gmail.com> > Date: September 17, 2009 5:48:57 PM GMT+02:00 > To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org>, ESUG Mailing list <esug-list(a)lists.esug.org> > Subject: [Esug-list] The SOM Family > Reply-To: ESUG Mailing list <esug-list(a)lists.esug.org> > > Hi, > > apologies for cross-posting ... > > At ESUG, I gave a short presentation on the SOM family of virtual > machine implementations (in Java, C, C++, and Squeak), and also said > that the VMs were not yet available. > > Well, *that* has changed now. They're available. They're MIT licensed. > They're fun. They're there for youse to use. ;-) > > I have one request: if you use them, please let me know. I'm curious > in what scenarios they're deployed. Also, please let me know about any > problems, suggestions for improvement, and such. > > Oh, ere I forget: http://www.hpi.uni-potsdam.de/swa/projects/som :-) > > Best, > > Michael > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/listinfo/esug-list

Aug. 20, 2010