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

Re: [Pharo-dev] Old ClassBuilder remove!

by Tudor Girba

Hi, This is not *just cleaning*! You might perceive it as such being so involved in it. You guys replaced something ugly with something based on a sound explicit model. When you do this at such a core level, the possibilities explode two layers on top. You might just do not see it, yet :). Just two examples: - Morphic uses a dictionary to allow extensions to add attributes to the base class. This is closed-world-based-assumption thinking because I have to know in advance what parts will be extended by someone else. This should be easily changeable with slots given that slots are manipulate-able at runtime (ideally). - In Fame we implement bidirectional relationships. By bidirectional relationships I mean you have classes like A ->* B, and when you have a B object and set the A parent, it automatically adds the B instance to the collection in A. The current implementation in Fame is difficult to grasp and the code of specifying the slots is spread over the whole Moose models. Once slots are supported as first class, we can build the strategy of bidirectionality directly in the slot support. This will be more elegant. Doru On Thu, Nov 21, 2013 at 2:24 PM, Camille Teruel <camille.teruel(a)gmail.com>wrote: > > On 21 nov. 2013, at 13:44, kilon alios <kilon.alios(a)gmail.com> wrote: > > any links why newcomers like me should be impressed ? Whats the advantages > ? > > > That's just cleaning. The old class builder was an incredibly complex > piece of code that is now replaced with the Slot class builder. > The later is based on slots and is much more understandable and thus much > easier to maintain. > It's been integrated some time ago thanks to Martin. > > Slots are the work of Toon and Camillo and enables a lot of useful > features: > > http://rmod.lille.inria.fr/archives/papers/Verw11a-OOSPLA11-FlexibleObjectL… > They are based on the reification of class layouts (variable,weak,fixed > and co) and instance variables (slots). > Slots are an abstraction added on top of low-level class "fields". > It means that one will be able to create a customized slot class that > define the logic to read and write a slot: > > Object subclass: #MyClass > slots: { x => MyFancySlot } > category: 'Playground' > > Then when a method read or writes x, the logic you defined in MyFancySlot > is executed. > All that still need to be absorbed by Opal so it's not available right now > but it will (Pharo 4)! > > > > > > On Thu, Nov 21, 2013 at 2:21 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Triple impressive! This is another sample of an apparently tiny change >> that actually has deep impact on the future of our beloved environment. >> >> Ladies and gentlemen, I know you are busy, but please take the time to >> acknowledge it :) >> >> Doru >> >> >> >> >> On Thu, Nov 21, 2013 at 12:58 PM, Martin Dias <tinchodias(a)gmail.com>wrote: >> >>> wow, impressive! >>> >>> >>> On Thu, Nov 21, 2013 at 9:02 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: >>> >>>> Hi, >>>> >>>> Yesterday Camille did the change to finally remove the old class >>>> builder! >>>> (just a removal + a small change to NativeBoost to use the new class >>>> builder to create anonymous classes). >>>> >>>> This means >>>> - 1000 Loc of completely un-understandable code removed. >>>> - we now 100% run on the new class builder from the Slot >>>> Project. >>>> >>>> Next on the list (not all for Pharo3): >>>> >>>> - remove PackageInfo >>>> - old Browser + CodeHolder hierarchy >>>> - PseudoClass&Co â> Ring >>>> - old AST+Compiler (this in Pharo4) >>>> >>>> We already did (all in Pharo3): >>>> -> remove URI >>>> -> deprecated Url for ZnUrl >>>> -> removed HTTPSocket facade >>>> -> MIMEType retired for ZnMimeType >>>> -> old Debugger is removed >>>> -> Class categories are replaced by Protocols >>>> >>>> I am quite sure that these cleanups will enable us to build a lot of >>>> very interesting things >>>> in the future. >>>> >>>> Marcus >>>> >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 21, 2013

Re: [Pharo-dev] Old ClassBuilder remove!

by Luc Fabresse

yes thanks a lot! I like cleaning. #Luc 2013/11/21 Camille Teruel <camille.teruel(a)gmail.com> > > On 21 nov. 2013, at 13:44, kilon alios <kilon.alios(a)gmail.com> wrote: > > any links why newcomers like me should be impressed ? Whats the advantages > ? > > > That's just cleaning. The old class builder was an incredibly complex > piece of code that is now replaced with the Slot class builder. > The later is based on slots and is much more understandable and thus much > easier to maintain. > It's been integrated some time ago thanks to Martin. > > Slots are the work of Toon and Camillo and enables a lot of useful > features: > > http://rmod.lille.inria.fr/archives/papers/Verw11a-OOSPLA11-FlexibleObjectL… > They are based on the reification of class layouts (variable,weak,fixed > and co) and instance variables (slots). > Slots are an abstraction added on top of low-level class "fields". > It means that one will be able to create a customized slot class that > define the logic to read and write a slot: > > Object subclass: #MyClass > slots: { x => MyFancySlot } > category: 'Playground' > > Then when a method read or writes x, the logic you defined in MyFancySlot > is executed. > All that still need to be absorbed by Opal so it's not available right now > but it will (Pharo 4)! > > > > > > On Thu, Nov 21, 2013 at 2:21 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Triple impressive! This is another sample of an apparently tiny change >> that actually has deep impact on the future of our beloved environment. >> >> Ladies and gentlemen, I know you are busy, but please take the time to >> acknowledge it :) >> >> Doru >> >> >> >> >> On Thu, Nov 21, 2013 at 12:58 PM, Martin Dias <tinchodias(a)gmail.com>wrote: >> >>> wow, impressive! >>> >>> >>> On Thu, Nov 21, 2013 at 9:02 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: >>> >>>> Hi, >>>> >>>> Yesterday Camille did the change to finally remove the old class >>>> builder! >>>> (just a removal + a small change to NativeBoost to use the new class >>>> builder to create anonymous classes). >>>> >>>> This means >>>> - 1000 Loc of completely un-understandable code removed. >>>> - we now 100% run on the new class builder from the Slot >>>> Project. >>>> >>>> Next on the list (not all for Pharo3): >>>> >>>> - remove PackageInfo >>>> - old Browser + CodeHolder hierarchy >>>> - PseudoClass&Co â> Ring >>>> - old AST+Compiler (this in Pharo4) >>>> >>>> We already did (all in Pharo3): >>>> -> remove URI >>>> -> deprecated Url for ZnUrl >>>> -> removed HTTPSocket facade >>>> -> MIMEType retired for ZnMimeType >>>> -> old Debugger is removed >>>> -> Class categories are replaced by Protocols >>>> >>>> I am quite sure that these cleanups will enable us to build a lot of >>>> very interesting things >>>> in the future. >>>> >>>> Marcus >>>> >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > >

Nov. 21, 2013

Re: [Pharo-dev] Old ClassBuilder remove!

by phil＠highoctane.be

facking awesome ! On Thursday, November 21, 2013, Camille Teruel wrote: > > On 21 nov. 2013, at 13:44, kilon alios <kilon.alios(a)gmail.com<javascript:_e({}, 'cvml', 'kilon.alios(a)gmail.com');>> > wrote: > A > > any links why newcomers like me should be impressed ? Whats the advantages > ? > > > That's just cleaning. The old class builder was an incredibly complex > piece of code that is now replaced with the Slot class builder. > The later is based on slots and is much more understandable and thus much > easier to maintain. > It's been integrated some time ago thanks to Martin. > > Slots are the work of Toon and Camillo and enables a lot of useful > features: > > http://rmod.lille.inria.fr/archives/papers/Verw11a-OOSPLA11-FlexibleObjectL… > They are based on the reification of class layouts (variable,weak,fixed > and co) and instance variables (slots). > Slots are an abstraction added on top of low-level class "fields". > It means that one will be able to create a customized slot class that > define the logic to read and write a slot: > > Object subclass: #MyClass > slots: { x => MyFancySlot } > category: 'Playground' > > Then when a method read or writes x, the logic you defined in MyFancySlot > is executed. > All that still need to be absorbed by Opal so it's not available right now > but it will (Pharo 4)! > > > > > > On Thu, Nov 21, 2013 at 2:21 PM, Tudor Girba <tudor(a)tudorgirba.com<javascript:_e({}, 'cvml', 'tudor(a)tudorgirba.com');> > > wrote: > >> Triple impressive! This is another sample of an apparently tiny change >> that actually has deep impact on the future of our beloved environment. >> >> Ladies and gentlemen, I know you are busy, but please take the time to >> acknowledge it :) >> >> Doru >> >> >> >> >> On Thu, Nov 21, 2013 at 12:58 PM, Martin Dias <tinchodias(a)gmail.com<javascript:_e({}, 'cvml', 'tinchodias(a)gmail.com');> >> > wrote: >> >>> wow, impressive! >>> >>> >>> On Thu, Nov 21, 2013 at 9:02 AM, Marcus Denker <marcus.denker(a)inria.fr<javascript:_e({}, 'cvml', 'marcus.denker(a)inria.fr');> >>> > wrote: >>> >>>> Hi, >>>> >>>> Yesterday Camille did the change to finally remove the old class >>>> builder! >>>> (just a removal + a small change to NativeBoost to use the new class >>>> builder to create anonymous classes). >>>> >>>> This means >>>> - 1000 Loc of completely un-understandable code removed. >>>> - we now 100% run on the new class builder from the Slot >>>> Project. >>>> >>>> Next on the list (not all for Pharo3): >>>> >>>> - remove PackageInfo >>>> - old Browser + CodeHolder hierarchy >>>> - PseudoClass&Co â> Ring >>>> - old AST+Compiler (this in Pharo4) >>>> >>>> We already did (all in Pharo3): >>>> -> remove URI >>>> -> deprecated Url for ZnUrl >>>> -> removed HTTPSocket facade >>>> -> MIMEType retired for ZnMimeType >>>> -> old Debugger is removed >>>> -> Class categories are replaced by Protocols >>>> >>>> I am quite sure that these cleanups will enable us to build a lot of >>>> very interesting things >>>> in the future. >>>> >>>> Marcus >>>> >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > > -- --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:phil@highoctane.be | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium Pharo Consortium Member - http://consortium.pharo.org/ Featured on the Software Process and Measurement Cast - http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller

Nov. 21, 2013

Re: [Pharo-dev] Old ClassBuilder remove!

by Camille Teruel

On 21 nov. 2013, at 13:44, kilon alios <kilon.alios(a)gmail.com> wrote: > any links why newcomers like me should be impressed ? Whats the advantages ? That's just cleaning. The old class builder was an incredibly complex piece of code that is now replaced with the Slot class builder. The later is based on slots and is much more understandable and thus much easier to maintain. It's been integrated some time ago thanks to Martin. Slots are the work of Toon and Camillo and enables a lot of useful features: http://rmod.lille.inria.fr/archives/papers/Verw11a-OOSPLA11-FlexibleObjectL… They are based on the reification of class layouts (variable,weak,fixed and co) and instance variables (slots). Slots are an abstraction added on top of low-level class "fields". It means that one will be able to create a customized slot class that define the logic to read and write a slot: Object subclass: #MyClass slots: { x => MyFancySlot } category: 'Playground' Then when a method read or writes x, the logic you defined in MyFancySlot is executed. All that still need to be absorbed by Opal so it's not available right now but it will (Pharo 4)! > > > > On Thu, Nov 21, 2013 at 2:21 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Triple impressive! This is another sample of an apparently tiny change that actually has deep impact on the future of our beloved environment. > > Ladies and gentlemen, I know you are busy, but please take the time to acknowledge it :) > > Doru > > > > > On Thu, Nov 21, 2013 at 12:58 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > wow, impressive! > > > On Thu, Nov 21, 2013 at 9:02 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > Yesterday Camille did the change to finally remove the old class builder! > (just a removal + a small change to NativeBoost to use the new class builder to create anonymous classes). > > This means > - 1000 Loc of completely un-understandable code removed. > - we now 100% run on the new class builder from the Slot Project. > > Next on the list (not all for Pharo3): > > - remove PackageInfo > - old Browser + CodeHolder hierarchy > - PseudoClass&Co â> Ring > - old AST+Compiler (this in Pharo4) > > We already did (all in Pharo3): > -> remove URI > -> deprecated Url for ZnUrl > -> removed HTTPSocket facade > -> MIMEType retired for ZnMimeType > -> old Debugger is removed > -> Class categories are replaced by Protocols > > I am quite sure that these cleanups will enable us to build a lot of very interesting things > in the future. > > Marcus > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Nov. 21, 2013

Re: [Pharo-dev] Spotlight behaviour

by Tudor Girba

Hi Esteban, This is great! Not the way it looks, but that you are working on all those little details that make theme-ing close to impossible. Do you need help? Cheers, Doru On Wed, Nov 20, 2013 at 2:42 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > :) > > > I'm slowly working in a darktheme... problem is the INCREDIBLE amount of > hardcode colors and silly code. > So it will take some time until is ready (also because I work on it when > I'm bored and not wanting to do what I should do... like today :P) > > Esteban > > > On Nov 20, 2013, at 2:34 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > > yes I can confirm that this work also on windoom 7. Indeed Sven your Pharo > looks a bit more sexy than mine. > > the code you posted works also like a charm for me , thank you. Now If I > could get also a dark theme working with pharo that would be awesome. All > this white hurts my eyes. But I guess I will have to compromise for the > time being :) > > thank you > > > On Wed, Nov 20, 2013 at 2:58 PM, Sven Van Caekenberghe <sven(a)stfx.eu>wrote: > >> >> On 20 Nov 2013, at 13:46, Esteban A. Maringolo <emaringolo(a)gmail.com> >> wrote: >> >> > Sven. >> > >> > What version are YOU using? Fonts and windows look so clean an sharp! :) >> >> ;-) >> >> Yes they are. >> >> Like I said, Pharo version #30582 >> >> defaultFont Source Sans Pro Normal points: 12 height: 21 >> listFont Source Sans Pro Normal points: 12 height: 21 >> menuFont Source Sans Pro Normal points: 12 height: 21 >> windowTitleFont Source Sans Pro Bold points: 12 height: 21 >> balloonFont Source Sans Pro Normal points: 9 height: 16 >> codeFont Source Code Pro Normal points: 11 height: 19 >> buttonFont Source Sans Pro Normal points: 12 height: 21 >> haloFont Source Sans Pro Normal points: 9 height: 16 >> >> Installed with a script from our local look and feel guru, Doru: >> >> #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' >> 'SourceSansProBoldâ) >> do: [ :each | >> Smalltalk globals >> at: each asSymbol >> ifAbsent: [ >> Gofer new >> smalltalkhubUser: 'girba' project: 'FreeFonts'; >> package: each; >> load ]. >> (Smalltalk at: each asSymbol) new install ]. >> FreeTypeSystemSettings loadFt2Library: true. >> FreeTypeFontProvider current updateFromSystem. >> >> StandardFonts >> setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' >> pointSize: 12); >> haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 9); >> windowTitleFont: (LogicalFont familyName: 'Source Sans Pro Bold' >> pointSize: 12); >> balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 9); >> codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 11). >> >> And then I finally make the window font bold, manually. >> >> The screenshot was done on Mac OS X 10.9 >> >> HTH, >> >> Sven >> >> > Esteban A. Maringolo >> > >> > >> > 2013/11/20 Sven Van Caekenberghe <sven(a)stfx.eu> >> > What version are you using ? >> > >> > In #30582 it does work: >> > <Screen Shot 2013-11-20 at 13.34.46.png> >> > >> > You can always try typing a space after Objectâ¦ >> > >> > Sven >> > >> > On 20 Nov 2013, at 13:23, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> > >> >> HI, >> >> >> >> do you know why search behaves like this? I was expecting Object to >> show up >> >> >> >> <Screenshot 2013-11-20 13.20.40.png> >> >> >> >> >> >> Cheers >> >> Uko >> > >> > >> >> >> > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 21, 2013

Re: [Pharo-dev] Loading Xtreams in Pharo

by David T. Lewis

On Thu, Nov 21, 2013 at 12:29:36PM +0100, Torsten Bergmann wrote: > > https://ci.inria.fr/pharo-contribution/job/Xtreams/ > > > > still a little rough, but it is a start. > > If possible I would like to see the project itself moved over from SqS to STHub. > > Not as a "Pharo" fork but as a replacement for the Squeaksource repo. > Sorry but I was too often bitten by SqS problems... For information: The squeaksource.com service is now hosted on a different server, and is maintained by the Squeak community. The previous reliability and performance problems have been resolved. I don't want to discourage anyone from moving to other repositories, but you should not feel like you have to do it on account of the previous reliability issues. FYI only, Dave

Nov. 21, 2013

Re: [Pharo-dev] Loading Xtreams in Pharo

by Frank Shearar

On 21 November 2013 11:29, Torsten Bergmann <astares(a)gmx.de> wrote: >> https://ci.inria.fr/pharo-contribution/job/Xtreams/ >> >> still a little rough, but it is a start. > > If possible I would like to see the project itself moved over from SqS to STHub. > > Not as a "Pharo" fork but as a replacement for the Squeaksource repo. > Sorry but I was too often bitten by SqS problems... Fair enough, and "once bitten twice shy", but please give SqS a chance: it's on a new box, running an updated image, and admins are actually watching out for the box. If you see any kinds of problems, I'm sure Chris Muller will want to hear about them. frank > Thx > T. > >

Nov. 21, 2013

Re: [Pharo-dev] Old ClassBuilder remove!

by Norbert Hartl

Am 21.11.2013 um 13:21 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > Ladies and gentlemen, I know you are busy, but please take the time to acknowledge it :) full ack Norbert

Nov. 21, 2013

Re: [Pharo-dev] Old ClassBuilder remove!

by kilon alios

any links why newcomers like me should be impressed ? Whats the advantages ? On Thu, Nov 21, 2013 at 2:21 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Triple impressive! This is another sample of an apparently tiny change > that actually has deep impact on the future of our beloved environment. > > Ladies and gentlemen, I know you are busy, but please take the time to > acknowledge it :) > > Doru > > > > > On Thu, Nov 21, 2013 at 12:58 PM, Martin Dias <tinchodias(a)gmail.com>wrote: > >> wow, impressive! >> >> >> On Thu, Nov 21, 2013 at 9:02 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: >> >>> Hi, >>> >>> Yesterday Camille did the change to finally remove the old class builder! >>> (just a removal + a small change to NativeBoost to use the new class >>> builder to create anonymous classes). >>> >>> This means >>> - 1000 Loc of completely un-understandable code removed. >>> - we now 100% run on the new class builder from the Slot >>> Project. >>> >>> Next on the list (not all for Pharo3): >>> >>> - remove PackageInfo >>> - old Browser + CodeHolder hierarchy >>> - PseudoClass&Co â> Ring >>> - old AST+Compiler (this in Pharo4) >>> >>> We already did (all in Pharo3): >>> -> remove URI >>> -> deprecated Url for ZnUrl >>> -> removed HTTPSocket facade >>> -> MIMEType retired for ZnMimeType >>> -> old Debugger is removed >>> -> Class categories are replaced by Protocols >>> >>> I am quite sure that these cleanups will enable us to build a lot of >>> very interesting things >>> in the future. >>> >>> Marcus >>> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Nov. 21, 2013

Re: [Pharo-dev] Old ClassBuilder remove!

by Tudor Girba

Triple impressive! This is another sample of an apparently tiny change that actually has deep impact on the future of our beloved environment. Ladies and gentlemen, I know you are busy, but please take the time to acknowledge it :) Doru On Thu, Nov 21, 2013 at 12:58 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > wow, impressive! > > > On Thu, Nov 21, 2013 at 9:02 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > >> Hi, >> >> Yesterday Camille did the change to finally remove the old class builder! >> (just a removal + a small change to NativeBoost to use the new class >> builder to create anonymous classes). >> >> This means >> - 1000 Loc of completely un-understandable code removed. >> - we now 100% run on the new class builder from the Slot Project. >> >> Next on the list (not all for Pharo3): >> >> - remove PackageInfo >> - old Browser + CodeHolder hierarchy >> - PseudoClass&Co â> Ring >> - old AST+Compiler (this in Pharo4) >> >> We already did (all in Pharo3): >> -> remove URI >> -> deprecated Url for ZnUrl >> -> removed HTTPSocket facade >> -> MIMEType retired for ZnMimeType >> -> old Debugger is removed >> -> Class categories are replaced by Protocols >> >> I am quite sure that these cleanups will enable us to build a lot of very >> interesting things >> in the future. >> >> Marcus >> > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 21, 2013