When I was developing a new Morphic layout policy (in Squeak before there was
Pharo, but I imagine it still applies), I found numerous bugs relating to
bounds and layout methods and the order they get called in various
circumstances; bounds & layout is a poorly documented, fragile part of Morphi
I have some partly-finished Squeak code that creates a schema-specific
validating XML parser & generator (well, data objects that do this) given an
XSD. My motivating use case is to enable quick support of new XML-based file
formats. So, you would design your objects as usual, then run my sche
