Do you have any idea on what the time line is ? are we talking short term or long term
Well, the idea came up about two days ago. The hope is to figure out a way to do it soon (a week? something like that).
Part of the problem is notifying people when new things get posted to the list or something along those lines; ideas on this would be welcome.
It is a start, but think it should be a set of keywords, because different people need different starter bugs. Some want to get started with cplusplus while others might just need some with GUI (XUL etc)
I'd think the component the bug is in covers this part....
Agreed. The problem is how to organize it and how to link to it from where... I wrote some overview docs at some point, and I don't even think they're linked to from anywhere on the mozilla.org site, in the wake of the site redesign.
This should really be the easy part, stuff it in a wiki or something. Lets have some content before we start thinking about structure.
We HAVE content. We have somewhere on the order of 10 documents just on the layout engine. We have good documentation on strings, arrays, and hashtables. We have various XPCOM documents, RDF docs, security docs, uriloader documentation, etc, etc.
The problem is that none of this is very easy to find. "stuff it in a wiki" doesn't help find it.
Like http://www.mozilla.org/newlayout/doc/gecko-overview.htm ?Yes it could be something like that, perhaps it is a bit light on the actual text. It looks like something that was made to support a presentation but sadly the actual content of the
It was a presentation, yes. I'll look into writing a document based on those graphics.
- An overview of which XPCOM components/services are available and their APIs.
This would need to be organized somehow -- we have a LOT of such components/services.... Suggestions on how? This is really the most serious problem with the docs we have -- finding what you want is hard.
How about an simply list like
FileComponent: Performs local file access <link to api>
PreferenceComponent: Performs storage and retrieval of program prefereces <link to api>
This list would have hundreds (if not thousands) of items in it. I see 93 IDL files in xpcom/, and some of them define multiple interfaces... And these are just the core XPCOM layer. I see 809 IDL files in the tree if I exclude the DOM api and all of mailnews and editor. Just having a list won't cut it for this stuff -- it needs to be categorized somehow...
If someone can generate a list of docs involved (already nontrivial), this could probably be done.... I agree that it's worth doing.
How about an simply search of files in the cvs webpart ?
There's a lot of stuff on the website that's not docs. Most of the website, in fact. The website CVS is somewhere on the order of 60MB, last I checked...
-Boris _______________________________________________ mozilla-documentation mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-documentation
