Hi All.

I'm trying to change a web site I'n building from web only to also be
accessible from basically any internet capable device. I want to use some
variation of cf_bodycontent to generate the pages. This is how I've thought
about doing it:

1) I set a struct of attributes for such things as number of characters per
line and navigation style in the request scope that identify the physical
characteristics of the device.
2) Use my dsp_ and act_ pages to create XML content rather than HTML.
3) Create a request.bodycontent variable that contains a well formed XML
document based on a DTD that I specify. I don't want to use WDDX because it
is too focused on handling different data types and I want mine to handle
different parts of a given page eg title, main heading, body, ad,
navigation,auction etc.  and be completely specific to my needs.
4) Create a variation of CF_BODYCONTENT that takes the request.bodycontent
variable, runs it through an XSLT engine that will transmogrify it into WAP,
or HTML or RIM or whatever.

I just want to create an abstraction layer for the data.

My question is are there any good, preferably free XSLT engines that I can
use as I'm writing this tag? Is there a better way of doing this within the
fusebox environment. I don't want to get into the situation of creating
whole directories that do nothing but take existing functionality and
repackage it for other devices.

ed

PS Yes I am aware of the irony of wanting to support these technologies
after flaming away at them last week :) I still think HTML will be the
primary way of accessing information but little nuggets of VERY PERTINENT
information might be nice to have when you need them. I would also like to
think of a way of abstracting data from presentation thus leaving the
possibility of opening my web sites to whole universes of alternative
devices relatively easily.

------------------------------------------------------------------------------
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to