Hi Martin, The current system supports serializing QX objects to a JSON string notation using the ISO standard for dates (qx.util.Json). But serializing in the opposite direction - a JSON string notation into QX objects (qx.data.marshal.Json) does not attempt to process string literals in the ISO Date notation (EG "2011-02-19T04:49:14.534Z").
I think it would be a good thing to allow for this. My thoughts are to include a delegate interface to qx.data.marshal.Json that allows for extending the toModel() method. That would allow for a default delegate to parse strings for date notations and also allow for any other processing similar to the data binding delegates. -- View this message in context: http://qooxdoo.678.n2.nabble.com/JSON-Date-format-tp6047708p6050404.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Index, Search & Analyze Logs and other IT data in Real-Time with Splunk Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. Free Software Download: http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
