Mar 302011
 

 

Here are today’s Wiki Wednesday articles! If you know about these topics, please try to find a few minutes to look over these articles that are marked as needing technical intervention and see if you can fix them up. You can do so either by logging into the wiki and editing the articles directly, or by emailing your notes, sample code, or feedback to mdnwiki@mozilla.org.

Contributors to Wiki Wednesday will get recognition in next week’s Wiki Wednesday announcement. Thanks in advance for your help!

JavaScript

Thanks to Jifeon and reneruiz for their contributions last week.

SpiderMonkey

Developing Mozilla

Thanks to Benjamin Smedberg for his contributions last week.

Extensions

Thanks to John J. Barton for his contributions last week.

XUL

XPCOM

Interfaces

Thanks to Kyle Huey for his contributions last week.

Plugins

Thanks to Benjamin Smedberg for his contributions last week.

CSS

SVG

Thanks to Jeremie Patonnier for contributing last week.

HTML

DOM

Thanks to BYK for contributing last week.

 Posted by at 4:13 PM
Mar 262011
 

Obviously, the main achievement for the week was a community-wide one: the delivery of Firefox 4 on March 22nd! That said, I did get a few things done this week:

  • Created a new bitly template that returns a short URL for the specified page on devmo. This is used by the Wiki Wednesday article list script to output short URLs for pasting into newsgroups.
  • Assorted article cleanup and other work. Very little new documentation this week though, sorry.
  • Arranged to get our staging server updated to the latest version of MindTouch in preparation for QA beginning testing so we can finally get upgraded, now that their plate is getting less crowded with releases of Firefox.
 Posted by at 11:41 PM
Mar 232011
 

Here are today’s Wiki Wednesday articles! If you know about these topics, please try to find a few minutes to look over these articles that are marked as needing technical intervention and see if you can fix them up. You can do so either by logging into the wiki and editing the articles directly, or by emailing your notes, sample code, or feedback to mdnwiki@mozilla.org.

Contributors to Wiki Wednesday will get recognition in next week’s Wiki Wednesday announcement. Thanks in advance for your help!

JavaScript

SpiderMonkey

Thanks to Dmandelin and cdleary for their contributions last week.

Developing Mozilla

Thanks to Neil Rashbrook for his contribution last week.

Extensions

XUL

XPCOM

Thanks to Benjamin Smedberg for his contribution last week.

Interfaces

Plugins

Thanks to mendicant for contributing last week.

CSS

SVG

HTML

DOM

Thanks to Neil Rashbrook for his contribution last week.

 Posted by at 4:35 PM
Mar 202011
 

With just days to go until we ship Firefox 4, work has gotten into that “everything is a little hard to categorize” place. That said, here are a few things that got done this past week:

  • Added a little text and code snippets for the unique window IDs added in Gecko 2.0.
  • Turns out our query for finding the dev-doc-needed/resolved bugs was leaving a few things out. Florian found that and now we’re using a revised query. I went through all the newly-discovered ones, fixing some of the documentation, noting others that were no longer in need of documentation, and removing the dev-doc-needed tag from some that were found to be invalid but never got untagged.
  • Tons more cleanup of documentation.
  • Had assorted meetings related to planning for the Kuma project (that is, the new wiki for MDN).
 Posted by at 3:03 AM
Mar 162011
 

Here are today’s Wiki Wednesday articles! If you know about these topics, please try to find a few minutes to look over these articles that are marked as needing technical intervention and see if you can fix them up. You can do so either by logging into the wiki and editing the articles directly, or by emailing your notes, sample code, or feedback to mdnwiki@mozilla.org.

Contributors to Wiki Wednesday will get recognition in next week’s Wiki Wednesday announcement. Thanks in advance for your help!

JavaScript

Thanks to BYK for contributing last week!

SpiderMonkey

Thanks to gal for contributing last week!

Developing Mozilla

Extensions

XUL

XPCOM

Thanks to jdm for contributing last week!

Interfaces

Plugins

CSS

Thanks to Greg Tyler for his contributions last week!

SVG

HTML

DOM

 Posted by at 7:51 PM
Mar 152011
 

I’ve been looking over the documentation as well as the bug lists, and it looks like we’ve reached the point at which the documentation is complete — for a generous definition of the term “complete.” That is to say that everything that impacts a significant number of people has been documented reasonably thoroughly. There are as of the moment I’m writing this post 18 bugs that are tagged with the dev-doc-needed keyword that are also resolved.

Of these 18 remaining items:

  • 3 are partially documented, with the rest of the work that needs to be done on hold pending some block or another being removed. However, they’re documented enough that people should be able to get their work done.
  • 2 are large issues (the creation of the new XrayWrapper to replace XPCNativeWrapper and the new Cocoa NPAPI event model) that affect a moderate number of people. I’ve been gathering notes to write about the XrayWrapper stuff and hope to start writing this week; the plugin stuff is a bigger problem and I’m not sure when that will get written up properly. Soon, I hope.
  • 9 items are actually left over from older releases. These are generally very obscure items that affect so few people that documenting them has not been important enough to get attention from anyone.
  • 1 (WebSockets) is on hold pending spec changes, and is not actually ready to document yet.
  • 3 items are relevant to Gecko 2.0 but are extremely limited in the number of people they effect and are complex enough that they have not gotten written up yet because of the combination of those two factors.

So we’re near the end of the road for this documentation cycle. It would be very helpful if you could take a look at the list and see if there’s anything there that you can help get documented — either by writing it, pointing out code samples, or answering questions that may have been asked and never answered in the bug comments. Or just drop me email if you know about the subject of the bug so I know to talk to you about it!

I know at least some of you are no longer cranking out code for Firefox 4, so you have time to help!

 Posted by at 2:24 AM
Mar 142011
 

A busy week in which lots of articles got a little bit of work, plus the following:

 Posted by at 1:32 PM
Mar 092011
 

Here are today’s Wiki Wednesday articles! If you know about these topics, please try to find a few minutes to look over these articles that are marked as needing technical intervention and see if you can fix them up. You can do so either by logging into the wiki and editing the articles directly, or by emailing your notes, sample code, or feedback to mdnwiki@mozilla.org.

Contributors to Wiki Wednesday will get recognition in next week’s Wiki Wednesday announcement. Thanks in advance for your help!

JavaScript

Thanks to last week’s contributor to the JavaScript documentation: Neil Rashbrook

SpiderMonkey

Developing Mozilla

Thanks to Neil Rashbrook for his contributions last week.

Extensions

XUL

XPCOM

Thanks to last week’s contributor: Neil Rashbrook.

Interfaces

Plugins

CSS

SVG

HTML

DOM

 Posted by at 3:55 PM
Mar 062011
 

As part of our ongoing effort to make our documentation more globally useful, instead of implying that our web content is Firefox specific, we’re going to start to get rid of our old “Requires Gecko X” banners at the tops of pages covering web standards in favor of compatibility tables. Some articles already have them, others don’t, but we’re going to start using them more.

This coming week, one of my tasks is going to be to try to create a MindTouch template that, given information about each browser or engine, will automatically lay out and generate a compatibility table. To do this, I’m going to make use of MindTouch’s support for named parameters, so that you can do something similar to this:

{{CompatTable(gecko:{version:”1.9.2″, note:”Was called -moz-foo before Gecko 2.0.”}, safari:{version:”4.0″, note:”Some notes.”}, ie:{version:8})}}

This would generate the table, automatically filling out any rows for unmentioned browsers with empty rows. For example, the table generated by the above template might do something like this:

Browser Version Available Notes
Chrome - -
Gecko 1.9.2 (Firefox 3.6) Was called -moz-foo before Gecko 2.0.
Internet Explorer 8
Opera - -
Safari 4.0 Some notes.

Notice that there are rows for Chrome and Opera even though they weren’t specified. This ensures that the tables site-wide will be consistently formatted. We can add new browsers to the table by simply adding them to the template, and updating articles at the appropriate times.

The main issues that need to be decided upon before actually writing this template:

  • Can we simply have a “webkit” version number and figure out which version of Chrome and Safari that applies to?
  • Can the same “webkit” version be used for mobile versions of Safari? I don’t think it can. Do any mobile versions of Safari have enough market share (and are different enough) to warrant mentioning explicitly, other than iOS?

By using named parameters, we can be much more flexible about leaving out bits of information, plus we can add more fields later without having to recode all past uses of the template. That said, if anyone has thoughts on additional information the template should initially be designed to support, please let me know.

 Posted by at 8:46 PM