You are reading a single comment by @Velocio and its replies.
Click here to read the full conversation.
London Fixed Gear and Single-Speed is a community of predominantly fixed gear and single-speed cyclists in and around London, UK.
This site is supported almost exclusively by donations. Please consider donating a small amount regularly.
@Velocio
I'll look at it this morning, but if it's not effortlessly fixable I'm going to skip it.
No.
Better than scalable icons would be sprites or SVG.
But I'm not doing those either.
This is where the bleed into legacy app would entangle me too greatly. A lot of the icons aren't even in the HTML templates, or rather, part of the image file names come out of PHP as variables, and are stitched together at runtime and then construct file names and paths within the templates and end up pointing to gif files.
I could in theory just replace the entire icon set with a similarly sized set of png files, but even then I'm not convinced I would find every trace of the word "gif" in the codebase.
You've got to bear in mind the code base is split between those 2k PHP files and the 1k templates in a database... and because it's PHP it's been abused slightly so a lot happens in eval() at runtime.
It's actually kinda neat that I've managed to butcher vBulletin this far... I'm still using over 90% of the existing vBulletin code. Even though from outward appearances you wouldn't guess it.