Grok Menu

[Souheil CHELFOUH]

Hello Grokkers,

We discussed the possibility of working on a grok menu package with
J-W, in Cologne.
I'm very interested into that. Is anyone willing to work on that with
me ? J-W, I guess you won't have much time for that.
megrok.menu is still out there, but I think it needs some serious
cleaning and updating.
If possible, if philiKON is reading this : is it possible to share the
ownership ? thank you.

- Souheil
_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

[Souheil CHELFOUH]

Actually, Martijn is also a package owner :) So, Martijn, if you could
give me the rights... :)
Or "sancho" :)

2009/10/27 Souheil CHELFOUH <trollfot@...>:

> Hello Grokkers,
>
> We discussed the possibility of working on a grok menu package with
> J-W, in Cologne.
> I'm very interested into that. Is anyone willing to work on that with
> me ? J-W, I guess you won't have much time for that.
> megrok.menu is still out there, but I think it needs some serious
> cleaning and updating.
> If possible, if philiKON is reading this : is it possible to share the
> ownership ? thank you.
>
> - Souheil
>

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

[Santiago Videla]

Hey, I'm sancho at pypi

I really would like to help you on this, but I'm don't have too much time these days... I'm studying at university and working in another project with django, so I prefer to don't compromise me with this.

About the package ownership... I thought that I was a "mantainer", but I'm "owner", so it's done. You are "owner" too.

Best Regards

On Wed, Oct 28, 2009 at 6:41 AM, Souheil CHELFOUH <trollfot@...> wrote:

Actually, Martijn is also a package owner :) So, Martijn, if you could
give me the rights... :)
Or "sancho" :)

2009/10/27 Souheil CHELFOUH <trollfot@...>:

> Hello Grokkers,
>
> We discussed the possibility of working on a grok menu package with
> J-W, in Cologne.
> I'm very interested into that. Is anyone willing to work on that with
> me ? J-W, I guess you won't have much time for that.
> megrok.menu is still out there, but I think it needs some serious
> cleaning and updating.
> If possible, if philiKON is reading this : is it possible to share the
> ownership ? thank you.
>
> - Souheil
>
_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

--
Santiago Videla
http://www.linkedin.com/in/svidela

Sigue la mata dando de que hablar siempre abajo y a la izquierda donde el pensamiento que se hace corazón resplandece con la palabra sencilla y humilde que l@s tod@s somos.

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

[Souheil CHELFOUH]

YAY !
Thank you :)

2009/10/28 Santiago Videla <santiago.videla@...>:

> Hey, I'm sancho at pypi
>
> I really would like to help you on this, but I'm don't have too much time
> these days... I'm studying at university and working in another project with
> django, so I prefer to don't compromise me with this.
>
> About the package ownership... I thought that I was a "mantainer", but I'm
> "owner", so it's done. You are "owner" too.
>
> Best Regards
>
> On Wed, Oct 28, 2009 at 6:41 AM, Souheil CHELFOUH <trollfot@...>
> wrote:
>>
>> Actually, Martijn is also a package owner :) So, Martijn, if you could
>> give me the rights... :)
>> Or "sancho" :)
>>
>> 2009/10/27 Souheil CHELFOUH <trollfot@...>:
>> > Hello Grokkers,
>> >
>> > We discussed the possibility of working on a grok menu package with
>> > J-W, in Cologne.
>> > I'm very interested into that. Is anyone willing to work on that with
>> > me ? J-W, I guess you won't have much time for that.
>> > megrok.menu is still out there, but I think it needs some serious
>> > cleaning and updating.
>> > If possible, if philiKON is reading this : is it possible to share the
>> > ownership ? thank you.
>> >
>> > - Souheil
>> >
>> _______________________________________________
>> Grok-dev mailing list
>> Grok-dev@...
>> https://mail.zope.org/mailman/listinfo/grok-dev
>
>
>
> --
> Santiago Videla
> http://www.linkedin.com/in/svidela
>
> Sigue la mata dando de que hablar siempre abajo y a la izquierda donde el
> pensamiento que se hace corazón resplandece con la palabra sencilla y
> humilde que l@s tod@s somos.
>

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

[Jan-Wijbrand Kolman-3]

Souheil CHELFOUH wrote:
> I'm very interested into that. Is anyone willing to work on that with
> me ? J-W, I guess you won't have much time for that.

Not really, but it is still a topic that needs work badly.

Our current approach is not to use "zope's menus" at all, but merely
implement menu-like UI components by way of viewlets.

There's a couple of advantages to that:

1) viewlet-based menu items can easily be registered based on layer and
context and premission requirements.

2) viewlets are generally well understood.

3) URL computation can sometimes be easier.

4) Menu items are registered outside of the views, whereas megrok.menu
registeres menu items as part of the views.


One remark: one of my "conclusions" after discussing menus during the
Neanderthal sprint was that there seem to be two types of menus:

* Menus that provides links to actions or views for the current context
object ("list contents for this container", "view container", "set
permissions for this context", etc.).

* Menus that provide navigational elements for the complete application
("go the the application root", "show the user preferences view",
"configure this or that view").


That's just a quick list of thoughts.. there's probably way more things
to think of...


regards,
jw

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev