Add simple wrapper markup around regions
Add region management capabilities

- Add ways to add/edit/remove regions on the UI
- New admin page to edit weights for the regions (with drag and drop)
- Added API function to remove a layout
Improve UX for editing and adding a region

- Have real titles when editing and adding a region
- Simplify form code by defaulting the region to empty values
Track usage for regions, deny deletion, inform user

- Dig usage data of regions from panels layouts
- Use this information to display in overview table, so users know where certain regions are used
- Deny region deletion if a region is used in a layout; let user remove the region from the layout
- Improved deletion page title
Rename generic layout.admin.inc to layout.admin.regions.inc

In preparation of introduction of other types of things managed by the module, such as breakpoints/grids.
Move regions page to under panels layout screen

Integrate workflow better with building actual layouts.
Add admin UI for grids/breakpoints, media CSS generator

- This will have a fancy JS UI so this is just a quick stop-gap.
- Added code to generate media query based CSS (for now inline, yeah, evil) to apply the breakpoints based CSS to the page.
Move new breakpoint UI to the end, make it possible to remove breakpoints

And remove some duplicate code that was left around
Add machine names to grids for later use

- Convert grids to objects for unification of data types
- Add machine name to grids for future cross-reference from layouts
Avoid required machine name problem when not adding new grids
Make it possible to assign "grid classes" to regions

- Added a (so far) cumbersome UI to assign grid classes to regions
- Add the "col" class to all regions (inspired by gridpak)
- Move region names outside of the layouts, only store them with regions (canonical place for region info)
- Remove some breakpoint/grid related cruft
- Enhance region list API to give us the list by machine name; useful at many places now
Move grids to the ctools exportables API

- Instead of storing grids in a one-off variable, store them in the Drupal schema
- Add ctools integration for export/import support and code based versioning possibility
- Rework API functions to use proper ctools crud functions instead
Apply ctools-type terminology to regions

For a possible future when regions might be managed by ctools; this is not consistent with core naming schemes (the previous one was more consistent), but internal consistency seems more important at this point.
Issue #1698944 followup by akamustang: fix typos in function names
Merge branch 'refs/heads/node/1677196' into 7.x-1.x
First take at integrating the Responsive Layout Designer into the Layout module.

Signed-off-by: J. Renée Beach <splendidnoise@gmail.com>
Merge branch 'refs/heads/node/1677196' into 7.x-1.x
Refactored the prototype from the /prototype directory to the /plugins/layouts/ResponsiveLayoutDesigner directory.

Signed-off-by: J. Renée Beach <splendidnoise@gmail.com>
Removed assets that were only necessary in the stand-alone prototype. Moved some of them into the module's assets.

Signed-off-by: J. Renée Beach <splendidnoise@gmail.com>
Merge branch 'refs/heads/refactor-rld-prototype' into 7.x-1.x