> > I would like to know how to ask the system what classes did I change. > But the only things I found took minutes to execute (asking every > class for its authors, or something like that). Very brute-fore. I'm > sure there is a better approach I am not aware of.
You can either register to the systemAnnouncer in Pharo 2.0 and you can register to get specific announcement (class creation….) or you can query the Changeset singleton >> Which is why the recovering from the changes file is better. > > I don't see it as "which one is better". I am honoured that this was > interpreted as a serious theoretical "inclusion" as a Pharo feature, > with shortcomings or not :-) > >> Dont worry, the image crashes every now and then to all of us! fortunately >> since Pharo1.0, less and less every day... > > Yes, I also noticed! The VM is very robust nowadays! > >> Regarding the UI, you should check out Spec, by Benjamin and Stef. It's >> easier to create morphs programmatically than with the raw Polymorph. > > I think I actually used Spec, but not sure... > >> And also check out Glamour, the ones used in Moose. > > Glamour is for building tools, right...? Could I have used it...? > >> Saludos, >> Fernando > > Saludos también! ;-) > > Sebastian >
