View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000016 | Composr | core_menus | public | 2010-04-05 22:25 | 2013-11-19 22:25 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Severity | Feature-request | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0000016: Fully support menu stitching | ||||
| Description | For example, making a drop-down menu by stitching other menus, or stitching a dynamic menu onto a node of a custom menu. Currently it's available via hacking a special coding in via the tooltip field. This was a short-term fudge to avoid changing such a core database structure. | ||||
| Tags | Risk: Large database change | ||||
| Time estimation (hours) | 3 | ||||
| Sponsorship open | |||||
| related to | 0001366 | resolved | Chris Graham | Adaptive menu mode |
| child of | 0000142 | resolved | Chris Graham | Merged sitemap API |
|
|
We may want to officially make use of this, redesigning Composr to have a single drop-down menu that spans all zones. Also redesign the CSS to be a lot simpler - remove zone menus and top menus, leaving just dropdown, embossed and tree. Place each menu type in it's own CSS file, and use "mix-ins" to avoid repetition (or possibly just copy&paste, if it makes things easier for themers). For mobiles, it might be best to have a menu button that pulls out a full screen accordion-based navigation. I'm not sure, it needs thought. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-06-08 00:15 | Chris Graham | Tag Renamed | Large database change => Risk: Large database change |
