Hey, usually we don't use such methods like this with the try-catch if we know that it will fail the first time. I haven't checked it but i guess that code part is pretty old, which could be a reason the way it is. But sometimes its just necessary to work with exceptions so removing that will not guarantee that your application will behave the way you want in the future with firebug on.
> In my project I have used 399 classes and while debugging build-version > firebug only stops always at Instantiating DateField. Why do you need to debug the build version? That should not happen very often that you need to debug the build version. > It's clear, it is no error for normal users, there is a try-catch. > Is there a better way to initialize the class eg. with parameters that > prevent it? > > If it is safe, at startup the Class runs always into catch, wouldn't it > be better to test it additionally by an if? Sure there could be a better way to initialize it. As I said, I would not write the code the way it is. But the current amount of ideas to work on is just too big to check all code and remove stuff we would write different today. ;) But you may open a bug report and in time, we sure change that code. > Please, I do not want to seem petty, but I am relatively new to qooxdoo > and still not so sure you need to know. Don't worry. ;) Best, Martin ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
