I never said the back-end was complicated. In fact, I pointed out that I've written THREE different back-end "servers" and each of them was TRIVIAL-- the most recent of which was the most trivial of all. What I DID say seemed complicated and absurd was the machinations required to get data packaged up and ready to GO to the back-end. As Jim and I were discussing, it should be really easy-- a JSON object or something similar. It SHOULDN'T take three whole days to figure out how to add extra parameters or turn a model into a regular array or to have to hoist it into being an object again in order to get it to the back-end. But that's what happened. Everything that seemed like it should be simple and obvious turned out to be complicated and obscure. And in fact, I wasn't able to reach a satisfactory conclusion without digging through the bowels of the framework code to figure out how they pick apart the object. If any of that is documented in the manual someplace, I've completely missed it.
-- View this message in context: http://qooxdoo.678.n2.nabble.com/Need-help-with-Models-please-tp7581630p7581687.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
