Hi list, one cool aspect of qooxdoo is all the magic behind the property system: the automatic setter/getter, validation and value application support etc. The downside to the convenience this all brings is that the machinery behind is quite complex and sometimes makes debugging difficult if something goes wrong, especially when callbacks are involved. Take this example of a firebug console output:
http://qooxdoo.678.n2.nabble.com/file/n5547118/Bild_10.png I am informed about an error "No such property: category". The stack trace, however, reveales very little. In fact, the location where the error is thrown according to the trace seems to have nothing to do with the actual error. I assume this has to do with the automatic wrapping and unwrapping of functions that are the base of the property system. I have not clue where and when the error really occurs, and have to work with a log or console.log() statements to find out. Is there anything that can be done to make debugging easier in this respect? Thanks, Christian -- View this message in context: http://qooxdoo.678.n2.nabble.com/qooxdoo-property-system-and-debugging-tp5547118p5547118.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
