Model / DisplayableObject relation should be thought carefully

[Ducasse]

• Naively I was thinking that DisplayableObject should be a superclass of Model so that we can
  also directly inherit from it (some objects are not model but still want to have theme, and other)
• DisplayableObject should probably also offer UIManager default access.
• I'm thinking that DisplayableObject could be a subclass of Model. But may be it should not.
  In any case it should packaged in a UI package because right now Model is not depending on UI concerns. So it would be good not to introduce it.

[stale]

To limit bug bankruptcy (see https://www.joelonsoftware.com/2012/07/09/software-inventory/) this issue has been automatically marked as stale because it has not had any activity in 6 months. It will be closed in 1 month if no further activity occurs. If this issue remains important to you, please comment to reactivate the issue. Thank you for your contributions.

Joel on Software

Software Inventory

Imagine, for a moment, that you came upon a bread factory for the first time. At first it just looks like a jumble of incomprehensible machinery with a few people buzzing around. As your eyes adjus…

[Ducasse]

This is still active. I'm waiting for Spec 20 to have have an icon manager and a theme method so that I can check all the non Model/presenter users of smalltalk ui theme smalltalk ui icons....

[guillep]

This is a big non punctual thing, difficult to action.
I propose to close it, maybe this should be moved to a place/wiki that stores "project ideas".