Hi Steven, In order not to duplicate work already done, you should carefully look at http://mozilla.org/docs/dom and http://mozilla.org/docs/dom/contribute/doc.html. We also already have a reference on the most important objects. It is very detailed and imho we should work on extending that one. It can be found at http://mozilla.org/docs/dom/domref. Netscape Developer pages (developer.netscape.com) also have their own reference with all the properties and methods supported by all html elements. However that one is auto-generated. It can be found at http://developer.netscape.com/evangelism/docs/technotes/xref/dom-html-element/. All in all, please make sure you don't duplicate the work when working in that area.
Feel free to work on anything else you'd like or to contact the owner of the DOM reference ([EMAIL PROTECTED]) if you would like to help him extend that reference. Thanks, -Fabian. Steven T. Hatton wrote: > I am not a tech writer! However, I am interested in doing a bit of > outlining of the objects and methods of Mozilla's JavaScript > environment. My first inclination is to simply dump the objects to > screen as you can see done in this page: > > http://members.bellatlantic.net/~hattons/jsExplorer/htdocs/jsExplorer.html > > NOTE WELL: That page is subject to change at anytime and is not > guaranteed to be available in the future. > > After the object is dumped I figure the thing to do is go through each > member and determine how much the previous Client Side JavaScript > documentation covers, as well as the differences between the current > characteristics of the members and the older versions. Much of the > material should already exist in the older documentation, so the real > task seems to be to identify the new features and modify the existing > documentation to correspond with the current reality. > > The first thing that came to mind when I considered this task was the > value of having a DTD similar to DocBook. Does such a thing exist? > > TIA, > > Steven >
