The 'lack of overview' is a general problem with much of our recent work. we changed our content types in this way. I am thinking that Contrib modules might be able to provide alternative UI which is read-only and fulfills the need for an overview. Eventually, those modules might be folded into core. Dries Buytaert wrote:
Well, assuming the general approach taken in the patch, this (moving block location to the individual block config pages) does seem like the most promising proposal so far to improving the admin UI while maintaining multiple themes. Assuming two enabled themes, on the block's config page it might look something like:
_________ --|Placement|------------------------------------------------------- | _________ _ | | Bluemarine |_________|_| [select box with Bluemarine's regions] | | _________ _ | | Blix |_________|_| [select box with Blix's regions] | | | | For each enabled theme, select the region you want this block to | | appear in. | |__________________________________________________________________|
If there is only one enabled theme, we might simplify this to: _________ _ Placement |_________|_| [select box with default theme's regions]
That is what I had in mind. The /only/ drawbacks are that it takes quite a few clicks to layout your blocks, that the administrator will no longer have a good overview, and that it gets us further away from http://www.cyberdummy.co.uk/test/dd.php. Food for thought.
-- Dries Buytaert :: http://www.buytaert.net/