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

[Pharo-project] ConfigurationOfAlien

by Fernando olivero

Hi, just added ConfigurationOfAlien to the MetacelloRepository. To load Alien using Metacello configurations evaluate Gofer new url: 'http://www.squeaksource.com/MetacelloRepository' ; package: 'ConfigurationOfAlien'; load. (ConfigurationOfAlien project version:'1.0') load. ( John please update the ALIEN squeaksource page with the previous text ) Note: Using the available MAC VM i the pharo page, you should be able to run the test correctly. ( the alien plugin 'IA32ABI 7 May 2009 (e)', is compiled inside that vm, there's no need for the external one) Metacello question: If i want load Alien Examples, the package Alien-MacOSExamples, but don't want to add them to the above configuration , should i create a new #versionXXX method ? Or provide a class side method like for example ConfigurationOfAlien>>loadWithMaxOsExamples (ConfigurationOfAlien project version:'1.0') load:#('Alien-MacOsExamples') Saludos, Fernando

Jan. 13, 2010

Re: [Pharo-project] How can I remove a picture from background ?

by Gary Chambers

Well, still many loose ends around as we refactor, that's for sure! As for understanding Morphic, there's so much that none can know all... hence trying to simplify with Pharo. Some good stuff, some bad and even when you think you know, there's always something that comes up ,either too easy or next to impossible... Regards, Gary ----- Original Message ----- From: CÃ©drick BÃ©ler To: Pharo-project(a)lists.gforge.inria.fr Sent: Wednesday, January 13, 2010 4:31 PM Subject: Re: [Pharo-project] How can I remove a picture from background ? 2010/1/13 Gary Chambers <gazzaguru2(a)btinternet.com> All about getting to know how Morphic works... or sometimes doesn't, as you explore further down the rabbit hole! quite scaring actually :) For instance, for background, I had a quick look at PasteUpMorph and there is backgroundMorph which might be more appropriate but I find no hooks... Anyway... now I know I still don't want to understand morphic :) Regards, Gary ----- Original Message ----- From: Mariano Martinez Peck To: Pharo-project(a)lists.gforge.inria.fr Sent: Wednesday, January 13, 2010 3:56 PM Subject: Re: [Pharo-project] How can I remove a picture from background ? hahahahha why everybody had the same idea and I didn't ? hahah I seems I ask something very stupid... Thanks anyway CÃ©drick 2010/1/13 CÃ©drick BÃ©ler <cdrick65(a)gmail.com> something like (not sure though): World color: Color white 2010/1/13 Mariano Martinez Peck <marianopeck(a)gmail.com> Hi: I do something like this: Form setBackgroundFromImageFileNamed: '/Users/mariano/Pharo/body.png' And the picture is set as background, but then I don't know how to remove it. I look for a while but I didn't find anything. Thanks for the help, Mariano _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- CÃ©drick _______________________________________________ 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 -- CÃ©drick ------------------------------------------------------------------------------ _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 13, 2010

Re: [Pharo-project] How can I remove a picture from background ?

by CÃ©drick BÃ©ler

2010/1/13 Gary Chambers <gazzaguru2(a)btinternet.com> > All about getting to know how Morphic works... or sometimes doesn't, as > you explore further down the rabbit hole! > quite scaring actually :) For instance, for background, I had a quick look at PasteUpMorph and there is backgroundMorph which might be more appropriate but I find no hooks... Anyway... now I know I still don't want to understand morphic :) > > Regards, Gary > > ----- Original Message ----- > *From:* Mariano Martinez Peck <marianopeck(a)gmail.com> > *To:* Pharo-project(a)lists.gforge.inria.fr > *Sent:* Wednesday, January 13, 2010 3:56 PM > *Subject:* Re: [Pharo-project] How can I remove a picture from background > ? > > hahahahha why everybody had the same idea and I didn't ? hahah > > I seems I ask something very stupid... > > Thanks anyway CÃ©drick > > 2010/1/13 CÃ©drick BÃ©ler <cdrick65(a)gmail.com> > >> something like (not sure though): >> World color: Color white >> >> 2010/1/13 Mariano Martinez Peck <marianopeck(a)gmail.com> >> >>> Hi: I do something like this: >>> >>> Form setBackgroundFromImageFileNamed: '/Users/mariano/Pharo/body.png' >>> >>> And the picture is set as background, but then I don't know how to remove >>> it. I look for a while but I didn't find anything. >>> >>> Thanks for the help, >>> >>> Mariano >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> CÃ©drick >> >> _______________________________________________ >> 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 > -- CÃ©drick

Jan. 13, 2010

Re: [Pharo-project] EventSensor vs EventInputSensor

by Miguel Enrique CobÃ¡ Martinez

El miÃ©, 13-01-2010 a las 17:15 +0100, Fernando olivero escribiÃ³: > Sensor class = InputEventSensor true > Now, it only remains to know if this should be a permanent change in the Pharo image or just a preloadDoit of the metacello configuration of Magma. Stef? What do you think? Cheers > > On Jan 13, 2010, at 5:08 PM, Chris Muller wrote: > > > Sensor class = InputEventSensor > > > _______________________________________________ > 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

Jan. 13, 2010

Re: [Pharo-project] NewCompiler load on PharoCore

by Miguel Enrique CobÃ¡ Martinez

El miÃ©, 13-01-2010 a las 18:08 +0200, Igor Stasenko escribiÃ³: > Can someone clarify, why WriteBarrier depends on compiler (new > compiler or old compiler - not really important). > I just wonder what compiler functionality its depends on. WriteBarrier uses the class BytecodeGenerator that is part of the package NewCompiler (that is currently on rewrite for the closure images). Why it need it and how it use it, I really don't know. I have only a vague idea of what WriteBarrier does, and as Mariano said, I use Magma but never used or activated the WriteBarrier functionality of it. Cheers > > 2010/1/13 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > > > > On Wed, Jan 13, 2010 at 5:02 PM, Chris Muller <asqueaker(a)gmail.com> wrote: > >> > >> 2010/1/12 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >> > Magma depends on NewCompiler ??? > >> > >> No, WriteBarrier depends on NewCompiler. > >> > >> Magma can, at the explicit option of the user, turn on the > >> WriteBarrier option if the WriteBarrier package is present. > >> WriteBarrier used to be self-contained, later it became dependent on > >> NewCompiler. > >> > >> Unless the WriteBarrier option is switched on by the user, its > >> presence or absence in the image (as well as NewCompiler) has no > >> effect on Magma. > >> > > > > Thanks for the clarification Chris. It was strange for me that as I used > > Magma a couple of times and I never installed WriteBarrier neither > > NewCompiler. > > > > Cheers > > > > Mariano > > > > > >> > >> - Chris > >> > >> _______________________________________________ > >> 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 > > > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > 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

Jan. 13, 2010

Re: [Pharo-project] Comments on Metacello and ConfigurationOfExternalWebBrowser

by Mariano Martinez Peck

2010/1/13 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > El miÃ©, 13-01-2010 a las 16:20 +0100, Mariano Martinez Peck escribiÃ³: > > > > > > >#commonSqueak or something like that , which is for pharo and > > squeak (but > > >not gemstone) > > > > It's called "squeakCommon" and I have no idea if "gemstone" > > means > > the pharo based gemstone image > > > > Not, that's GemTools. Gemstone, is the Smalltalk gemstone. > > > > or the server. Anything I see is that > > FFI config also uses #common and developers for it are > > Esteban, you and > > Dale. > > > > I didn't do the FFI ;) In addition, if you see all the confs I > > announced I put everything in #pharo because I didn't test it in > > squeak. Actually, at the beginning, I put everything in #common but > > then Dale suggest me to put them in #pharo if I only tested there, and > > that's what I did. If them someone test it in squeak or gemstone, and > > works ok, then we can put it as common. > > > > So if I only tested on Pharo I shouldn't use #common but #pharo and when > someone makes it work on Squeak the will change it to #commonSqueak and > when someone else verifies that works in every know platform he/she will > have to change it to #common? > At least that's what I understood. But maybe I am wrong. Let's hear the opinion of our god Dale :) > > > > But yes, everything that uses FFI, I think should be only in Squeak > > and Pharo as Gemstone does not support a "similar" FFI. > > > > > > So you should know ;) > > > > However - what if Metacello gets ported. Do we have an > > "commercialSmalltalksCommon", "vastAndVW", ... or any other > > combination or do we have to maintain a spec for any each > > platform. > > > > Would'nt it be better to have a spec and tell on which > > (multiple) > > targets it is able to run. > > > > > > +1 I totally agree. That solution doesn't scale. The ideal would be > > if for: can also an array, as load: do for example: > > > > You can do load: 'aGroup' or load: #('group1' 'group2' ) > > > > So, maybe would be cool to do: > > > > for: #('squeak' 'pharo' .... ) > > > > what do you think? > > > > > > > > Questions over Questions ... > > > > Bye > > T. > > > > > > > > > > -- > > Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla > > Firefox 3.5 - > > sicherer, schneller und einfacher! > > http://portal.gmx.net/de/go/chbrowser > > > > _______________________________________________ > > 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 >

Jan. 13, 2010

Re: [Pharo-project] Comments on Metacello and ConfigurationOfExternalWebBrowser

by Miguel Enrique CobÃ¡ Martinez

El miÃ©, 13-01-2010 a las 16:20 +0100, Mariano Martinez Peck escribiÃ³: > > > >#commonSqueak or something like that , which is for pharo and > squeak (but > >not gemstone) > > It's called "squeakCommon" and I have no idea if "gemstone" > means > the pharo based gemstone image > > Not, that's GemTools. Gemstone, is the Smalltalk gemstone. > > or the server. Anything I see is that > FFI config also uses #common and developers for it are > Esteban, you and > Dale. > > I didn't do the FFI ;) In addition, if you see all the confs I > announced I put everything in #pharo because I didn't test it in > squeak. Actually, at the beginning, I put everything in #common but > then Dale suggest me to put them in #pharo if I only tested there, and > that's what I did. If them someone test it in squeak or gemstone, and > works ok, then we can put it as common. > So if I only tested on Pharo I shouldn't use #common but #pharo and when someone makes it work on Squeak the will change it to #commonSqueak and when someone else verifies that works in every know platform he/she will have to change it to #common? > But yes, everything that uses FFI, I think should be only in Squeak > and Pharo as Gemstone does not support a "similar" FFI. > > > So you should know ;) > > However - what if Metacello gets ported. Do we have an > "commercialSmalltalksCommon", "vastAndVW", ... or any other > combination or do we have to maintain a spec for any each > platform. > > Would'nt it be better to have a spec and tell on which > (multiple) > targets it is able to run. > > > +1 I totally agree. That solution doesn't scale. The ideal would be > if for: can also an array, as load: do for example: > > You can do load: 'aGroup' or load: #('group1' 'group2' ) > > So, maybe would be cool to do: > > for: #('squeak' 'pharo' .... ) > > what do you think? > > > > Questions over Questions ... > > Bye > T. > > > > > -- > Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla > Firefox 3.5 - > sicherer, schneller und einfacher! > http://portal.gmx.net/de/go/chbrowser > > _______________________________________________ > 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

Jan. 13, 2010

Re: [Pharo-project] EventSensor vs EventInputSensor

by Fernando olivero

Sensor class = InputEventSensor true On Jan 13, 2010, at 5:08 PM, Chris Muller wrote: > Sensor class = InputEventSensor

Jan. 13, 2010

Re: [Pharo-project] NewCompiler load on PharoCore

by Lukas Renggli

> Can someone clarify, why WriteBarrier depends on compiler (new > compiler or old compiler - not really important). > I just wonder what compiler functionality its depends on. WriteBarrier introduces something like immutable objects at the language level by rewriting all state access in an anonymous subclass. Having a compiler at hand certainly makes things simpler. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 13, 2010

Re: [Pharo-project] EventSensor vs EventInputSensor

by Chris Muller

Great idea Miguel. I believe this will not only work just fine, but will allow models in Pharo which reference the "Sensor" (something I doubt has ever happened, or ever will) to persist and materialize properly. *Provided*, that, in Pharo: Sensor class = InputEventSensor answers "true", which I'm assuming it does (can't launch a Pharo image at the moment to be sure). - Chris 2010/1/12 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com>: > I have a question about EventSensor. > > In Pharo doesn't exists anymore, it was replaced by InputEventSensor > that has this class comment: > > An InputEventSensor is a replacement for the old Morphic EventSensor > framework. > It updates its state when events are received so that all state based > users of Sensor (e.g., Sensor keyboard, Sensor leftShiftDown, Sensor > mouseButtons) will work exactly as before. The usage of these funtions > is discouraged. > > I am installing Magma on a Pharo core image and Magma uses EventSensor, > by adding some methods to this class. As the class doesn't exist it > shows the following message: > > This package depends on the following classes: > Â EventSensor > You must resolve these dependencies before you will be able to load > these definitions: > Â EventSensor classSide>>maMaterializeFromGraph:using: > Â EventSensor>>maAsStorageObject > Â EventSensor>>maUsesStandardStorage > > > Select Proceed to continue, or close this window to cancel the > operation. > > If before loading Magma I do > > Smalltalk at: #EventSensor put: InputEventSensor. > > Then everything works without warnings. Also the InputEventSensor > receives the methods added by Magma. > > My questions are: > > Is this valid? > Must this (the InputEventSensor in the slot of EventSensor in Smalltalk) > be part of the image or will be a regresion to the situation before the > deletion of EventSensor? > What will be the correct way to handle this, change the Pharo/PharoCore > with my hack or to ask Chris Muller, the maintainer of Magma to not use > EventSensor but InputEvenSensor in the case of Pharo/PharoCore? > > Can I be reminded of the reasons to drop EventSensor in favor of > InputEvenSensor? > > Thanks for the answers > -- > 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

Jan. 13, 2010