Re: Board icons usability for themers
Reply #15 –
there's exactly one place for that technique in index.css, the styling of the select boxes.
All other's are part of the editor css, mainly to save a buch of http requests.
Let's be a bit more realistic: how often have you seen a custom theme with it's own editor icons (made from a novice themer)?
Re: Board icons usability for themers
Reply #16 –
Ok, so let's be a bit more realistic. Exactly what awesome benefits do you get from doing the select boxes, and only the select boxes, this way in index.css?
Re: Board icons usability for themers
Reply #18 –
That'd be ok, for the editor buttons, if you comment them all. I still can't see the point of throwing this stuff into index.css though.
Of course, as soon as someone tries to make a dark theme they most likely will want to change all the editor images, for the simple reason that the defaults would be largely illegible on a dark background. Admittedly this is probably not something beginners are likely to attempt, but is something that I and others have done in the past with SMF themes.
Re: Board icons usability for themers
Reply #20 –
I'm up for selects just using CSS, but don't really see why they needed an image there anyway.
Re: Board icons usability for themers
Reply #23 –
That's the point: you can't. So you can't use a sprite for smiley.
But you can use the base64 trick if you want (AFAIU).
Re: Board icons usability for themers
Reply #24 –
Yes. Look at the Wedge source. If someone uses a smiley somewhere, it adds a CSS file (a few gzipped kb's) with all default smileys, encoded. It really is faster. Especially in the editor.
Re: Board icons usability for themers
Reply #29 –
There should be a glyph that would work, some of the better arrows were missing from some of the fonts sets we use, I got caught by that a couple of times. There should be something we could use out of the font-awesome css as well since thats loaded by default, although in this case one of the standard font glyphs would be better.