[Pharo-project] MultiCompositionScanner depending on Morphic stuff
stephane.ducasse at inria.fr
Thu Mar 15 11:28:26 EDT 2012
>> Good catch
>> We should move them close to MultiCompositionScanner
> Yes, in general the structure of the system is ad-hoc. e.g. the whole Multi-* changes should be folded into
> the classes that they extend (or at least be moved close).
> Other: Canvas is in Morphic,
it should not :)
> it's not clear where text support should be.. and lots more.
yes but no stress one by one and we will get better.
More information about the Pharo-dev