Thanks for responding carise! I was beginning to wonder where/if there was any active Gears community around!
I have used MS Script Debugger in the past - maybe time to try again. With IE8 I've read the dev tools are improved. I downloaded the dev channel version of Chrome today. They have added the profile and script tabs to their version of webkit's inspector. The db tab is still missing, :(. Even in Chrome debugging worker threads does not seems possible. However, this dev channel version of Chrome does seem more stable for debugging gears code than FF. Although I do still experience infrequent crashes (not unexpected in a dev version). Also the current version of chrome 3 dev's Script tab seems to pile up multiple versions of my js files. So if I reload a page 3 times, I will have three copies of each js file loaded by the page. If Ive updated the js file on my server, I seem to have old and new versions mixed together. Also don't seem to be able to disable a breakpoint as they tend to disappear - easy workaround is to close the web inspector which causes all the breakpoints to clear. I was surprised to see the version of gears available for FF3 is more recent than the version supported within Chrome 3 dev. On Jun 26, 2:29 pm, carise <[email protected]> wrote: > I developed my project on IE + IE script debugger (the one that comes > with MS Office or whatever). And a lot of alert statements. Also I > found that using SQLiteManager (FF extension) helped. However, I never > really played with breakpoints and stuff... though I admit that my > worker threads are pretty simplistic and I found it very difficult to > debug the worker. I did minimal debugging by sending messages from the > worker... which isn't the best solution, but it helped somewhat. > > On Jun 25, 1:54 pm, skye <[email protected]> wrote: > > > > > What do people out there currently use to develop with Gears? I've > > been trying FF 3.0.11 with Firebug, however it is very fragile. > > Inspecting a Gear object or using the DOM tab of Firebug pretty > > consistently causes FF to completely bomb. If two worker threads send > > a message while I am paused at a breakpoint FF pretty consistently > > blows up. Setting and honoring a breakpoint in worker code seems > > impossible as the worker is not attached to the DOM (I am guessing). > > > Do others have these issues? If not, what are your tricks, tips? I > > am open to developing in Chrome 2 however the lack of a real debugger > > is a major hurdle.
