Since the beginning, vBulletin has had some way of inserting style-related variables into its templates. In vBulletin 1 and 2, replacement variables were used, and simple html-esque tags could be inserted in order to re-style text etc. For example:<smallfont>Here is some small text</smallfont> would be replaced with<font size="1" family="verdana, arial, helvetica, sans-serif">Here is some small text</font> The content of the replacement ...
<smallfont>Here is some small text</smallfont>
<font size="1" family="verdana, arial, helvetica, sans-serif">Here is some small text</font>
When I was hired by Jelsoft back in 2001, the first thing I did was to make some sweeping changes to the vBulletin 2 style in time for its fourth beta release, though many of the design elements were already in place and could not be re-done without major changes to the PHP code. For vBulletin 3, the task of producing the style once again fell to me. My goal was to simplify the layout, produce consistent design rules, to make commonly-used controls more prominent and to take those ...
A major feature slated to debut with vBulletin 4.0 is a new front-end style marked-up with semantic XHTML and styled with CSS. The task of producing the new templates using this scheme has thrown up all manner of questions, challenges and show-stopping problems, one of which I will discuss here. Background In vBulletin 3.x, the primary markup vehicle was the HTML <table> tag and almost all elements on vBulletin pages could be summarized as having the following ...
Anyone who runs a color-calibrated workflow and has switched to Vista will be aware that there is a serious problem relating to ICC profiles having their gamma values periodically 'forgotten' by Vista. Attachment 264Thus far, in order to get around this, I have been using a freeware tool called 'Display Profile' to force Vista to load up the correct profile and gamma LUT for my displays. However, as I run a triple-monitor setup, that means a lot of messing around each ...
You've probably noticed that the blog sidebar has now moved to the left of the main content. The original intention had always been to have the sidebar to the right, as this would allow the main content to sit nestled up to the left margin. You can see several style changes I made to facilitate getting the content as far left as possible such as the new skinny vertical 'thead' bars on entry and comment lists. Unfortunately, with some customers insisting that 800 pixel ...
