"Fabian Guisset" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> JavaScript in an interesting example. In Mozilla we have two
> implementations of it: Rhino and spidermonkey. One is written in Java,
> the other in C. The current website separates them into
> mozilla.org/spidermonkey and mozilla.org/rhino, linked from
> mozilla.org/js. I argue that neither spidermonkey nor rhino are
> products. They are technologies, created to be embedded in larger
> structures to form a usable software. Now maybe we could have
> /dev/tech/js which links to /dev/tech/spidermonkey and /dev/tech/rhino.
> It would be interesting to have the opinion of a js person on this.
Hey, that's me:)
Let me tell you my opinion of what I have been listening to in this thread.
You all have been splitting hairs on categorizing where these belong, but
the real issue is your target audience. (this does apply to the quote
above).
I see 4 groups of people who will be going to these pages.
1) C++ and other developers who want to join Mozilla's development team and
need to have references on how things work at a very low level. (lets just
call this group "mozilla/dev")
2) Software developers who wish to "re-use" Mozilla's technologies within
their own applications. (lets just call this group "mozilla/tech")
3) Web page developers. (lets just call this group "mozilla/web")
4) Mozilla browser end user's. (lets just call this group "mozilla/user")
I feel that ALL of the site should be structured (not necessarily the URI's,
but at least the web links) so that each of the above 4 types of people can
quickly get to what they need.
Now, as a JS person, I do not care whether the JS engine is SpiderMonkey or
Rhino (other than the differences to the properties and methods available to
the JS programmer and which browser this is the case). Bringing up these to
the JS programmer is just confusing the issue. We don't care!
So, my opinion is that you should have relevant documentation available in 3
groups, under mozilla/dev for those who wish to help in it's development,
mozilla/tech for those who wish to embed the engine in their own product,
and mozilla/web for the web page developer.
Under this scheme of course you need to separate the content into the three
categories with cross-links to relevant information that is under the other
categories.
Jeff Yates
http://www.pbwizard.com
