Thanks. Another question. The other framework I used allowed me to set an
attribute of an object, and it would be marked as unsaved. I could then call a
save method on the object and it would collect all unsaved attributes along
with the id number, recursively down through attributes that were sub-objects,
and put it all into a json object that was sent to the server and persisted.
The server would respond and the unsaved attributes were marked as saved.
How would this sort of thing be done with qooxdoo? Is there built-in
functionality for it?
Jeff
On Oct 17, 2012, at 12:02 AM, Martin Wittemann <[email protected]>
wrote:
> Hey,
> we do have a JSON marshaler [1] which would take care of such transormations.
> This marshaler does use implicitly created classes for each object. So in the
> given sample, it would create a class offering the properties id, name and
> father. Based on that class, it would create an instance of person #25. As
> soon as the marshaler sees the object stored as father, it checks for the
> properties and will use the same class as these are the same properties.
> In short, this will work out of the box.
> Regards,
> Martin
>
> [1]
> http://demo.qooxdoo.org/current/apiviewer/#qx.data.marshal.Json~createModel
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
