On Thursday 20 November 2003 07:43 am, Tod Harter wrote: > On Wednesday 19 November 2003 7:22 pm, Michael A Nachbaur wrote: > > 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.
Intriguing. Do you perhaps have any samples you would be able to show that illustrates this concept? Does the client-side application provide the "Controller" part of the framework? What is the result of the XSLT transform, a conventional web page rendered in a <xul:browser/> element, or plugged straight into a standard container element like a <tabpanel/> or <box> element? -- /* Michael A. Nachbaur <[EMAIL PROTECTED]> * http://nachbaur.com/pgpkey.asc */ Trin Tragula - for that was his name - was a dreamer, a thinker, speculative philosopher or, as his wife would have it, an idiot. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
