| Possible Suggestions for Tools [message #764628] |
Mon, 12 December 2011 10:00  |
Eclipse User |
|
|
|
I'd like to throw out a couple of ideas for tooling enhancements and see what the community thinks. When I get a chance, I'll RFE them.
First, does anybody see the need for a stack trace capability? With the Infobus and nested widgets, sometimes it just gets difficult to figure out who triggered what. I'd love to be able to walk up the chain and see what happened and in JavaScript that's just not very easy.
Second, how about some conditional generation? I'd love to be able to flip a generation-time switch and add or remove code (especially logging). A simple IF_DEFINED would be enough for me, but I'd love to hear what others think.
Joe
|
|
|
|
| Re: Possible Suggestions for Tools [message #764685 is a reply to message #764680] |
Mon, 12 December 2011 12:04  |
| Eclipse User |
|
|
|
Agreed. I just spent several days tracking down a timing issue and only did it by basically putting my own logging on every function and my own JS stack trace. Both are very clunky and the stack in particular is fragile, and both will have to be removed for deployment. And since I don't want to lose the code, what I do is go in and comment out every line. Not bad for a couple of modules. Not fun for a large number.
I am tempted (TEMPTED, mind you) to write a tool that will spin through code and selectively comment or uncomment code (probably based on the previous line of code having a specially formatted comment).
But conditional code perhaps based on definitions set in the deployment descriptor (and alternately triggered by source-code annotations) would be most awesome.
|
|
|
Powered by
FUDForum. Page generated in 0.04145 seconds
Home