[Glamour] open new browser action

Excellent initiative!

You are working on this already open issue :)
http://code.google.com/p/moose-technology/issues/detail?id=464

- I would prefer the name to be spawn instead of actAndOpen
- you should put the actions in the same list as the others instead of adding a new openBrowserActions instance variable. This is because we want to be able to control the order of actions in the menus. Right now, you are adding them at the end of the menu and this is not good enough.

Cheers,
Doru

On 9 Aug 2011, at 12:36, Cyrille Delaunay wrote:

> Hello ,
>
> I started to work on a  'actAndOpen' mechanism.
>
> The idea would be to allow glamour to encapsulate the action of opening a new glamour browser (the use case i have in mind for now is to open a GLMWizard).
> The model store those sepecific actions (like actions , selectionActions and now openBrowserActions and selectionOpenBrowserActions) , then each renderer now how to deal with them.
> What I did for now is to provide a similar interface than for other actions:
>
>          aBrowser actAndOpen: [ ... ] entitled: '..'.
>
> The requirement is that the block return a browser.
>
> For now selectionActAndOpen: works fine
>
> Does this looks correct ? Am I taking the good direction ?

> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"In a world where everything is moving ever faster,
one might have better chances to win by moving slower."




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Hi Cyrille,

Nice job. It looks good now.

Could you close the issue? :)

Cheers,
Doru

On 9 Aug 2011, at 13:01, Cyrille Delaunay wrote:

> Ok thanks , I will go that way
>
> 2011/8/9 Tudor Girba <[hidden email]>
> Excellent initiative!
>
> You are working on this already open issue :)
> http://code.google.com/p/moose-technology/issues/detail?id=464
>
> - I would prefer the name to be spawn instead of actAndOpen
> - you should put the actions in the same list as the others instead of adding a new openBrowserActions instance variable. This is because we want to be able to control the order of actions in the menus. Right now, you are adding them at the end of the menu and this is not good enough.
>
> Cheers,
> Doru
>
>
> On 9 Aug 2011, at 12:36, Cyrille Delaunay wrote:
>
> > Hello ,
> >
> > I started to work on a  'actAndOpen' mechanism.
> >
> > The idea would be to allow glamour to encapsulate the action of opening a new glamour browser (the use case i have in mind for now is to open a GLMWizard).
> > The model store those sepecific actions (like actions , selectionActions and now openBrowserActions and selectionOpenBrowserActions) , then each renderer now how to deal with them.
> > What I did for now is to provide a similar interface than for other actions:
> >
> >          aBrowser actAndOpen: [ ... ] entitled: '..'.
> >
> > The requirement is that the block return a browser.
> >
> > For now selectionActAndOpen: works fine
> >
> > Does this looks correct ? Am I taking the good direction ?
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "In a world where everything is moving ever faster,
> one might have better chances to win by moving slower."
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"No matter how many recipes we know, we still value a chef."

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev