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

[Bèr Kessels]

Op dinsdag 6 juni 2006 16:49, schreef Adrian Rossouw:
> 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.

Good proposal. A few sidenotes:
 * As long as we keep the posibility to swap themes with an API, or by 
changing a SESSION var, I see no problems. Adrian S can still develop / test 
his themes, but should use a (new, yet to be coded) feature in 
themedev.module. People can still set admin themes, mobile themes and so with 
modules such as print_theme.module, sections.modules, etc.
  * Regions are theme specific, so if you want to proceed this way, you really 
need to overhaul the regions system to. I would make that two diff. projects
  * We cuold see to it that a module is developed by somone who thinks the 'my 
settings theme settings' must remain. user_themes.module? That cannot be 
hard. :)

Bèr
-- 
 [ Bèr Kessels | Drupal services www.webschuur.com ]


Drupal upgrade repareert kritiek beveiligingslek:
 http://help.sympal.nl/drupal_upgrade_repareert_kritiek_beveiligingslek
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.drupal.org/pipermail/development/attachments/20060609/23cdec14/attachment.pgp