Hello, We are at the point where we need to have extensive JS error logging in production for our web-app. I've seen that Qx already tackles this problem with a qx.event.GlobalError class.
However I played with it this morning (we're still under 1.0 but could update to 1.2.x if improvements have been made in this area), and I was not really able to do anything useful with it. The two points that bother me: 1) Is there an entry point for qx.io.remote.transport.Script._requestFinished() ? It would seem normal to have one, else every exception occuring on the return of a server request won't be handled. But from my tests, it seems there isn't. Should I manually add it ? (seems a bit strange) 2) Once I get the exception in the error handler, I was not able to do anything with it. I just wrote a very stupid a =b line on the source (where b is not defined). If I don't have an error handler defined, under FF this pops up in the Firebug console with useful information and the line of the error. If I activate the error handler, I get a qx.core.WindowError object, but it does not contain any useful info: toString() returns "", getLineNumber() returns 0 .... A global error handler is definitely something that is needed in a complex web-app and we really need to use it... but at this point I need help understanding how to make it work reasonably well. Jean-Noel PS: I read the Qx docs on this. ------------------------------------------------------------------------------ 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
