What I didi for Nautilus was to use pragmas,
this way I have my domain object (Nautilus), and menus are defined in another
class (NautilusRefactoring by example).
And NautilusRefactoring knows how to communicate with Nautilus.
This way, the domain abject can stay clean, and I have a special class for menu
:)
Ben
On Jun 30, 2013, at 7:55 PM, Stéphane Ducasse <stephane.duca...@inria.fr> wrote:
> yes so far I added
>
> menus
> "ugly just to brainstorm and get something working now"
>
> ^ #(('inspect' #inspect))
>
> to build menus but I find that not that nice
>
> On Jun 30, 2013, at 7:34 PM, Damien Cassou <damien.cas...@gmail.com> wrote:
>
>> On Sun, Jun 30, 2013 at 7:06 PM, Stéphane Ducasse
>> <stephane.duca...@inria.fr> wrote:
>>> Now I'm wondering how I could define menu items in a way that I do not
>>> polute the domain object with
>>> menus.
>>
>>
>> you can use double-dispatch and create both a #menuForLogItem: and a
>> #menuForSubLogItem: on the UI. This means to add a #menuFromUI: method
>> in each subclass. You can also use a visitor to have a #accept: method
>> in each subclass instead.
>>
>> --
>> Damien Cassou
>> http://damiencassou.seasidehosting.st
>>
>> "Success is the ability to go from one failure to another without
>> losing enthusiasm."
>> Winston Churchill
>>
>
>
