November 2013 - Pharo-dev - lists.pharo.org

Smalltalks 2013 video now available

by Andres Valloud

Check out the playlist here: http://www.youtube.com/playlist?list=PLCGAAdUizzH027lLWKXh_44cGuEsay7-R Make sure you don't miss Smalltalks 2014! Andres.

Nov. 20, 2013

Re: [Pharo-dev] Convert to Athens

by J.F. Rick

Right. Where is this Athens repository? I have the latest in Pharo30/main (Athens-Morphic-MarcusDenker.23.mcz) and that does not seem to include AthensWrapperMorph. Cheers, Jeff On Wed, Nov 20, 2013 at 8:35 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > On 19 November 2013 17:42, J.F. Rick <self(a)je77.com> wrote: > >> Indeed. I would like to know that. It doesn't seem to be included in the >> latest Pharo 3.0. >> >> > it could be not yet included. > in that case, load most recent Athens-Morphic package from athens > repository. > > > >> Cheers, >> >> Jeff >> >> >> On Fri, Nov 15, 2013 at 7:34 PM, Hilaire Fernandes < >> hilaire.fernandes(a)gmail.com> wrote: >> >>> Le 15/11/2013 14:17, Igor Stasenko a Ã©crit : >>> > >>> > for transition , i implemented a special morph, AthensWrapMorph >>> > which wraps (as its name says) its children morphs and forces them to >>> be >>> > rendered by athens >>> > (the child morphs will never receive #drawOn: but #drawOnAthensCanvas: >>> > instead ). >>> >>> >>> I guess Jeff, may want to know where to find this wrapper. >>> >>> Hilaire >>> >>> >>> -- >>> Dr. Geo http://drgeo.eu >>> >>> >>> >> >> >> -- >> Jochen "Jeff" Rick, Ph.D. >> http://www.je77.com/ >> Skype ID: jochenrick >> > > > > -- > Best regards, > Igor Stasenko. > -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

Nov. 20, 2013

Re: [Pharo-dev] MetaRepoForPharo30 write permissions

by Pavel Krivanek

Hi Torsten, thank you very much. Of course I tried it before. I'm not a member of the Smalltalkhub Pharo team so this is the reason why I have to act as explicit contributor. Cheers -- Pavel 2013/11/20 Torsten Bergmann <astares(a)gmx.de> > Done, but I think it should have worked even > without adding you as a contributor. > > > Gesendet: Dienstag, 19. November 2013 um 21:48 Uhr > Von: "Pavel Krivanek" <pavel.krivanek(a)gmail.com> > An: "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org> > Betreff: [Pharo-dev] MetaRepoForPharo30 write permissions > > Hi, > > can someone add me to the MetaRepoForPharo30 repository? My username is > PavelKrivanek. > > Cheers, > -- Pavel > >

Nov. 20, 2013

Re: [Pharo-dev] MetaRepoForPharo30 write permissions

by Torsten Bergmann

Done, but I think it should have workedÂ even without adding you as a contributor. Â Gesendet:Â Dienstag, 19. November 2013 um 21:48 Uhr Von:Â "Pavel Krivanek" <pavel.krivanek(a)gmail.com> An:Â "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org> Betreff:Â [Pharo-dev] MetaRepoForPharo30 write permissions Hi, Â can someone add me to theÂ MetaRepoForPharo30 repository? My username is PavelKrivanek. Â Cheers, -- Pavel

Nov. 20, 2013

Re: [Pharo-dev] Convert to Athens

by Igor Stasenko

On 19 November 2013 17:42, J.F. Rick <self(a)je77.com> wrote: > Indeed. I would like to know that. It doesn't seem to be included in the > latest Pharo 3.0. > > it could be not yet included. in that case, load most recent Athens-Morphic package from athens repository. > Cheers, > > Jeff > > > On Fri, Nov 15, 2013 at 7:34 PM, Hilaire Fernandes < > hilaire.fernandes(a)gmail.com> wrote: > >> Le 15/11/2013 14:17, Igor Stasenko a Ã©crit : >> > >> > for transition , i implemented a special morph, AthensWrapMorph >> > which wraps (as its name says) its children morphs and forces them to be >> > rendered by athens >> > (the child morphs will never receive #drawOn: but #drawOnAthensCanvas: >> > instead ). >> >> >> I guess Jeff, may want to know where to find this wrapper. >> >> Hilaire >> >> >> -- >> Dr. Geo http://drgeo.eu >> >> >> > > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick > -- Best regards, Igor Stasenko.

Nov. 20, 2013

Re: [Pharo-dev] [squeak-dev] Re: Xtreams in Pharo 3

by Levente Uzonyi

On Wed, 20 Nov 2013, Levente Uzonyi wrote: > On Tue, 19 Nov 2013, Nicolas Cellier wrote: > >> For the OpalCompiler support, I have simply added the compiler method in >> Xtreams-Parsing because it does not conflict with anything else, I have >> the feeling that this is bearable... >> I have also added a NotFoundError subclass of NotFound in Xtreams-support. >> It's not ideal. That also means that bleeding-edge will not load in Squeak >> 4.4 or older, and maybe not elder version of Pharo... > > You mean any version of Squeak, since there's no class named NotFound. I see you've added it. > >> Maybe I could have changed NotFoundError reference into NotFound? >> In the future, or if we really want a bleding edge in elder images, we may >> have to fork the Xtreams-support, but as long as we can, it's better to >> avoid it. > > You can postpone this for a few months, but I don't see why it would make > sense. Forking is bad, but if you want to support two diverging platforms, > then you'll have to do it sooner or later. Well, it's not worth to bother with it, because IIUC the Pharo folks will fork it anyway. Levente > > > Levente > >> >> >> 2013/11/19 Sven Van Caekenberghe <sven(a)stfx.eu> >> >> On 18 Nov 2013, at 22:33, Nicolas Cellier >> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >> > Ah, NotFoundError is also undeclared in Squeak, it is the >> VisualWorks class name. >> > It could go into Xtreams-Support... >> >> OK, are you going to check this in, or should I ? >> >> How are we going to deal with platform specific stuff (like the Opal >> compiler switch) ? >> >> Sven >> >> >> >> > >

Nov. 20, 2013

Re: [Pharo-dev] Xtreams in Pharo 3

by Levente Uzonyi

On Tue, 19 Nov 2013, Nicolas Cellier wrote: > For the OpalCompiler support, I have simply added the compiler method in Xtreams-Parsing because it does not conflict with anything else, I have > the feeling that this is bearable... > I have also added a NotFoundError subclass of NotFound in Xtreams-support. > It's not ideal. That also means that bleeding-edge will not load in Squeak 4.4 or older, and maybe not elder version of Pharo... You mean any version of Squeak, since there's no class named NotFound. > Maybe I could have changed NotFoundError reference into NotFound? > In the future, or if we really want a bleding edge in elder images, we may have to fork the Xtreams-support, but as long as we can, it's better to > avoid it. You can postpone this for a few months, but I don't see why it would make sense. Forking is bad, but if you want to support two diverging platforms, then you'll have to do it sooner or later. Levente > > > 2013/11/19 Sven Van Caekenberghe <sven(a)stfx.eu> > > On 18 Nov 2013, at 22:33, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > Ah, NotFoundError is also undeclared in Squeak, it is the VisualWorks class name. > > It could go into Xtreams-Support... > > OK, are you going to check this in, or should I ? > > How are we going to deal with platform specific stuff (like the Opal compiler switch) ? > > Sven > > > >

Nov. 20, 2013

Re: [Pharo-dev] [squeak-dev] Re: Xtreams in Pharo 3

by Chris Muller

Unfortunate that KeyNotFound is not more generic (e.g., NotFound). On Tue, Nov 19, 2013 at 4:50 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > For the OpalCompiler support, I have simply added the compiler method in > Xtreams-Parsing because it does not conflict with anything else, I have the > feeling that this is bearable... > I have also added a NotFoundError subclass of NotFound in Xtreams-support. > It's not ideal. That also means that bleeding-edge will not load in Squeak > 4.4 or older, and maybe not elder version of Pharo... > Maybe I could have changed NotFoundError reference into NotFound? > In the future, or if we really want a bleding edge in elder images, we may > have to fork the Xtreams-support, but as long as we can, it's better to > avoid it. > > > 2013/11/19 Sven Van Caekenberghe <sven(a)stfx.eu> >> >> >> On 18 Nov 2013, at 22:33, Nicolas Cellier >> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >> > Ah, NotFoundError is also undeclared in Squeak, it is the VisualWorks >> > class name. >> > It could go into Xtreams-Support... >> >> OK, are you going to check this in, or should I ? >> >> How are we going to deal with platform specific stuff (like the Opal >> compiler switch) ? >> >> Sven > > > > >

Nov. 20, 2013

Re: [Pharo-dev] Xtreams in Pharo 3

by Nicolas Cellier

For the OpalCompiler support, I have simply added the compiler method in Xtreams-Parsing because it does not conflict with anything else, I have the feeling that this is bearable... I have also added a NotFoundError subclass of NotFound in Xtreams-support. It's not ideal. That also means that bleeding-edge will not load in Squeak 4.4 or older, and maybe not elder version of Pharo... Maybe I could have changed NotFoundError reference into NotFound? In the future, or if we really want a bleding edge in elder images, we may have to fork the Xtreams-support, but as long as we can, it's better to avoid it. 2013/11/19 Sven Van Caekenberghe <sven(a)stfx.eu> > > On 18 Nov 2013, at 22:33, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > Ah, NotFoundError is also undeclared in Squeak, it is the VisualWorks > class name. > > It could go into Xtreams-Support... > > OK, are you going to check this in, or should I ? > > How are we going to deal with platform specific stuff (like the Opal > compiler switch) ? > > Sven >

Nov. 19, 2013

Re: [Pharo-dev] CodePharo

by phil＠highoctane.be

I had a look. We can seal a lot of ideas quite fast. And it is a good opportunity to do a sample Seaside app with a modern look. Phil

Nov. 19, 2013