Group items tagged

When used effectively, JavaScript debuggers help find and squash errors in your JavaScript code. To become an advanced JavaScript debugger, you'll need to know about the debuggers available to you, the typical JavaScript debugging workflow, and code requirements for effective debugging. In this article, we'll discuss advanced debugging techniques for diagnosing and treating bugs using a sample web application.

At the start of this year, I sat down to write the "Errors and Debugging" chapter of Simply JavaScript. I cracked my fingers, dove into the landscape of JavaScript debugging tools, and emerged very disappointed several hours later. At the time, Firefox was the only browser with a JavaScript debugging tool worth writing about: Firebug. Less than a year later, the landscape has changed dramatically. Every major browser has introduced new development tools that make it easier to diagnose problems with your HTML, CSS, and JavaScript code right inside the browser in question. But can any of these tools stack up against the slick and effortlessly powerful tools provided by Firebug? Let's take a look.

" From time to time I need to debug OAuth-protected APIs, checking response headers and examining XML and JSON payloads. curl generally rocks for this sort of thing, but when the APIs in question are protected with OAuth, things break down. Likewise for benchmarking (ab, httperf, etc.) and exploration-isn't it nice to browse APIs that return XML in Firefox? This needn't to be the case. Enter oauth-proxy This is why I wrote oauth-proxy. It does what it says on the tin: it acts a proxy server that transparently adds OAuth headers to requests."

With proper mark-up/logic separation, a POJO data model, and a refreshing lack of XML, Apache Wicket makes developing web-apps simple and enjoyable again. Swap the boilerplate, complex debugging and brittle code for powerful, reusable components written w

"Build engaging, cross-platform rich Internet applications Flex is a highly productive, free, open source framework for building expressive web applications that deploy consistently on all major browsers, desktops, and operating systems by leveraging the Adobe® Flash® Player and Adobe AIR® runtimes. While Flex applications can be built using only the free Flex SDK, Adobe Flash Builder™ (formerly Adobe Flex® Builder™) software can accelerate development through features like intelligent coding, interactive step-through debugging, and visual design of the user interface layout."

IAR Embedded Workbench for ARM is an integrated development environment (IDE) designed for building and debugging embedded applications for the ARM microprocessor. It includes a C/C++ compiler able to achieve a high level of optimization, thus generating a very compact and efficient FLASH/PROMable code.

The first point when you need one, the USBMULTILINK in combination with the one chip Berg bug and debug interface on Freescale's microcontrollers provides all the functionalities associated with an in circuit emulator at a fraction of the cost.

The idea of JDojo is to bring JavaScript and Dojo to Java. To achieve this, JDojo provides Java stubs for existing Dojo and JavaScript types a compiler participant to the Eclipse Java compiler that emits JavaScript files for each Java file compiled The programmer does not program against the Java JDK classes, but against Dojo and JavaScript stubs that JDojo provides. The compiler participant only allows a subset of the existing JDK classes and also limits the Java language constructs that can be used. To support important features that exist in JavaScript but are not available in Java, JDojo provides Java annotations that the programmer can use to instruct the compiler how to translate code. While the compiler still produces class files, what is of interest is the JavaScript code. Only the generated JavaScript code is executable, the Java code is not. Contrary to Java-JavaScript cross compilers, JDojo does not add anything on top of the JavaScript and Dojo types. JDojo programmers program against the DOM, Dojo widget and other existing Dojo classes the same way as they would do it when programming JavaScript. Therefore, the Java code a JDojo programmer writes looks very similar to the JavaScript code he would have written. However, the programmer now can take advantage of a typed programming environment and benefit from the Eclipse Java Tooling. The translator produces JavaScript that looks as similar as possible to the Java code (without the types), and matches what a JavaScript programmer would have written. This is important when executing and debugging the generated JavaScript; it is still easy to understand the JavaScript code and map a bug back to the Java code. JDojo also fits nicely in the existing Jazz web bundles. JDojo code is placed in a new Java source folder, while the generated JavaScript is inserted in 'resources' folder that also holds existing JavaScript code. To use existing JavaScript code in JDojo, 'Stub' classes can be added, containing only th