CSS, Fun, and Modern Browsers
Even though my business offers different services: concept design, art & illustration, and web design – it seems incoming projects will undoubtedly be for the same service at any particular time. For the last couple of months almost everything has been web design.
Thus, web design is on my mind right now. One of the projects on which I have been working, is a redesign of my blog and resource Art & Architecture. Since it is a project for myself, I have decided to design it for a minimum screen resolution of 1024 pixels wide. It looks better on a 1280×1024 resolution, and even better on the 1920×1200 resolution running on my monitor. I have taken some time to play with enhancements using the Spry Framework in Adobe Dreamweaver. I have also been messing around with jQuery. Both offer some very cool possibilities.
The content for all current projects is database driven with structural html markup, and styled with css; no tables. I have been improving my web programming skills by dropping hard earned money on reference books, and doing lots of research on the web, and one thing confuses me a little. I vowed to keep everything positive on this blog, but a little rant here, the “expert” programmers writing these references spend a lot of time talking about designing for people with ultra low res monitors, and how to create work-arounds for people using ten year old outdated browsers. The first thought that comes to my mind, why is anyone using Internet Explorer 5 for Mac? There are any number of browsers available, and they are all FREE!
So I have been testing my code on current browsers: Firefox, Safari, Opera, Flock, Avant, Maxthon, SeaMonkey, Chrome, and Internet Explorer 6, 7, 8. (If you are not using a current browser, here is your opportunity.) As I can only have one version of Internet Explorer on my system at one time, I use IE Tester for testing Explorer. Second rant for this post, as I write the code (as the “experts” instruct me), my pages work perfectly in everything except Internet Explorer 6, 7, 8. So the second stage of every page design seems to be butchering the code three different ways to get it to work in each of the three Microsoft products. And they write our operating system! Microsoft! Learn how to write a browser and quit holding back the web!
Enough said: I must dive back into a reference book and find a hack to make today’s web page work in Internet Explorer. Yeeha!