for the logger in StephaneDucasse/SystemLogger/
But I'm not really happy.
Do not use the configuration since I was editing it.
Stef
On Jun 30, 2013, at 10:11 PM, Tudor Girba wrote:
> Where can I look at this code?
>
> Doru
>
>
> On Sun, Jun 30, 2013 at 8:32 PM, Stéphane Ducasse
> wrote:
>
Where can I look at this code?
Doru
On Sun, Jun 30, 2013 at 8:32 PM, Stéphane Ducasse wrote:
> Ok I will look at it or you will show me.
> For now I'm in brainstorming and API extension stabilisation phase.
>
> Stef
>
> On Jun 30, 2013, at 8:23 PM, Benjamin <
> benjamin.vanryseghem.ph...@gmail
Ok I will look at it or you will show me.
For now I'm in brainstorming and API extension stabilisation phase.
Stef
On Jun 30, 2013, at 8:23 PM, Benjamin
wrote:
> What I didi for Nautilus was to use pragmas,
> this way I have my domain object (Nautilus), and menus are defined in another
> clas
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
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 wrote:
> On Sun, Jun 30, 2013 at 7:06 PM, Stéphane Ducasse
> wrote:
>> N
On Sun, Jun 30, 2013 at 7:06 PM, Stéphane Ducasse
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 #men
