Voting starts in March for the Drupal Association Board election.
This is a sub-issue to
Drupal core only supported static layouts so far, with defining characteristics of a fixed set of regions and a static markup structure with pre-baked CSS positioning. It is not possible to edit these layouts in a user friendly way, so with, we are proposing a set of modules to serve this need in Drupal core.
This issue is about the dynamic region list handler, which is a very simple module that handles a list of machine name + label combinations with some pre-defined regions shipped with the module in configuration, all regions being editable and deletable. These regions are going to be used in the editable layouts later on in other modules.
Admittedly, this module has not much use without editable layouts given these regions are not expected to be used or useful outside of editable layouts.
The proposed module is named region with a configuration entity called Region and the respective form controllers and default configuration. Test coverage for creating regions, editing regions, deleting regions and doing these with built-in regions is included.
|#22||region-module-22.patch||17.72 KB||Gábor Hojtsy|
FAILED: [[SimpleTest]]: [MySQL] 48,167 pass(es), 0 fail(s), and 105 exception(s). View
|#22||interdiff.txt||2.48 KB||Gábor Hojtsy|
|#21||region-module-21.patch||18.31 KB||Gábor Hojtsy|
PASSED: [[SimpleTest]]: [MySQL] 46,553 pass(es). View
|#21||interdiff.txt||520 bytes||Gábor Hojtsy|
|#20||region-module-21.patch||18.31 KB||Gábor Hojtsy|
PASSED: [[SimpleTest]]: [MySQL] 46,539 pass(es). View