Changes between Initial Version and Version 2 of Ticket #6226


Ignore:
Timestamp:
Nov 21, 2008, 6:16:49 AM (12 years ago)
Author:
bill
Comment:

Replying to alex:

Secondly, I expect that menus will be re-used often, and while there's a programmatic example of adding items to a menu, no example is provided for how to remove them, nor is there a "clear()" method or similar for removing dijit.MenuItem?() instance. Similarly, there isn't a uniform "remove from parent" (not destroy()) method on MenuItem? instances.

Menu.removeChild(MenuItem?) should work, doesn't it?

Lastly, it would seem that the construction of a set of menu items is the common case. Supporting a JSON-style syntax for describing a set of items and their generic properties seems useful for constructing trees of menus.

I agree that's a common case, although it can easily be done by code outside of menu. I don't see the benefit of adding it to Menu itself, although that's debatable. There's also a possibility of dojo.data integration... if you think about it Menus and Trees are similar in their hierarchical structure, and trees work off of dojo.data.

Anyway, I'm going to close this ER for now.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6226

    • Property Status changed from new to closed
    • Property Resolution changed from to wontfix
    • Property Summary changed from dijit.Menu API oddities to Menu: API enhancements
    • Property Milestone changed from 1.2 to 1.4
    • Property Owner set to bill
    • Property Type changed from defect to enhancement