[development] Move multiple theme per site support to contrib module

[Jenny Hsueh]

I like the idea of grouping the  theme and block/region admin functions 
together.

but having the notion of "enabled" and "default" theme is essential to 
us, we use groups on our sites and having the ability for each group to 
choose their own theme seems a kicker, people feel that's a space belong 
to themselves.  If there are  other ways to achieve the same result it 
will be fine, but we don't want to lose the  user specified theme 
capabilities  -- i.e. make sure the contribute module for multi-theme 
support is available at the same time when it disappears  from the core.

Thanks
Jenny

Adrian Rossouw wrote:

> I was playing with theme stuff again, and I realised how completely  
> sub-optimal the current configuration is.
>
> How many people actually use user specified themes on their sites?  
> This is the kind of functionality that only
> really clutters up the default interface, and confuses a lot of  
> people for no good reason.
>
> We should simply remove the 'enabled' checkbox, and rename the  
> default radio to 'enable'.
>
> This removes a chunk of code , and all this can very easily be done  
> via _form_alter now, for those that need it.
>
>
>
> What I would also like to see , is that we re-organise the the admin  
> as follows :
> admin
>    display
>        theme (default tab)
>        regions (tab, ie: what admin/blocks used to be)
>        settings (tab)
>
>
> Also. completely getting rid of the tiered theme setting stuff, and  
> only having one set of settings, per theme (same with the block)
>
> I do believe that the block / region settings are very much a display  
> issue.
>
>
>
>
> -- 
> Adrian Rossouw
> Drupal developer and Bryght Guy
> http://drupal.org | http://bryght.com
>
>
>
>
>