The good thing about wiki's are they are easily updated, so I think it would be good for a kind of catalog pages of the documentation. It would be quick to make ad-hoc overview pages.
Write up some ad-hoc overview pages, and I'll check them in. If that's all we want it for, it's not worth the trouble of setting up a wiki.
Well I actually allready setup a wiki on my personal server http://server.lynggaard.org/JSPWiki/
I will try an use this as an playground until we can find some common ground of how to structure it, and then we can move it to Mozilla.org
NOTE: Im just finishing the setup, from tommorrow THIS WILL BE OPEN TO ALL TO CONTRIBUTE!!
Well, lets start by getting the list, then lets sort it and put it in categories.
find . -name "*.idl" -o \( \( -name "mailnews" -o -name "dom" -o -name "editor" \) -prune \) | grep idl
Lets coordinate this with Neil Deakin, from his post it looks like somehting is on the ways
All apis that are not internal to a module are defined in IDL files,
basically... (there are some exceptions like unicode converters, and I think we should consider fixing those....)
Fixing how
Are actual API should really be some sort of extract of the IDL files, like doxygen, javadoc or the like.
Exactly. Most of the IDL files are incredibly poorly documented, though. And a lot don't clearly say what the thing does and how you would use it.
None should really say how you get one, since that's not part of the API.
how I get one ? Im not sure what you mean...
I was perhaps assuming that the content was somehow structured so that one could overcome it by looking at a minority of subfolders.Maybe it was a bad assumption..
It's very loosely structured, really.... Content is all over and just linked to from a central spot (in theory).
:-( _______________________________________________ mozilla-documentation mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-documentation
