#3579 closed defect (wontfix)
Menu: base MenuItem off of Button/DropDownButton
Reported by: | bill | Owned by: | bill |
---|---|---|---|
Priority: | high | Milestone: | 1.3 |
Component: | Dijit - Form | Version: | 0.9 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description (last modified by )
Make MenuItem? extend Button, and a new Submenu (or similar name) class that extends DropDownButton?.
In terms of API changes this will
- make the Menus hierarchical (see #3578)
- separate widget name for the leaf MenuItems? vs. the inner nodes.
- icon specified as iconClass rather than iconSrc
Change History (8)
comment:1 Changed 14 years ago by
Description: | modified (diff) |
---|
comment:2 Changed 14 years ago by
comment:3 Changed 14 years ago by
Milestone: | 0.9beta → 0.9 |
---|
Given that [9404] is complete, the API is stabilized, so I don't mind deferring the rest of this work to 0.9 final, or even to 1.0.
comment:4 Changed 14 years ago by
Milestone: | 0.9 → 1.0 |
---|
comment:5 Changed 14 years ago by
Milestone: | 1.0 → 2.0 |
---|
comment:7 Changed 12 years ago by
Description: | modified (diff) |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
Changed my mind; refactor is not necessary, or even useful enough to do.
comment:8 Changed 10 years ago by
Component: | Dijit → Dijit - Form |
---|
Note: See
TracTickets for help on using
tickets.
(In [9404]) Make MenuItem? take iconClass parameter like *Button widgets. Make menus hierarchical, like nested lists in HTML. Add some experimental non-menu popups from menu items.
It's starting to look like MenuBar? and Toolbar should be the same widget.
Refs #3579 (it implements the API changes without actually doing the refactoring)