Since I hadn't addressed your points in my previous post here goes:
code reader wrote:i think that the main issue here is style inheritance.
since we do support style inheritance now, i think that the question is: how many existing subsilver-based styles use it?
if there are some who do, to stop supporting it would mean that we deprive the developers of those style of the option of the option to upgrade to 3.1.
imo this would be a bad thing.
however, if all the subsilver styles are done in cut/paste, i do not see a huge problem with stopping the support.
maybe one of them will publish a "how to upgrade your subsilver based style to 3.1" on the wiki...
I agree that this is a problem and it might certainly be useful if someone were to maintain the subsilver2 template for 3.1, but I do not think it is important enough to put a lot of resources into that. If we can we should definitely provide instructions on how to upgrade, although I imagine that to be a process difficult or impossible to explain to regular users.
code reader wrote:of course, a different issu altogether is the necessity to fix prosilver, especially where performance is concerned.
we know for some time now that prosilver has some serious issues, specifically around the use of css:
-- style.php is expensive, performance-wise.
-- unlike subsilver, the cache does not work as intended: modifying one of the .css files does not trigger automatic recompilation. i think it's becuase of the @inclusion, but i am not sure.
-- the whole "css in the database" is a mess.
in short: prosilver needs some fixin', not in the .html or .css, but in the php mechanism that handles the css.
this is not directly related to stopping the support for subsilver, except that for some time now subsilver was the "last resort" of those who got burned by one of prosilver issues mentioned.
Chris has already worked on these issues in the feature/ascraeus-experiment branch. Current intent is to use that code for 3.1. This means we will drop support for database stored css and get rid of a php request for "dynamic" styles by pre-compiling them for all language/template/imageset combinations. Apart from that, you're welcome to suggest improvements to the style itself, although we should really start a new topic for that
code reader wrote:request:
we invested countless hours ("we" as in 'shs, dhn and myself mainly in bug-reporting capacity, though i did contribute some patches too) making subsilver RTL-friendly.
then when prosilver was exposed (you can't imagine how grateful i was for the accident that forced its premature exposure - the original psotfx plan was to expose it on the day of releasing gold, if you can imagine that), we invested a second batch of countless hours making prosilver RTL-friendly.
please, if you want to replace subsilver with a prosilver-derivative or completely new CSS-based subsilver lookalike, *please* get at least one RTL-nik in the loop before unleashing it on the public.
I do remember Paul's ideas on keeping the style secret until last minute and never quite liked that idea. There is not going to be any private style development of any kind. So no such issues should arise in the future.