On Wednesday 19 November 2003 7:22 pm, Michael A Nachbaur wrote:
> I've started transitioning my application to use a Mozilla XUL client
> application, installed using a download from the intranet website, that
> presents the user with a fat client interface to the same server-side
> intranet application.
>
> Mozilla has made a really big commitment to RDF for all manner of aspects
> of it's basic operations; tree views, templated XUL sections (for
> repeatable clusters of display elements), menus and so on can all be
> programmatically built using RDF as a datasource.
>
> The bummer about all this is I find it pretty hard to generate RDF using
> AxKit.  I ended up dropping down into a plain'ol mod_perl handler, and
> printed out the RDF tags manually.  My XUL application is still just a
> prototype, but I'd like to see this functionality merged into AxKit more
> before going whole-hog into it.
>
> So, anyway, to answer the question, I would like to see better support for
> outputting RDF in AxKit.  Perhaps I had better spit the RDF out as a result
> of an XSL transform, but somehow that never occurred to me before.

Interesting. I am trying a different tack. My client-side application is built 
by loading an initial page, which contains javascript logic which goes back 
to the server via XMLHttpRequest(), gets whatever data is required for the 
particular operation being performed (served back as raw XML by the server 
side), applies XSLT to it, and attaches the resulting UI to the DOM tree in 
whatever is designated as the content area for whatever enclosing UI element 
is holding this 'panel' or whatnot. XUL could certainly be incorporated in 
there, but basically what I have is a component and a corresponding XSLT to 
instantiate it. You can go back and forth to the server all day and there are 
no 'pages' being loaded. In fact the application becomes entirely a normal 
event-driven GUI, albeit with some javascript glue logic. 
-- 
Tod Harter
Giant Electronic Brain
http://www.giantelectronicbrain.com


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to