The problem is related not to XUL. As Rick Marshall has stated, XUL is a user interface language (hence the acronym), designed to bring a heavier weight XML-based UI definition/layout language to the client. The client then takes on more of the heavy lifting responsibility, leaving the calls back to the server, mainly, for data requests.
That said, there does exist the ability to build a smarter UI such that the need to post data from an HTML form (< keyword) back to the server is, more or less anyway, replaced by newer, more flexible technologies (like XML/XSLT on the client, or XML sent as a payload using XmlHttpRequest()) in which that same data can then be used in a format that is easier to work with than that of the server side Form object that is pulled out of the request stream. The server (although XForms, the original replacement for HTML forms, can be integrated with an XForms aware server and as such allow the ability to write less code, to perform the same level of processing on the server, to then send back to the client for further procssing and rendering) doesn't know what to do with any of the other stuff (if any has been sent at all... doubtful, but possible... kinda) so it doesnt.
If you need to extract the data that is bound to the XUL document structure, and then send this data as part of a payload back to the server, then you need to do so using either the XmlHttpRequest object, or stick it inside of a hidden HTML text box and send it along for the ride when the form is submitted to then serialize into an XML stream (if thats what you have packed it up as) or process in some sort of server side text processing technology, Regular Expressions being the more likely candidate to be available on any given server.
Theres more work to do on the client for sure. But the benefit to your client in terms of performance, and to your server in terms of taking a significant chunk of its load and processing this instead on the client, overall, is a MUCH more desirable approach.
On 2/19/06, Rashmi . <[EMAIL PROTECTED]> wrote:
I tried embedding html form tags, but when the form is submitted only the values stored in the html input tags get submitted, the values entered in XUL input does not get submitted. This is a big problem for me.
I feel that XUL is better than AJAX but, why does XUL not submit form data to the back end just like how HTML does?
Tei < [EMAIL PROTECTED]> wrote:1) AJAX, the good one.
2) embed html tags ,may work
think in the application level. one abstraction layer up.--
On 2/19/06, Rashmi . wrote:
> Hello,
>
> I am trying to use XUL for my website's administration module. I was able to
> implement a simple example where I show a text box and a button.
>
> Then I tried to find out information on how to submit what is entered in the
> text box to the business layer and eventually to the database.
>
> I researched for 2 days on the internet regarding this, but it looks like
> there is no straight forward way to submit a forms data when the web page is
> built using XUL.
>
> Is this true?
>
>
> Clearly I don't completely understand the purpose of XUL. From what I have
> read so far, it seems like XUL is only suited for rendering content and not
> for saving user entered data.
>
> Please let me know what XUL can and cannot do.
>
> I am really looking forward to use XUL to build my website, but I need to
> know if I can use XUL to submit form data first.
>
> -Thank you
> Rashmi
>
Oscar Vives
--------------------------------------------------------------------
Consultor de Software Libre
www.servicios-dpi.com
Telf 645 167 472
[EMAIL PROTECTED]
--
<M:D/>
M. David Peterson
http://www.xsltblog.com/
