[RFC|Merged] Merge style components

[Arty]

I'd say +1, if we implement some kind of theme inheritance, too and allow multiple levels of inheritance.

Oh, I do like that idea! Imagine being able to clone theme by customizing only colours.css

New RFC incoming

[hanakin]

+3 million anything and everything to simplify the mess of theme development and progress it towards the current/next standard I am all for. Personally I am can not fathom ppl who use the current inheritance method or any for that matter, this provides a clean way to allow those who would be to do so gracefully.

[marian0810]

I actually use that a lot

What components are you mixing?

Most of my extra styles only have a theme folder and an imageset, using the template of subsilver2.

[Arty]

Then its not a problem at all. Define template inheritance in style.cfg (currently in template.cfg) and you don't need to copy templates.

[Arty]

Patch (work in progress)

Ticket: http://tracker.phpbb.com/browse/PHPBB3-10632
Patch in progress: https://github.com/cyberalien/phpbb3/tr ... components

[Arty]

First part of patch is available for testing: https://github.com/phpbb/phpbb3/pull/573

Everything is working, except for styles management in admin control panel.

[Arty]

First version of styles management is ready. You can find it here: https://github.com/phpbb/phpbb3/pull/577

What is included so far:

• Merged style components (this RFC) - complete
• Unlimited parent styles tree (RFC) - complete
• Revamp of acp_styles (RFC) - incomplete

What isn't done yet:

• Editing templates via admin control panel
• Purging templates cache via acp_styles (you have to click "purge cache" button on acp index instead)
• Terminology for template inheritance / parent styles and for disabled / hidden / inactive styles (see this post and few posts below it)
• Removing old entries from language/en/acp/styles.php (some entries have been removed)

Everything that is available so far should work. You should be able to install or upgrade forum, you should be able to use all existing styles management functions.

To test template inheritance, I've uploaded pack of styles here: download
It is compressed version of my "styles" directory, includes prosilver, subsilver2 and bunch of prosilver clones made with colorizeit. Most of them have dummy template inheritance set up, some are missing templates in order to test inheritance.

You can create more clones by using function "colorize my files" when editing prosilver on colorizeit.

[ecwpa]

Not sure if this is the right place to ask but, is there a way to not caché templates? This is extrictly for styles developers who don't want to be clearing caché every time you make a change.

[Arty]

admin control panel -> load settings -> recompile stale style components -> enable

[ecwpa]

Thanks! Thats a weird name for that option though.