User:Waldo

  • Revision slug: User:Waldo
  • Revision title: User:Waldo
  • Revision id: 105686
  • Created:
  • Creator: Waldo
  • Is current revision? No
  • Comment irrelevant!

Revision Content

About Me

My name is Jeff Walden. My primary work within MDC is^H^Hshould be on the {{ Source("toolkit/components/help", "toolkit Help Viewer") }}. I also own and manage the Firefox Help viewer and documentation projects, and I've done a little work on the nascent Thunderbird Help -- take a look at our current progress and jump in and start making changes if you're interested in helping. I also do also other random stuff, such as working on E4X in the browser and writing an HTTP server in JavaScript (used in various Mozilla test suites and frameworks).

Within MDC I've been doing things in various areas -- I wrote the JS implementations of the Array extras added in JS 1.6 (I have implementations for lastIndexOf/indexOf which await the next Firefox point release, which fixes some minor bugs in each which I'm waiting for, so the articles are correct for what people will use). I also respond to questions in the JS reference and try to clarify parts when necessary, and I do other random things as time permits. In practice I probably also maintain the xpcshell unit test docs, although that's mostly because I've been the one making changes to the test harness recently.

Stuff In Progress

  • CXC migration has been "done" for ages; I just need time to actually step through the compilation steps and make sure everything actually works in Firefox 1.5. I've fixed all errata as well as numerous typos, and it's pretty much as good as it can be except for likely being in a non-working state.
  • nsCOMPtr, nsRefPtr, nsAutoPtr, etc. - I think I grok nsCOMPtr, but I've just been "forced" to learn about nsRefPtr via review comments, and given the paucity of documentation on it (what I've figured out is mostly from reading {{ Bug("104346") }} and one link from a comment within it about std::auto_ptr I think there needs to be something on MDC. I don't remember seeing up-to-date docs on nsCOMPtr, so that seems like something that needs doing as well at some point.
  • Whack Traversing an HTML table with JavaScript and DOM Interfaces with a huge style stick (maybe; it's enough work that it may be a better use of my time to do something else)

Important Links

Contact Me

  • Email - jwalden at mit dot edu

Stuff

  • CXC Style Reference - a work in progress
  • Stuff MDC needs:
    • An easy way to download it all (weekly exports?)
    • The start of a hierarchy for documenting the Mozilla code base - documentation by component is rather haphazard now, and if there were a framework I'd be interested in starting to work at filling out parts of it
      • (definitely being implemented slowly)

Revision Source

<h3 name="About_Me">About Me</h3>
<p>My name is Jeff Walden. My primary work within MDC is^H^Hshould be on the {{ Source("toolkit/components/help", "toolkit Help Viewer") }}. I also <a class="external" href="http://www.mozilla.org/projects/help-viewer/">own and manage the Firefox Help viewer and documentation projects</a>, and I've done a little work on the nascent Thunderbird Help -- take a look at <a class="external" href="http://wiki.mozilla.org/Thunderbird:Help_Documentation:Base">our current progress</a> and jump in and start making changes if you're interested in helping. I also do also other random stuff, such as working on E4X in the browser and writing an HTTP server in JavaScript (used in various Mozilla test suites and frameworks).
</p><p>Within MDC I've been doing things in various areas -- I wrote the JS implementations of the Array extras added in JS 1.6 (I have implementations for lastIndexOf/indexOf which await the next Firefox point release, which fixes some minor bugs in each which I'm waiting for, so the articles are correct for what people will use). I also respond to questions in the JS reference and try to clarify parts when necessary, and I do other random things as time permits. In practice I probably also maintain the xpcshell unit test docs, although that's mostly because I've been the one making changes to the test harness recently.
</p>
<h3 name="Stuff_In_Progress">Stuff In Progress</h3>
<ul><li><a href="en/Creating_XPCOM_Components">CXC</a> migration has been "done" for ages; I just need time to actually step through the compilation steps and make sure everything actually works in Firefox 1.5. I've fixed all errata as well as numerous typos, and it's pretty much as good as it can be except for likely being in a non-working state.
</li><li><a href="User:Waldo/Smart_Pointers_and_XPCOM">nsCOMPtr, nsRefPtr, nsAutoPtr, etc.</a> - I think I grok <code>nsCOMPtr</code>, but I've just been "forced" to learn about <code>nsRefPtr</code> via review comments, and given the paucity of documentation on it (what I've figured out is mostly from reading {{ Bug("104346") }} and one link from a comment within it about <code>std::auto_ptr</code> I think there needs to be something on MDC. I don't remember seeing up-to-date docs on nsCOMPtr, so that seems like something that needs doing as well at some point.
</li><li>Whack <a href="en/Traversing_an_HTML_table_with_JavaScript_and_DOM_Interfaces">Traversing an HTML table with JavaScript and DOM Interfaces</a> with a huge style stick (maybe; it's enough work that it may be a better use of my time to do something else)
</li></ul>
<h3 name="Important_Links">Important Links</h3>
<ul><li><a class="external" href="http://whereswalden.com/">y<sub>0</sub></a>
<ul><li>my blog when I (rarely) feel like it
</li></ul>
</li><li><a class="external" href="http://www.getfirefox.com/">Mozilla Firefox</a>
<ul><li>'nuff said
</li></ul>
</li></ul>
<h3 name="Contact_Me">Contact Me</h3>
<ul><li>Email - jwalden at mit dot edu
</li></ul>
<h3 name="Stuff">Stuff</h3>
<ul><li> <a href="User:Waldo/Creating_XPCOM_Components_d11n_Style">CXC Style Reference</a> - a work in progress
</li><li> Stuff MDC needs:
<ul><li> An easy way to download it all (weekly exports?)
</li><li>The start of a hierarchy for documenting the Mozilla code base - documentation by component is rather haphazard now, and if there were a framework I'd be interested in starting to work at filling out parts of it
<ul><li>(definitely being implemented slowly)
</li></ul>
</li></ul>
</li></ul>
Revert to this revision