Looking forward to the TideSDK 1.3 release. I've extended the sample app provided but I'm unable to figure out how to breakpoint my code and step through it for debugging purposes. Of course when running in the browser I can use chrome debugging tools but in the Tide sandbox how do I accomplish this?
One way to achieve this is to open up the inspector inside the app and use the webkit inspector to breakpoint and step through your source code.
Related
Fellows I am having a huge trouble with an project in Ionic and I want to use a dedugger in order to solve more effficiently.
Do you know how to use a debuggger in order to achieve that;
If the answer is the firefox debugger how I will use it in order to debug my application?
For Mozilla Firefox, the following are different ways to set a breakpoint within the JavaScript code in the debugger.
For Google Chrome, since this is the JavaScript you can also use Debugging with breakpoints (Debugging JavaScript). This will help you a lot.
More about debugging: How to Properly Debug Your Ionic Application.
When I debug a Cordova app what I constantly do is step through its code inside Chrome's WebInspector. In order to be able to do this, however, I have to wait for the device to become ready in chrome://inspect/#devices (only then can I click on the appearing link for the started app). But if I do this the inspector will not halt on breakpoints if I am not quick enough. How do experienced Cordova developer tackle this issue?
Additionally to frank's comment I just found GapDebug which offers instant debug and, thus, comes close to what I deserve.
Are there any tools/methods for debugging phonegap Blackberry(5,6,7) app . Presently am using Alert for debugging which is very tedious .
Since you are using PhoneGap, its always better to view/debug you app on a webkit browser like Chrome/Safari. Also try Ripple emulator from BlackBerry which is the best web emulator for mobile devices: https://chrome.google.com/webstore/detail/ripple-emulator-beta/geelfhphabnejjhdalkjhgipohgpdnoc?hl=en
Since you are developing a web app, and as far as I know there's no "official" IDE for BlackBerry Webworks, this question is not BB or Phonegap specific. You are just asking how to debug JavaScript. There are a lot of questions in SO about this, just run a search. I'll give you my two cents:
As the JavaScript code runs in a browser, you need to debug in the browser. Most browsers have built-in debugger or extensions. For Firefox I'd reccomend Firebug extension, in Chrome the built-in debugger is pretty good. I can't tell about IE but I think there's something similar.
If you need to debug on device, then use console instead of alert.
Finally, have a look at WebStorm. Probably the best IDE for JavaScript right now, but you need to purchase a license. It allows you to attach to the browser debugger and debug in the IDE.
I notice for chrome I can load an extension I'm developing into it without packaging it or anything. I'm wondering is this possible to do on FireFox? If not, what's the least painful way to develop and test at the same time? I'm using linux.
Yes, I believe you can perform what is a called a "chrome reload".
http://kb.mozillazine.org/Getting_started_with_extension_development#Development_cycle
I have a webapp which is tested by selenium. Everything works well: writing tests in java, setting breakpoints in my webapp through firebug.
unfortunately I am not able to debug the user-extensions.js it self: After starting the java-test, two firefox windows are opened. One holds the webapp to test, the other one holds the data-flow which uses the user-extensions.
How can I debug the user-extensions?
It seems that it is not possible. I made a workaround and switched the functions to my webapp to debug them there.
It really depends on the browser you're using. I've been able to debug user-extensions using Chrome. In the control Window, you need to right-click and then view the window as a tab. Once you do that, you can activate the developer tools for the control window, which will include the JavaScript debugger.
It's possibile using the Venkman debugger (a separate Firefox extension) and Firefox up until version 32, and that's quite a precious combination.
With Firefox 33 and later, Venkman is broken by api changes, and the native debugger unluckily doesn't allow to debug xul based extensions.