John, this is a late reply, but I've been reading through these again... How, do you supposed, you provide the content for each audience? I assume you mean sniffing the browser?
I could check the cgi.http_accept variable for: x-wap.wml, vnd.wap.wml, x-hdml, and other similar values. Would that be enough to sniff the difference between mobile and desktop? I'm not sure which way I will go with this. I'm still evaluating everyone else's suggestions as well. Thanks M!ke -----Original Message----- From: John Dowdell [mailto:[EMAIL PROTECTED] Sent: Thursday, April 14, 2005 3:54 PM To: CF-Community Subject: Re: Handheld Layout Development (was RE: CSS) Dawson, Michael wrote: > [When developing WWW pages and also delivering to mobile > audiences, do you prefer one doc or two?] Some people believe there's "content" which can be poured into lots of different containers. Oftentimes people enamored of "web standards" do not like it when multiple documents are used instead of CSS. Another scenario is when activists disparage separate pages optimized for text-to-speech converters. Me, I'd be tempted to make sure each audience has the best experience possible, and would optimize the content for the way each audience would use it, even if that means separate files. jd ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:5:154779 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/5 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:5 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.5 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
