Quote:
Your themes have one form error and numerous warnings for missing div's tr's and tables etc.
May not sound like much, but if and when one goes to add mods or other markup to the themes, the misconfiguration is more than likely to create unwanted problems.
I also don't understand why you needed to rename files, or include the default.cfg in your themes as the latter removes the global attribute of the default.cfg, and all .cfg additions and changes if necessary could have been added or included into the style.cfg.
You also need to re-work the cms blocks to be compatible with the default layout of IP themes, rather than suggest that advert blocks be compromised - Because that's what Icy Phoenix is all about.
Edit: Damn 24 hr restriction! :shock:
elpulgas wrote: [View Post]
There is absolutely no difference between a monitor and a TV irrespective of its size, resolution or whether it is progressive or interlaced.
The screen only mimics the digital input that the markup provides. :P
The biggest problem is that people add "fixed width" in amongst "variable width" when creating themes or any other html markup.
Consider - If it's fluid width then use %'s, if not then use fixed px, as combing the both does create the problems you highlighted.
In other words - It's the programmer - not the monitor.
Hell! I use a 40 inch "TV" at times on unreal resolutions, and if it "Breaks" - It's usually not the "TV's" problem. ;)