Postby code reader » Thu Mar 04, 2010 5:40 pm
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...
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.
peace.