Hey, in general a good idea but this error is thrown by qx.core.Object using the bootstraps error method. So using the stacktrace there would bring in a new dependency (I guess) which is not good at that level.
Best, Martin Am 21.09.2010 um 11:06 schrieb panyasan: > > Hi Martin, > > thanks for the clarification. But wouldn't it make more sense in theses > cases to automatically print a qooxdoo-stacktrace using qx.dev.StackTrace > (I don't remember the correct class name) instead of letting the error be > handled by the javascript engine (which produces these unusable stack > traces)? Maybe this could be made configurable (or is already?) > > Thanks, > > Christian > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/qooxdoo-property-system-and-debugging-tp5547118p5553814.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 ------------------------------------------------------------------------------ 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
