Re: [Pharo-dev] We did it! SlotClassBuilder is active
Congrats! That's really a huge step forward. Didn't expect that so soon! Norbert Am 03.07.2013 um 17:00 schrieb Marcus Denker : > Hi, > > Today we turned on the SlotClassBuilder… this means actually quite a huge > change, as it puts into place > lots of things that we can build on later. > > What it means for now > > -> A new, much easier to understand ClassBuilder > -> meta Objects. Layouts + Slots > > For example, there is now for every instance variable a meta object that > describes it > It will be very interesting to see what we can do with that! > > Thanks to Toon + Camillo for the original implementation, and Martin Dias > with Camillo > for the work to get in really into 3.0. > > Marcus
Re: [Pharo-dev] We did it! SlotClassBuilder is active
On 03 Jul 2013, at 17:00, Marcus Denker wrote: > Hi, > > Today we turned on the SlotClassBuilder… this means actually quite a huge > change, as it puts into place > lots of things that we can build on later. > > What it means for now > > -> A new, much easier to understand ClassBuilder > -> meta Objects. Layouts + Slots > > For example, there is now for every instance variable a meta object that > describes it > It will be very interesting to see what we can do with that! > > Thanks to Toon + Camillo for the original implementation, and Martin Dias > with Camillo > for the work to get in really into 3.0. > > Marcus Progress, progress ! Now we need some nice blog posts explaining all this to mere mortals, like me. Sven
Re: [Pharo-dev] We did it! SlotClassBuilder is active
Yes thanks to all to keep pushing this kind of really cool new features! Luc 2013/7/3 Sven Van Caekenberghe > > On 03 Jul 2013, at 17:00, Marcus Denker wrote: > > > Hi, > > > > Today we turned on the SlotClassBuilder… this means actually quite a > huge change, as it puts into place > > lots of things that we can build on later. > > > > What it means for now > > > > -> A new, much easier to understand ClassBuilder > > -> meta Objects. Layouts + Slots > > > > For example, there is now for every instance variable a meta object that > describes it > > It will be very interesting to see what we can do with that! > > > > Thanks to Toon + Camillo for the original implementation, and Martin > Dias with Camillo > > for the work to get in really into 3.0. > > > > Marcus > > Progress, progress ! > > Now we need some nice blog posts explaining all this to mere mortals, like > me. > > Sven > > >
Re: [Pharo-dev] We did it! SlotClassBuilder is active
Yeee! 2013/7/3 Luc Fabresse > > Yes thanks to all to keep pushing this kind of really cool new features! > > Luc > > > 2013/7/3 Sven Van Caekenberghe > >> >> On 03 Jul 2013, at 17:00, Marcus Denker wrote: >> >> > Hi, >> > >> > Today we turned on the SlotClassBuilder… this means actually quite a >> huge change, as it puts into place >> > lots of things that we can build on later. >> > >> > What it means for now >> > >> > -> A new, much easier to understand ClassBuilder >> > -> meta Objects. Layouts + Slots >> > >> > For example, there is now for every instance variable a meta object >> that describes it >> > It will be very interesting to see what we can do with that! >> > >> > Thanks to Toon + Camillo for the original implementation, and Martin >> Dias with Camillo >> > for the work to get in really into 3.0. >> > >> > Marcus >> >> Progress, progress ! >> >> Now we need some nice blog posts explaining all this to mere mortals, >> like me. >> >> Sven >> >> >> >
Re: [Pharo-dev] We did it! SlotClassBuilder is active
I'm impressed and pleased! Thanks Camillo and Martin for your attitude. Really. It opens a new range of possibilities with first class instance variables. Now with Opal + slots we will be able to implement cool features. Stef > Hi, > > Today we turned on the SlotClassBuilder… this means actually quite a huge > change, as it puts into place > lots of things that we can build on later. > > What it means for now > > -> A new, much easier to understand ClassBuilder > -> meta Objects. Layouts + Slots > > For example, there is now for every instance variable a meta object that > describes it > It will be very interesting to see what we can do with that! > > Thanks to Toon + Camillo for the original implementation, and Martin Dias > with Camillo > for the work to get in really into 3.0. > > Marcus
Re: [Pharo-dev] We did it! SlotClassBuilder is active
Thanks Martin for polishing everything :) On 2013-07-03, at 21:47, Stéphane Ducasse wrote: > I'm impressed and pleased! > Thanks Camillo and Martin for your attitude. > Really. > It opens a new range of possibilities with first class instance variables. > Now with Opal + slots we will be able to implement cool features. > > Stef > >> Hi, >> >> Today we turned on the SlotClassBuilder… this means actually quite a huge >> change, as it puts into place >> lots of things that we can build on later. >> >> What it means for now >> >> -> A new, much easier to understand ClassBuilder >> -> meta Objects. Layouts + Slots >> >> For example, there is now for every instance variable a meta object that >> describes it >> It will be very interesting to see what we can do with that! >> >> Thanks to Toon + Camillo for the original implementation, and Martin Dias >> with Camillo >> for the work to get in really into 3.0. >> >> Marcus > >
Re: [Pharo-dev] We did it! SlotClassBuilder is active
2013/7/3 Sven Van Caekenberghe : > On 03 Jul 2013, at 17:00, Marcus Denker wrote: >> Today we turned on the SlotClassBuilder… this means actually quite a huge >> change, as it puts into place >> lots of things that we can build on later. > Now we need some nice blog posts explaining all this to mere mortals, like me. +1 Another mere mortal here that wants to know how and why this is a big leap in the Pharo history.
Re: [Pharo-dev] We did it! SlotClassBuilder is active
Wow! I cannot wait to clunky dictionary-based instance variable extensions with slots. Doru On Wed, Jul 3, 2013 at 5:00 PM, Marcus Denker wrote: > Hi, > > Today we turned on the SlotClassBuilder… this means actually quite a huge > change, as it puts into place > lots of things that we can build on later. > > What it means for now > > -> A new, much easier to understand ClassBuilder > -> meta Objects. Layouts + Slots > > For example, there is now for every instance variable a meta object that > describes it > It will be very interesting to see what we can do with that! > > Thanks to Toon + Camillo for the original implementation, and Martin Dias > with Camillo > for the work to get in really into 3.0. > > Marcus > -- www.tudorgirba.com "Every thing has its own flow"
Re: [Pharo-dev] We did it! SlotClassBuilder is active
Hehe, yes, and finally I can have more than 254 instance variables! Norbert Am 03.07.2013 um 23:38 schrieb Tudor Girba : > Wow! > > I cannot wait to clunky dictionary-based instance variable extensions with > slots. > > Doru > > > On Wed, Jul 3, 2013 at 5:00 PM, Marcus Denker wrote: > Hi, > > Today we turned on the SlotClassBuilder… this means actually quite a huge > change, as it puts into place > lots of things that we can build on later. > > What it means for now > > -> A new, much easier to understand ClassBuilder > -> meta Objects. Layouts + Slots > > For example, there is now for every instance variable a meta object that > describes it > It will be very interesting to see what we can do with that! > > Thanks to Toon + Camillo for the original implementation, and Martin Dias > with Camillo > for the work to get in really into 3.0. > > Marcus > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"
Re: [Pharo-dev] We did it! SlotClassBuilder is active
On Jul 3, 2013, at 11:38 PM, Tudor Girba wrote: > Wow! > > I cannot wait to clunky dictionary-based instance variable extensions with > slots. Me too :) Imagine no more MorphExtension :) Stef
Re: [Pharo-dev] We did it! SlotClassBuilder is active
On Jul 4, 2013, at 10:47 AM, Stéphane Ducasse wrote: > > On Jul 3, 2013, at 11:38 PM, Tudor Girba wrote: > >> Wow! >> >> I cannot wait to clunky dictionary-based instance variable extensions with >> slots. > > Me too :) > Imagine no more MorphExtension :) > Indeed. And all the flags of morphic (sticky, locked…) would be stored in one SmallInteger. Marcus
Re: [Pharo-dev] We did it! SlotClassBuilder is active
Great! Time to simplify Magritte. Stephan
Re: [Pharo-dev] We did it! SlotClassBuilder is active
I forgot about this side-effect. PetitParser will be so happy. Doru On Thu, Jul 4, 2013 at 9:51 AM, Norbert Hartl wrote: > Hehe, yes, and finally I can have more than 254 instance variables! > > Norbert > > Am 03.07.2013 um 23:38 schrieb Tudor Girba : > > Wow! > > I cannot wait to clunky dictionary-based instance variable extensions with > slots. > > Doru > > > On Wed, Jul 3, 2013 at 5:00 PM, Marcus Denker wrote: > >> Hi, >> >> Today we turned on the SlotClassBuilder… this means actually quite a huge >> change, as it puts into place >> lots of things that we can build on later. >> >> What it means for now >> >> -> A new, much easier to understand ClassBuilder >> -> meta Objects. Layouts + Slots >> >> For example, there is now for every instance variable a meta object that >> describes it >> It will be very interesting to see what we can do with that! >> >> Thanks to Toon + Camillo for the original implementation, and Martin Dias >> with Camillo >> for the work to get in really into 3.0. >> >> Marcus >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"
Re: [Pharo-dev] We did it! SlotClassBuilder is active
And Moose :) Doru On Thu, Jul 4, 2013 at 10:56 AM, Stephan Eggermont wrote: > Great! > Time to simplify Magritte. > > Stephan > > -- www.tudorgirba.com "Every thing has its own flow"
Re: [Pharo-dev] We did it! SlotClassBuilder is active
> Thanks Martin for polishing everything :) It's ok! It was a lot of fun. Thanks also to Guille Polito, who helped writing tests during GSoC-2012. +1 for the blog post. I don't have too much to say of the plans for the future but I could write about the current state of the project. Martín
Re: [Pharo-dev] We did it! SlotClassBuilder is active
On Thu, Jul 4, 2013 at 11:17 AM, Martin Dias wrote: > +1 for the blog post. I don't have too much to say of the plans for > the future but I could write about the current state of the project. yes please, current state description is already great. You may want to write it in Pier format so that we get a nice chapter. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
Re: [Pharo-dev] We did it! SlotClassBuilder is active
Congrats!! This opens more doors to me since i we can have stateful traits now :) 2013/7/4 Damien Cassou > On Thu, Jul 4, 2013 at 11:17 AM, Martin Dias wrote: > > +1 for the blog post. I don't have too much to say of the plans for > > the future but I could write about the current state of the project. > > > yes please, current state description is already great. You may want > to write it in Pier format so that we get a nice chapter. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >
Re: [Pharo-dev] We did it! SlotClassBuilder is active
On 4 July 2013 13:15, Sebastian Tleye wrote: > Congrats!! > This opens more doors to me since i we can have stateful traits now :) Do you mean it makes implementing stateful traits _much easier_, or _possible at all_? I'd be curious to know why, if the latter. Having first class slots means being able to implement triggers (and hence data flow type stuff), so I can see why it'd make it easier. frank > 2013/7/4 Damien Cassou >> >> On Thu, Jul 4, 2013 at 11:17 AM, Martin Dias wrote: >> > +1 for the blog post. I don't have too much to say of the plans for >> > the future but I could write about the current state of the project. >> >> >> yes please, current state description is already great. You may want >> to write it in Pier format so that we get a nice chapter. >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill
Re: [Pharo-dev] We did it! SlotClassBuilder is active
On 2013-07-04, at 14:29, Frank Shearar wrote: > On 4 July 2013 13:15, Sebastian Tleye wrote: >> Congrats!! >> This opens more doors to me since i we can have stateful traits now :) > > Do you mean it makes implementing stateful traits _much easier_, or > _possible at all_? I'd be curious to know why, if the latter. > > Having first class slots means being able to implement triggers (and > hence data flow type stuff), so I can see why it'd make it easier. Stateful traits already have been successfully implemented using slots + first class layouts, you can have a look at the implementation in the slot paper: http://rmod.lille.inria.fr/archives/papers/Verw11a-OOSPLA11-FlexibleObjectLayouts.pdf
Re: [Pharo-dev] We did it! SlotClassBuilder is active
2013/7/4 Sebastian Tleye > Congrats!! > This opens more doors to me since i we can have stateful traits now :) > Indeed! > > > 2013/7/4 Damien Cassou > >> On Thu, Jul 4, 2013 at 11:17 AM, Martin Dias >> wrote: >> > +1 for the blog post. I don't have too much to say of the plans for >> > the future but I could write about the current state of the project. >> >> >> yes please, current state description is already great. You may want >> to write it in Pier format so that we get a nice chapter. >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> >> >
