I'm building a custom skin that allows modules in a Pane to be arranged horizontally (float Left), and thus allow me to create an adaptable responsive design for my client.
The design points toward the existence of several container types (around 10), but there are 4 colour schemes, and each can be used in quarter width, half width, 3 quarter width and full width versions. Clearly I'm keen to write 10 adaptable containers instead of 160 static ones.
My question relates to how I can implement my interface (the settings are to be stored in TabModuleSettings). There are two parameters, Colour Scheme and Layout Width.
In my demonstration version, I added the parameters by manually altering the ModuleSettings control which contains the Container preview tools.
My Ideal scenario would be as follows:
1) Have the options appear on the ModuleSettings page using a built-in expansion method - it doesn't look like there is one even though I can see similar forum threads asking for one. I'm using DNN 7.0.0, can this be done by configuration without changing DNN code?
2) Add items to the Module Actions menu, driven by the selected Container. Can containers add items to the Actions menu?
3) The actual fields displayed on the ModuleSettings page to be defined by an Interface of the Container or Attributes etc.
Probably a big ask, but I haven't started on this yet, and I want to use the direction that will have the least impact on the core code-base.
Thanks for your help.