Prosilver redesign

[DavidIQ]

It isn't different information at all. If there is a new style it would be included with the core product and the old style would receive minimal support. This isn't any different from what was eventually done with subsilver2. The difference being that subsilver2 was originally designed to replace the 2.x subsilver, that is until prosilver came along at which point prosilver got the majority of the attention. This, however, is EXACTLY what we are trying to move away from.

[Master_Cylinder]

To me that's supporting two styles, even if one isn't going to be actively developed. *shrug*

Prosilver doesn't need a lot of tweaking, imho...

[DavidIQ]

If it is then it's that much less likely to happen. Suggesting we go back to what we were just trying to move away from is a step backwards imo.

[PixelFool]

Prosilver doesn't need a lot of tweaking, imho...

It could do with some cleaning up though, like replace the ugly rounded corner images with CSS border radius, we could also use something like SASS so in the CSS files we could have variables for the rounded corners, eg:

Code: Select all

$radius = 5px;

.navbar {
    border-radius: $radius;
    -moz-border-radius: $radius;
    -webkit-border-radius: $radiues;
}

With this, customising the style will be that much easier, and hopefully bring more people into styling with proSilver.

[Master_Cylinder]

That's what EXreaction said would happen (you guys fight it out) and it makes more sense than just replacing prosilver with something new. It's not going backwards, it's passing another milestone. Replacing prosilver with subsilver2 would be going backwards.

[DavidIQ]

Improving prosilver and then keeping it in place as a single style is NOT what you and some of the others were suggesting

[Master_Cylinder]

That's exactly what I suggested. I'm against just replacing it with an unknown new style which is what would have to happen if there aren't 2 styles when they add the next one. Prosilver will need to be depreciated and replaced someday. EXreaction said there will be 2 styles and you said there won't be 2 styles. I don't know which is correct now so I'll let you guys figure it out...

[hanakin]

The more i actually think about it I keep coming back to including BS as an asset via the cdn, we can tie that back to an admin setting to include it if need be but this allows not only for building off it for a new official theme but makes it easier for theme authors to jump on board and build BS themes. Then the official theme we would still need to revamp the structure of the code as I stated before to better separate the content into block, element, modifier and individual files within . As well as define our own mixin/variable files.

I would also go as far as to including the font-awsome cdn in a similar fashion.

Since BS & FA are essentially both widely used across the web and more and more point to the cdn for them their is an increasing chance that its already cached

[Pony99CA]

Sounds like BS to me, hanakin.

Seriously, for those of us who got lost in the length of this topic, what is "BS"? (Googling didn't help much. )

Steve

[Master_Cylinder]

BootStrap