Hi,

In article <[email protected]>,
           rfreedman<[email protected]> 
wrote:
> I reworked the xsl stylesheet.
> It produces the same output as before, but is much more efficient.
> Note that the forEach construct is very expensive, and generally
> frowned upon.
>
> I attached the new stylesheet, as well as some python code to do the
> transform.
> I think that you should consider doing the transform server-side,
> instead of sending the xml to the browser with a stylesheet reference -
> not all browsers handle that well. The only issue here is that you have
> to install libxml2, and I'm not sure if that's available on Windows or
> not...
>
> As far as the actual output, I think it might be a good idea to put out
> divs instead of tables, and put css classes on the divs. That way, you
> could skin it using css, and provide different css according to the
> user's choice.
> I'll work on that as I can over the next couple of days.

Thanks for that. This stylesheet was done pure to ensure that the data was
there and could be used via XSLT. It's by no means indicative of the actual
output I want.

As I said, my knowledge of XSLT is *very* limited, and when I started the
project a year or so ago I did ask for help on that side of things. I'd be
more than happy for you (or indeed a group of people) to 'take the reins' on
the XSLT side while I concentrate on the retrieval script.

Thanks for the input.

Andy

_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss

Reply via email to