I don't know if the ppl here (the dev team) is open to a new template. I think it's a good idea to have a brand new template.
I'm support your idea. Prosilver is a good theme in the looks but contains bad coding. Subsilver2 is ok theme but in the code it is almost the house of the Adams family "...mysterious and spooky...".
I don't know how your way of writing HTML/CSS code to design works but I'll be much available to help you deciding how to implement design ideas into HTML/CSS. I also think that the dev team should also have a vote in that. We really need a clean CSS, a clean HTML, an HTML as expressive as it can (using HTML5) and to compact CSS itself. Actually a CSS merger & compacter and a js merger & compacter would be awsome for phpbb3!
We're going to be using Assettic to handle resources in 3.2.
While I like the idea of a new template, I definitely don't think that it should be done for 3.2. It would take far too long, and prosilver would have to be maintained anyway, for the benefit of other styles. I would maybe
support a new style for 4.0.
What would take too long? design and coding it? if nothing else we need to start thinking of it in either aspect we can at least begin desing but for what I am think is something plain and basic yet still visually appealing. If we can can enough ppl with experience in all the areas it should be fairly easy. The hardest part to implement would be the JS as we need to replicate all the curretn functionallity into a new theme but it really needs to be rewritten and externalized essentially deign and code the theme semantically in flat html then go back through plit it up into the proper templates once that is achieved then add JS functionality it took me a whole month or two by myself to rewrite prosilver modern mock-up I did last year and that was with no help and rederic from the community.
I would hope it would or definately should be a lot cleaner than even that turned out as I was trying to replicate a design that was not planned for a proper semantic structure.
We need to list things out methodically what we need seperate it out in to groups of like features, what can be accomplish via a list what would be a drop down menu etc.. doing this will cut the coding time down before we even begin the design phase by litererally weeks as they would essentially be coded and styled once then tweaked slightly on an as needed bases sort of like a library of elements so to speak but on paper
I have been advicating this for over a year now that the main thing holding this effort back is mainly forum_fn.js, and the numerous inline functions in the theme that need to be summed up into psuedo at least to reimplement.
As mentioned earlier I am kind of in the middle of working on a redesign of my own site as well as tweaking my style as well and to work on another design would not be prudent as their would tend to be layover from own to the other I like to spread this out so that I code one and while design another to avoid this. However once I finish or get tot he heavy coding and finalize the design for my own project I will go full steam with this but until then I do not see any reason why we can not start a disscussion on the organization aspect that I mentioned above at least in the mean time. I literally have hrs out work where I can not really do anything but sit and troll in IE8 I want to take a "take our netwrok guys to the matresses!" somedays if you get the reference, but what can you do company policies and all.