Sebastian, thanks for sharing your code and thoughts. Maybe what Mariano was implying is that you already have the data for the backup in the changes, and having yet another mechanism for that adds complexity to the system.
I think is a good idea, but too focused on the categories you choose up front..and not on those actual changes you perform on the system. Which is why the recovering from the changes file is better. Dont worry, the image crashes every now and then to all of us! fortunately since Pharo1.0, less and less every day... Regarding the UI, you should check out Spec, by Benjamin and Stef. It's easier to create morphs programmatically than with the raw Polymorph. And also check out Glamour, the ones used in Moose. Saludos, Fernando On Mon, Nov 12, 2012 at 8:55 PM, Damien Cassou <[email protected]>wrote: > On Mon, Nov 12, 2012 at 8:06 PM, Sebastian Nozzi <[email protected]> > wrote: > > P.S. 2 -- I was amazed at how easy it was to code the UI! UI > > programming in Squeak/Pharo was always an area where I thought must be > > incredible complicated, but thanks to UITheme's builder (Polymorph?) > > it's a breeze. Good work! > > The new UI framework is Spec, I guess it's better than Polymorph but > don't know how they compare. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >
