Thank you Stephan, I think the image is becoming much clearer. However I still don't understand how SRP applies here:
> Person>>asNameMagritteMorph > ^(self magritteDescription select: [:each | each label = 'Name']) > asMorphOn: self Surely this is responsibility of the tool that needs it, no? Otherwise the Person class would have to describe every single possible scenario. Or maybe the tool would puts this into an extension protocol, which while visually places the code to Person class is actually separated (because it's part of another repository). > >> Also, is there maintained Magritte-Spec? I've seen something by Sean, >> but it's from 2013 with a single-ish commit. > > > I don't know if it needs more. Nothing changed in the spec interface since > then, did there? The Magritte-Spec seems to be just an experiment (with three classes) and it breaks Magritte-Morphic. Also I know I have changed Spec interface in the last year alone and as far as I can tell there was a lot work done in before. In any case I can always use asMagritteMorph morph asSpecAdapter in the meantime and maybe stitch together a Spec version once I am comfortable with Magritte. Thanks! Peter
