Venkman: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(3 intermediate revisions by 3 users not shown)
Line 10: Line 10:
''<br/>Todo: add more bug numbers!''
''<br/>Todo: add more bug numbers!''
=== Architecture ===
=== Architecture ===
General changes needed to make Venkman work with current development, to ease maintenance and attracting developers.
General changes have been made to make Venkman work with current development, to ease maintenance and attracting developers. It now lives in HG ([http://hg.mozilla.org/venkman/ hg.mozilla.org/venkman/]). Work on the build system is still progressing.
* Venkman should adhere to the common Mozilla build system (Makefile.in, jar.mn, install.rdf, etc.).
* Venkman should reside in its own hg repository (currently, it still lives in the to-be-abandoned CVS trunk aka as Gecko 1.9.0.x).
These two points should probably be done in close relation: do the move into Hg, then renew build structure there. CVS version numbers could continue 0.9.xx and keep backwards compatibility, while Hg version could become 0.10.yy and may break compatibility with pre-1.9 code.  


The meta {{bug|141097}} ("Release Venkman 1.0") is still valid, but needs to be changed to reflect this new reality.
The meta {{bug|141097}} ("Release Venkman 1.0") is still valid, but needs to be changed to reflect the current state of affairs.


=== Important Bugs ===
=== Important Bugs ===
Line 32: Line 29:
* ...
* ...


== Related Links ==
== Related Links ==
* Alex Vincent started a [http://groups.google.com/group/mozilla.dev.apps.js-debugger/browse_frm/thread/422b6ee58abc0701/061a3a638846405f?tvc=1&q=+Venkman+planning+for+Gecko+1.9#061a3a638846405f thread about Venkman's future] with focus on Gecko 1.9 in the Mozilla newsgroup mozilla.dev.apps.js-debugger in 2007, but it didn't really take off.
* Alex Vincent made a fresh attempt with his blog post on [http://weblogs.mozillazine.org/weirdal/archives/019539.html Gecko 1.9.1, TraceMonkey and Venkman?] recently.


*Alex Vincent started a [http://groups.google.com/group/mozilla.dev.apps.js-debugger/browse_frm/thread/422b6ee58abc0701/061a3a638846405f?tvc=1&q=+Venkman+planning+for+Gecko+1.9#061a3a638846405f thread about Venkman's future] with focus on Gecko 1.9 in the Mozilla newsgroup mozilla.dev.apps.js-debugger in 2007, but it didn't really take off.
*Alex Vincent made a fresh attempt with his blog post on [http://weblogs.mozillazine.org/weirdal/archives/019539.html Gecko 1.9.1, TraceMonkey and Venkman?] recently.
*'''END&nbsp;OF&nbsp;LIFE:''' &nbsp;Alex Vincent has blogged yet again, suggesting that Venkman cannot be supported for much longer, and should be replaced: [[http://weblogs.mozillazine.org/weirdal/archives/020974.html R.I.P., Venkman]]
* A comparison of Venkman and Firebug features lives here:  [https://wiki.mozilla.org/Venkman/Firebug_Comparison]


<small>''Page maintained by [mailto:mnyromyr@tprac.de Karsten Düsterloh]''</small>.
<br> <small>''Page maintained by [mailto:mnyromyr@tprac.de Karsten Düsterloh]''</small>.

Latest revision as of 03:52, 27 May 2011

Introduction

Venkman is Mozilla's cross platform JavaScript Debugger, visit devmo for a comprehensive overview. Alas, it's currently in a sad state of hibernation - its homepage is out of sync with reality since 2005! The current version on amo is 0.9.87.4, though.

Despite efforts for a web-related debugger for Firefox (named Firebug), Venkman still has its place as a cross-platform, cross-application (Firefox, SeaMonkey, Thunderbird, Netscape, etc.) debugging tool for both web and Mozilla chrome development.

Unfortunately, Venkman's codebase hasn't kept pace with current development of the Mozilla ecosystem, so action is badly required to keep Venkman alive. This page aims at helping in coordinating this.

Tasks

The stuff to be done can be splitted in three major groups:
Todo: add more bug numbers!

Architecture

General changes have been made to make Venkman work with current development, to ease maintenance and attracting developers. It now lives in HG (hg.mozilla.org/venkman/). Work on the build system is still progressing.

The meta bug 141097 ("Release Venkman 1.0") is still valid, but needs to be changed to reflect the current state of affairs.

Important Bugs

Bugs which break Venkman or make it hard to use.

  • bug 342590 – Make --enable-extensions=venkman work for XULRunner
  • bug 424493 - Copying native code stack frames generates errors
  • bug 446120 - Watches crash when expanding 2 levels and the values change
  • bug 449766 - Variable Value remains "undefined" when stopped in a debugger before initialization of the variable (JSD bug, seen in both Vnk and Firebug).
  • bug 452288 - Allow ignoring NS_ERROR_NO_INTERFACE errors
  • Venkman doesn't recognise let statements
  • ...

Enhancements

  • Better keyboard experience, eg. shortcut keys for (un)setting breakpoints, etc. pp.
  • Source code tooltips with variable values.
  • ...

Related Links

  • Alex Vincent started a thread about Venkman's future with focus on Gecko 1.9 in the Mozilla newsgroup mozilla.dev.apps.js-debugger in 2007, but it didn't really take off.
  • Alex Vincent made a fresh attempt with his blog post on Gecko 1.9.1, TraceMonkey and Venkman? recently.
  • END OF LIFE:  Alex Vincent has blogged yet again, suggesting that Venkman cannot be supported for much longer, and should be replaced: [R.I.P., Venkman]
  • A comparison of Venkman and Firebug features lives here: [1]


Page maintained by Karsten Düsterloh.