August 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Updating Pharo kernel

by Andrei Stebakov

Got the 1.2 image. Failed to load Gofer new squeaksource: 'MetacelloRepository'; package:'ConfigurationOfO2'; load. ((Smalltalk at: #ConfigurationOfO2) project version: '1.2') load: 'Dev'. Also failed to load Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load. ((Smalltalk at: #ConfigurationOfSeaside30) project version: '3.0.0-alpha5.15') load. Which loaded well with Pharo 1.1. Well, I guess it's a development image so this is expected... On Fri, Aug 20, 2010 at 2:13 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Yes > > andrei I think that what miguel is telling you is key. Having a reproducable process to load your code > is the best you can do to yourselves. > > Stef > > > >> 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 >> >> >> _______________________________________________ >> 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

[Pharo-project] Losing menus....

by StÃ©phane Ducasse

Hi I'm using a version of moose and now I cannot interact anymore with windows. When I click on them I get the world menu. If I open a tool, then I can interact with it but not with the windows I opened. Does anybody have an idea where this may come from? I tried to do a Ctrl. but nothing changes Stef

Aug. 20, 2010

Re: [Pharo-project] Updating Pharo kernel

by StÃ©phane Ducasse

Yes andrei I think that what miguel is telling you is key. Having a reproducable process to load your code is the best you can do to yourselves. Stef > 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 > > > _______________________________________________ > 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

> Where can I get 1.2 from? On the web page it says "not available yet." indeed this is strange. You can find them on the fileserver link. https://gforge.inria.fr/frs/?group_id=1299 >>>

Aug. 20, 2010

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