Kent Olsson schrieb:
Hi!
You mean that you will add it on top of the current transport layer.
Because I can not find it now.
Hej Kent,
Yes, we will do this in the future.
When a request is performed in
Transport_1.html the data comes in the data variable, which is converted
to a string.
No, this is not correct. The event is a QxDataEvent. To get the data
field attached we call getData(). The result of this is the QxResponse
object. This objects for example contains: getTextContent and
getXmlContent methods. There is nothing converted. This is just as the
native xmlhttp object returns the values.
How is this string meant to be parsed? By a DOM
parser??? :( or by a SAX parser ? :) I want the XML entities mapped into
variables.
I'm not sure if we are currently have this on our TODO. DOM or Sax
parsers are supported more or less by the todays browsers. I don't think
we need to implement this our own like google has done.
You talk about encode/decoder, but I can not find it. Is it
under development? What is your intention how it should be done?
I would like to do two things:
1. read keys and get their values
2. map widgets to data with an XML scheme as a carrier of the data
coming from a file or a database
I don't think there is a general solution for all users in preparing the
incoming data. I can think about some type of mime-type the user can
define for the response data. But there is currently no implementation
for this.
We would like to implement (integrated) json support first.
Sebastian
Kent
On Tue, 2006-03-07 at 09:59 +0100, Sebastian Werner wrote:
Kent Olsson schrieb:
Hej Sebastian!
What is your intention about mapping XML transferred data by QxTransport
to objects? How do you want it t be solved? I am talking about the
parsing itself.
I can see a class called QxData which has been deprecated. It has a
mapping method.
What exactly to you mean is currently missing? A mapping? I think we add
the encoder/decoder stuff on the top of our current transport layer.
Sebastian
Kent
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
