I made a sample of new JS Ref

[potappo]

hi, all.
I made a sample of new JS Ref that considers previous posts in this ML.
http://developer.mozilla.org/en/docs/User:Potappo:Core_JavaScript_1.5_Reference:Global_Objects
http://developer.mozilla.org/en/docs/User:Potappo:Core_JavaScript_1.5_Reference:Global_Objects:RegExp_%28members%29
http://developer.mozilla.org/en/docs/User:Potappo:Core_JavaScript_1.5_Reference:Global_Objects:RegExp_%28constructor%29
In this idea, current RegExp page (edited by Sevenspade) moves
RegExp (constructor) and RegExp redirects to RegExp (members).
By using Template:JSMembersInc, creating, maintenance, and
translation of members pages is easy.
http://developer.mozilla.org/en/docs/Template:JSMembersInc
Please comment on my idea.
regards.
--
potappo
MDC Japanese Translation Team

[John J. Barton]

potappo wrote:
> hi, all.
> I made a sample of new JS Ref that considers previous posts in this ML.
> http://developer.mozilla.org/en/docs/User:Potappo:Core_JavaScript_1.5_Reference:Global_Objects

Let the page be about the objects, not about confusion. Rather than:
--------
The term "global objects" here is not to be confused with the global
object. Here, global objects refer to objects in the global scope. The
global object itself can be accessed by this in the global scope.

Standard global objects
--------
How about
++++++++
These language-defined objects are in global scope.

Javascript 1.5 Defined Objects
++++++++

> http://developer.mozilla.org/en/docs/User:Potappo:Core_JavaScript_1.5_Reference:Global_Objects:RegExp_%28members%29
> http://developer.mozilla.org/en/docs/User:Potappo:Core_JavaScript_1.5_Reference:Global_Objects:RegExp_%28constructor%29

99% of the time, the useful information in this page for developers
amounts to two lines of text on the whole UI. Put everything I want to
know about using RegExp on one page. Then I only have to load one page.
It will be the top hit on searches so I don't have to guess which page
to try. I don't have to wonder if I've read all there is about RegExp
but I have.

The links to related pages (which I guess is what you were really asking
for feedback on) look great.

John.

[potappo]

John J. Barton <johnj...@johnjbarton.com> wrote:
> potappo wrote:
> > hi, all.
> > I made a sample of new JS Ref that considers previous posts in this ML.
> > http://developer.mozilla.org/en/docs/User:Potappo:Core_JavaScript_1.5_Reference:Global_Objects
>
> Let the page be about the objects, not about confusion. Rather than:
> --------
> The term "global objects" here is not to be confused with the global
> object. Here, global objects refer to objects in the global scope. The

- > global object itself can be accessed by this in the global scope.

>
> Standard global objects
> --------
> How about
> ++++++++
> These language-defined objects are in global scope.
>
> Javascript 1.5 Defined Objects
> ++++++++
>
>

I agree making description simple, but, "Standard global objects"
should not be changed. Because "Standard" is used to contrast　with
"LiveConnect".

> 99% of the time, the useful information in this page for developers
> amounts to two lines of text on the whole UI. Put everything I want to
> know about using RegExp on one page. Then I only have to load one page.
> It will be the top hit on searches so I don't have to guess which page
> to try. I don't have to wonder if I've read all there is about RegExp
> but I have.

O.K. I made a new sample of all in one page.
http://developer.mozilla.org/en/docs/User:Potappo:Core_JavaScript_1.5_Reference:Global_Objects:RegExp_%28all_in_one%29
http://developer.mozilla.org/en/docs/User:Potappo:Core_JavaScript_1.5_Reference:Global_Objects:RegExp:prototype
This sample moved members list from prototype (Object.prototype page
links members section of Object page).
How about this sample, all?

--
potappo
MDC Japanese Translation Team

> _______________________________________________
> dev-mdc mailing list
> dev...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-mdc
>

[John J. Barton]

potappo wrote:
> I agree making description simple, but, "Standard global objects"
> should not be changed. Because "Standard" is used to contrast　with
> "LiveConnect".
>

But which standard? The word standard can have two meanings here:
1) Normal, ordinary
2) An agreed-upon convention
The first one is imprecise: liveconnect is perfectly normal and ordinary
in some respects. The second one is what you mean. That's why I suggest
using a specific name rather than "standard".

I also suggest using the agreed-upon convention for naming these
objects. How about calling them "Native Javascript Objects" or
"Built-in Javascript objects" or "Initial Properties of the Javascript
Global Scope". By calling them "global objects" you right away fall in
the the confusion you were trying to clarify with the paragraph in the
first draft. Or "Global-scope Javascript Objects"?

John.