On Tue, 2 May 2000, Tim Gardner wrote:
> I am guessing that the "headless" version is what I do this when I am
> doing a shockwave piece which calls cgi scripts. I create an html
> version which provides a browser interface, albeit more boring, to
> the same basic code so that I can more easily test the cgi side.
>
> My strategy is to create two different versions of an "outputer"
> class, and within the code always call it to do the printing. For
> example $outputer->printResults( $x, $y); Then I create one outputer
> class which outputs proper html and one which outputs what the
> shockwave piece needs (much smaller). Then depending on parameters
> in the cgi calls or in the database, I instantiate the proper
> outputter to handle the call.
This is exactly what AxKit is designed to achieve. It's not complete yet
by any means. Join the list, start hacking and suggesting, and you'll
shape where it goes from here.
(with AxKit, association with different media devices from the standard
W3C list is automatic, and picking a stylesheet based on alternates is
just a plugin away). http://xml.sergeant.org/axkit/
--
<Matt/>
Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XML, Sybase and Oracle solutions
Email for training and consultancy availability.
http://sergeant.org http://xml.sergeant.org
