From my experience css is even more unreliable than user agent being set and all
browser producers seem to have their own idea of what a standard is supposed to
look like as well. At least with table layouts most of the current desktop
browsers will make a half decent try. With companies like Netscape and Microsoft
providing browsers you should stay away from strict anything is my advice :)
It depends what you're aiming for. If you're aiming for pixel perfect display on the usual browsers, great -- go for tables and the usual hacks. But in the meantime you're sacrificing forwards compatibility for backwards compatibility, making your site hugely inaccessible, causing huge ongoing development costs (update the hacks to support newer browsers and devices), etc etc.
What's the point in developing three or more sites (WAP, PDA, Desktop) when one can do the same, with a few SMALL sacrifices.
As a bonus, you're developing HTML for EVERYONE, not turning away ANYONE, and you're saving your client some money.
Anyway, this is getting a little OT :) You're entitled to do things your way, and so am I... the $'s and accessibility are making my decisions for me.
The ideal way of detecting a wap browser is through the accepted mime types from
the request header but I am not sure if that info is passed on by PHP.
You could try
<? $headers = width: 300px;; print_r($headers); <? and see what is supplied under accept with various devices
You need to look for something like this:
text/vnd.wap.wml for .wml files (WML source files)
application/vnd.wap.wmlc for .wmlc files (WML compiled files)
text/vnd.wap.wmlscript for .wmls files (WMLScript source files)
application/vnd.wap.wmlscriptc for .wmlsc files (WMLScript compiled files)
image/vnd.wap.wbmp for .wbmp files (wireless bitmaps)
Nice idea!
Justin
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
