[Grok-dev] Menu system
ct at gocept.com
Fri Oct 20 13:12:47 EDT 2006
I had another thought after writing my last mail:
It comes down a bit to terminology:
- In GUIs, menu items are used to trigger a callback function. They
typically do not have state that shows they have been called.
- In web sites, we normally have something that is called "navigation".
There, navigation entries allow us to select a URL and see where we are
(by checking whether we're on the same page as the navigation entry
would bring us to)
I think current Zope 3 menus mix this up a bit so we have a problem
defining what they do in simple language. Maybe by splitting those
responsibilities up a bit, we can achieve two simple solutions for
(Obviously web applications are a mixture between normal web sites and
GUIs, but maybe this idea was helpful.)
Martijn Faassen wrote:
> Christian Theune wrote:
>> I just had an experience that makes me wonder whether we should abstain
>> from re-using the Zope 3 menu system for grok. It's implementation seems
>> nasty: The interfaces aren't completely described and it makes
>> assumptions that actions of a menu always apply to the currently
>> published object ... As Jim pointed out that menus should be taken as a
>> pattern and re-implemented by different projects, well, we have an
>> opportunity here ...
> I'd be happy to make something new & simple for this. Do you have ideas
> for simple powerful menu systems?
> We should figure out how this project connects to grok; we could have a
> z3c.menu and then use this from grok (as a dependency), or make it be
> part of grok directly..
gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany
www.gocept.com - ct at gocept.com - phone +49 345 122 9889 7 -
fax +49 345 122 9889 1 - zope and plone consulting and development
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://mail.zope.org/pipermail/grok-dev/attachments/20061020/7b491a30/signature.bin
More information about the Grok-dev