Now, one of the biggest problem (or annoyances if you will) with TI (template inheritance) is the following:
Let's say you have a super/master style and 7 styles that inherit from it. At the moment, that means that you will have to copy all the .js files used by the styles to each and every style folder or copy the template calling for the .js file from the super style and put it in each of the inheriting style's template directories and then changing all {T_TEMPLATE_PATH} into {T_SUPER_TEMPLATE_PATH}.In the implementation for 3.0 there are a few limitations to this, which we won’t keep secret. For starters, there is no stacking of fallbacks. It’s only possible to fallback to a template that does not itself declare to be dependent on another template. The other major limitation is that it only affects the files managed by the template engine (*.html) and not the static javascript files bundled with many templates. Those static files still have to be copied, or manually linked using the new {T_SUPER_TEMPLATE_PATH} template variable.
So, either way, you're going to have to create a lot of (somewhat) duplicate files... which is exactly what TI set out to fix in the first place, right?
My suggestion:
Make the super style accept {T_SUPER_TEMPLATE_PATH}. At the moment, it simply ignores it, or at least doesn't do anything usefull with it. If phpBB could check each time it finds {T_SUPER_TEMPLATE_PATH} in the code if the style actually HAS a super style, and if not, change it to {T_TEMPLATE_PATH} then it would fix the whole problem I think. Then we won't have to duplicate all the .js or copy all kinds of templates (and thus exclude them from TI) just because we have to change 1 or 2 lines in them.