Spin-off from. This is just the first step in a refactoring process field ui needs.
Regions in Field UI
Now we have "main", "visible", "hidden" as default regions and separate row handlers to work with, etc ... . To alter the fields UI screens, it's very difficult and inefficient altering to obtain things that should be transparent or done behind the scene.
The solution is to use content/hidden so the concept of layouts can more easily be introduced later.
This patch includes:
- make regions consistent across the fields and display overview screens. Important, since there is only 1 region, it won't be shown at display screen.
- make row handling in PHP consistent for all screens. I started with "content" and "hidden" to not change too much at the same time.
- Refactor the code so the overview screens are based on the same base class. (One change is for instance that a method getRegions will define the regions and how the behavior is by default).
- added the region column so it works with regions by default. Nesting behavior is now consistent on both screens as well.
The only visually thing is that you need to change regions to change regions.
Before you needed to set the format type to something or "hidden", which triggered the region update.
FAILED: [[SimpleTest]]: [MySQL] 41,301 pass(es), 38 fail(s), and 40 exception(s). View
FAILED: [[SimpleTest]]: [MySQL] 41,300 pass(es), 10 fail(s), and 0 exception(s). View