- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Tutorial] Rediscovering the UX of the legendary HP-35 Scientific Pocket Calculator

by Sven Van Caekenberghe

Apparently it already got posted on YC News https://news.ycombinator.com/item?id=7943876 so it needs votes and comments to survive. On 25 Jun 2014, at 15:29, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I have written a new, extensive, long form, introductory article about Pharo. > > Rediscovering the UX of the legendary HP-35 Scientific Pocket Calculator > > A tutorial on Pharo, test and specification based immersive programming > > https://medium.com/@svenvc/rediscovering-the-ux-of-the-legendary-hp-35-scie… >

June 25, 2014

Re: [Pharo-dev] [Pharo4] Slots: API for Classes

by Esteban A. Maringolo

2014-06-25 11:52 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > On 25 Jun 2014, at 11:49, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 25 Jun 2014, at 16:43, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> >>> Slot >>> \SimpleSlot (current iv slot) >> >> Yes, the naming of that oneâ¦ I think we just need to take the freedom of iterating. >> For now I called it âInstanceVariableSlotâ, but that might be confusing and it is a long word. > > but is less confusing than âSimpleSlotâ, which basically says nothing, IMO What about SimpleInstanceVariableSlot? (just kidding) I don't like over descriptive class names. Because they restrict you from using it for other, unexpected, purposes or contexts. Regards!

June 25, 2014

Re: [Pharo-dev] [Pharo4] Slots: API for Classes

by Esteban Lorenzano

On 25 Jun 2014, at 11:49, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 25 Jun 2014, at 16:43, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > >> Slot >> \SimpleSlot (current iv slot) > > Yes, the naming of that oneâ¦ I think we just need to take the freedom of iterating. > For now I called it âInstanceVariableSlotâ, but that might be confusing and it is a long word. but is less confusing than âSimpleSlotâ, which basically says nothing, IMO > >> \CollectionSlot >> \BitmapSlot >> Esteban A. Maringolo >> >> >> 2014-06-25 9:38 GMT-03:00 Norbert Hartl <norbert(a)hartl.name>: >>> >>> Am 25.06.2014 um 14:22 schrieb Marcus Denker <marcus.denker(a)inria.fr>: >>> >>>> >>>> On 25 Jun 2014, at 14:16, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> >>>>> Very nice! >>>>> >>>>> Next would be an example of how to specialize a slot :) >>>>> >>>> >>>> Yes, the next steps are: >>>> >>>> - introduce abstract superclass for Slot >>>> >>>> (I am not yet sure: will the be âSlotâ and the default slots are âInstVarSlotâ, or do I add a >>>> âAbstractSlotâ class and Slot stays the default? Maybe thatâs better) >>>> >>> I like the former better. But if you do can you please help stop that naming scheme? Could we name it InstanceVariableSlot then? Pleeeeaaaase? >>> >>> Norbert >>> >>>> - Opal needs to delegate code generation to the Slot. >>>> >>>> - The abstract slot generates by default reflective read/write access code >>>> >>>> - subclasses can override. (e.g. the default slot overrides to do pushIvar/storeIvar bytecode) >>>> >>>> This is the enough to do behavioural changes to simple Slots. >>>> >>>> After that we need to check the code for âvirtualâ slots where e.g. multiple Boolean slots are mapped to one >>>> hidden flag ivar. >>>> >>>> And the of course >>>> >>>> - new class template (optional at first) >>>> - Monticello support >>>> >>>> Marcus >>>> >>>> >>> >>> >> > >

June 25, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40044 Home: https://github.com/pharo-project/pharo-core

June 25, 2014

[pharo-project/pharo-core] 39fbb8: 40044

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 39fbb8300ca8a48b1fbef3d69509bfd1de4853a2 https://github.com/pharo-project/pharo-core/commit/39fbb8300ca8a48b1fbef3d6… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-06-25 (Wed, 25 Jun 2014) Changed paths: A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script44.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40044.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot.package/InstanceVariableSlot.class/README.md A Slot.package/InstanceVariableSlot.class/definition.st Log Message: ----------- 40044 - add subclass for Slot - change all Slot objects for that class http://files.pharo.org/image/40/40044.zip

June 25, 2014

Re: [Pharo-dev] [Pharo4] Slots: API for Classes

by Marcus Denker

On 25 Jun 2014, at 16:43, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Slot > \SimpleSlot (current iv slot) Yes, the naming of that oneâ¦ I think we just need to take the freedom of iterating. For now I called it âInstanceVariableSlotâ, but that might be confusing and it is a long word. > \CollectionSlot > \BitmapSlot > Esteban A. Maringolo > > > 2014-06-25 9:38 GMT-03:00 Norbert Hartl <norbert(a)hartl.name>: >> >> Am 25.06.2014 um 14:22 schrieb Marcus Denker <marcus.denker(a)inria.fr>: >> >>> >>> On 25 Jun 2014, at 14:16, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>>> Very nice! >>>> >>>> Next would be an example of how to specialize a slot :) >>>> >>> >>> Yes, the next steps are: >>> >>> - introduce abstract superclass for Slot >>> >>> (I am not yet sure: will the be âSlotâ and the default slots are âInstVarSlotâ, or do I add a >>> âAbstractSlotâ class and Slot stays the default? Maybe thatâs better) >>> >> I like the former better. But if you do can you please help stop that naming scheme? Could we name it InstanceVariableSlot then? Pleeeeaaaase? >> >> Norbert >> >>> - Opal needs to delegate code generation to the Slot. >>> >>> - The abstract slot generates by default reflective read/write access code >>> >>> - subclasses can override. (e.g. the default slot overrides to do pushIvar/storeIvar bytecode) >>> >>> This is the enough to do behavioural changes to simple Slots. >>> >>> After that we need to check the code for âvirtualâ slots where e.g. multiple Boolean slots are mapped to one >>> hidden flag ivar. >>> >>> And the of course >>> >>> - new class template (optional at first) >>> - Monticello support >>> >>> Marcus >>> >>> >> >> >

June 25, 2014

can I be added to the pharoextras team?

by Paul DeBruicker

If not, could I be added as a contributor to the PharoExtras/XMLSupport repo? my sthub username is pdebruic Thanks for your help Paul

June 25, 2014

Re: [Pharo-dev] [Pharo4] Slots: API for Classes

by Esteban A. Maringolo

Slot \SimpleSlot (current iv slot) \CollectionSlot \BitmapSlot Esteban A. Maringolo 2014-06-25 9:38 GMT-03:00 Norbert Hartl <norbert(a)hartl.name>: > > Am 25.06.2014 um 14:22 schrieb Marcus Denker <marcus.denker(a)inria.fr>: > >> >> On 25 Jun 2014, at 14:16, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >>> Very nice! >>> >>> Next would be an example of how to specialize a slot :) >>> >> >> Yes, the next steps are: >> >> - introduce abstract superclass for Slot >> >> (I am not yet sure: will the be âSlotâ and the default slots are âInstVarSlotâ, or do I add a >> âAbstractSlotâ class and Slot stays the default? Maybe thatâs better) >> > I like the former better. But if you do can you please help stop that naming scheme? Could we name it InstanceVariableSlot then? Pleeeeaaaase? > > Norbert > >> - Opal needs to delegate code generation to the Slot. >> >> - The abstract slot generates by default reflective read/write access code >> >> - subclasses can override. (e.g. the default slot overrides to do pushIvar/storeIvar bytecode) >> >> This is the enough to do behavioural changes to simple Slots. >> >> After that we need to check the code for âvirtualâ slots where e.g. multiple Boolean slots are mapped to one >> hidden flag ivar. >> >> And the of course >> >> - new class template (optional at first) >> - Monticello support >> >> Marcus >> >> > >

June 25, 2014

Re: [Pharo-dev] [Tutorial] Rediscovering the UX of the legendary HP-35 Scientific Pocket Calculator

by Sven Van Caekenberghe

On 25 Jun 2014, at 16:16, jdelgado(a)lsi.upc.edu wrote: > Yes, I agree. It is simply awesome. Thanks a lot! Thx! > Bests, > > Jordi > > PD: I also love old calculators, though my first love was the HP-41CV Yes, the HP-41 was the one I was dreaming about when I was young: it was so cool - it went on several Space Shuttle missions and they used that a lot in their ads - but it was way too expensive for me as a kid.

June 25, 2014

Re: [Pharo-dev] [Tutorial] Rediscovering the UX of the legendary HP-35 Scientific Pocket Calculator

by Sven Van Caekenberghe

On 25 Jun 2014, at 16:06, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Sven. This is outstanding. > > It is not only a comprehensive tutorial, but also is good loking, with > a little touch of nostalgia for those who used a RPN calculator in the > past :) > > I wish we all could produce code and documentation the way you do. > Maybe cloning you is an option. > > Congratulations. Thank you, Esteban, I am glad you like it. Thanks for the medium.com recommendation too ! > Best regards, > > > ps: there is a typo in the first image of "Modelling the HP-35" section. Fixed. Yes, I think too much about models ;-) > Esteban A. Maringolo > > > 2014-06-25 10:29 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >> Hi, >> >> I have written a new, extensive, long form, introductory article about >> Pharo. >> >> Rediscovering the UX of the legendary HP-35 Scientific Pocket Calculator >> >> A tutorial on Pharo, test and specification based immersive programming >> >> >> https://medium.com/@svenvc/rediscovering-the-ux-of-the-legendary-hp-35-scie… >> >> >> It is a bit different because >> >> - it is based on a non-trivial example >> - it uses a backdrop story unrelated to Pharo >> - it uses several multimedia elements >> - it is published on medium.com which is a general publishing platform >> >> The appendix describes several ways you can get the code. I think building >> both a Spec and Seaside UI from the same specification as well as reusing >> functional tests in different contexts is cool. Anyway, I hope you enjoy it. >> >> Sven >> >> -- >> Sven Van Caekenberghe >> Proudly supporting Pharo >> http://pharo.org >> http://association.pharo.org >> http://consortium.pharo.org >> >

June 25, 2014