2017-04-28 12:26 GMT+02:00 Peter Uhnak <i.uhnak@gmail.com>:

> In fact they are not adapters. They are factories which creates backend
> views (morphs). And now there are completely no logic behind them: every
> adapter just passes state received from model to view instance.

This depends heavily on what the respective APIs provide.

In TabAdapter I connect SpecTab and MorphicTab directly, so it no longer lives during runtime.

In LabelAdapter the emphasis is being transcoded from symbol to random numbers (so this is not simple delegation)
In MenuItemAdapter you can see much more behavior.

All they do is asking model about set of options. For example menu adapter ask��

��self model autoRefresh ifTrue: ifFalse:

And this logic can be moved to model itself and represented by different model classes if necessary. (I talk about model as a presenter)