Two configuration sections:

Configuration

/admin/config/user-interface/mobile-navigation

"Configuration > User Interface > Mobile Navigation" will be used for declaring the media queries configuration for mobile navigation. It will show a list of displays(Breakpoints), and allow to reorder them and create new ones.
Each display will have a Name and a Media Query that defines it.

/admin/structure/menu/manage/MENU_NAME/mobile-navigation

We are mooving mobile navigation configuration to the menu configuration seccion.
At Admin - Structure - Menu, each corresponding menu will have an additional tab for "Mobile Navigation".
That tab should have a group of sub-tabs, one for each Display.
On each sub-tab the will be a form with all the configuration of a Mobile Navigation instance wich will be aplied to the current Menu at the current selected Display.

Data

Heres my proposal for a Database Schema to support the needs for MNv2.
The table MenusDisplay has all the fields needed for storing the features of each Mobile Navigation instance Configuration. I included the ones needed for new features like making the titles configurable and for making the default state(Expanded or collapsed) configurable.
Database model for MNv2

JS changes:

* Support for multiple configurations has changed the whole interface. It also of course, changes everything in the Javascript. A new parameters configuration definition for the construction of the main mobile_menu object is needed.
* JS will no longer clone the menu. It will only apply behavior and bindings to a menu that has already been redered at the server and came included with the HTML of the current page.
* Effects and menu pluguins require refactoring. We are incorporating the use of JQuery UI.
* Plugins must be external to the core of the mobile menu class. Only the plugins needed at the moment must be invoked.

CommentFileSizeAuthor
DB.jpg126.05 KBx7ian

Comments

x7ian’s picture

x7ian commented
Issue summary: View changes
lauriii’s picture

lauriii
he/him
Primary language Finnish
Location Finland
commented

Umm, what about menu blocks?

x7ian’s picture

x7ian commented

Thank you @lauriii!

I have implemented in the 2.x-dev the placing of block for the menu button.
I belive the Expand in place effect is the only show hide effect that needs to move the menu to a block tight where the menu button is located. For the rest of effects the menu is positioned fixed or absolutely so it doesnt need to be placed on any particular block.

What are your thouts on this lauriii?