[dentaku-devel] Client architectural considerations

[Brian T. <to...@bi...>]

I really like the feel of having a fat client.  And there definitely =
needs to
be a HTML client.  So I am considering using <stxx/>, which basically =
allows
the view to be completely XML driven.  It's a bit of extra work on the =
front
end, but I've done it before with a smaller project and am comfortable =
using
that code to get the transforms working within a day or so. =20

The nice thing about using XML everywhere is that the core reporting =
engine
can just cook XML, then send it off to the client for rendering, whether =
the
client is a fat client running standalone, a web application that is =
going to
transform it into HTML or PDF using <stxx/> or some other application =
type
that requires some other format. =20

What I am concerned about is my XSL skills... they are good enough for
government work, but maybe not passable for a system as complex as this. =
 Are
there any takers for doing reports in XSL?  Since the HTML table =
generation
is done in Struts Tiles, I don't think there will be a need for the =
entire UI
to be done this way, just the reports that fit into the tiles.  And I =
would
like to get some simple reports going as proof-of-concept for the =
overall
architecture ASAP.  I don't think the reports need to be anything but a =
basic
format text dump to start with.=20

If you have any XSL skills and would like to join, please drop me a note =
off
or on list!

Brian