On Monday 20 August 2007 20:02, Jim Fulton wrote:
> On Aug 20, 2007, at 7:57 PM, Stephan Richter wrote:
> > On Monday 20 August 2007 09:45, Christian Zagrodnick wrote:
> >> Should we fix that?
> >
> > Yes, or just deprecate the menu stuff. ;-) The default menu
> > framework was
> > insufficient i
On Aug 20, 2007, at 7:57 PM, Stephan Richter wrote:
On Monday 20 August 2007 09:45, Christian Zagrodnick wrote:
Should we fix that?
Yes, or just deprecate the menu stuff. ;-) The default menu
framework was
insufficient in every real-world project I have worked on. Menu
items based
on th
On Monday 20 August 2007 09:45, Christian Zagrodnick wrote:
> Should we fix that?
Yes, or just deprecate the menu stuff. ;-) The default menu framework was
insufficient in every real-world project I have worked on. Menu items based
on the context just do not work.
Regards,
Stephan
--
Stephan R
On Aug 20, 2007, at 9:45 AM, Christian Zagrodnick wrote:
Hoi
I just figured, that the browser:menuItem cannot be registered for
classes. But you can with browser:page. I think if a browser:page
can be registered for a class a menuItem should support this, too.
Also a will break on
get
Hoi
I just figured, that the browser:menuItem cannot be registered for
classes. But you can with browser:page. I think if a browser:page can
be registered for a class a menuItem should support this, too.
Also a will break on
getting the menu items because the implementation doesn't support
