- From: Julee Burdekin <jburdeki@adobe.com>
- Date: Tue, 3 Dec 2013 11:54:50 -0800
- To: PhistucK <phistuck@gmail.com>, Max Polk <maxpolk@gmail.com>
- CC: Renoir Boulanger <renoir@w3.org>, List WebPlatform public <public-webplatform@w3.org>
- Message-ID: <CEC373D6.A2A4F%jburdeki@adobe.com>
Max & PhistucK: I just have to say that I really appreciate your work on this!
Max: Did you do the full delete (to clean up old pages) and full upload to the test wiki?
Everyone: Except for the spaces > underscores, I think everything else should be deferred. (My comments inline as well. But…)
Unless someone feels we should hold up the import, let’s get this content imported!
I’m excited!
J
----------------------------
julee@adobe.com
@adobejulee
From: PhistucK <phistuck@gmail.com<mailto:phistuck@gmail.com>>
Date: Monday, December 2, 2013 at 12:31 AM
To: Max Polk <maxpolk@gmail.com<mailto:maxpolk@gmail.com>>
Cc: julee <jburdeki@adobe.com<mailto:jburdeki@adobe.com>>, Renoir Boulanger <renoir@w3.org<mailto:renoir@w3.org>>, WebPlatform Public List <public-webplatform@w3.org<mailto:public-webplatform@w3.org>>
Subject: Re: Second JS bulk upload
Thank you very much!
See my comments inline (for the last two messages).
☆PhistucK
On Sun, Dec 1, 2013 at 11:12 PM, Max Polk <maxpolk@gmail.com<mailto:maxpolk@gmail.com>> wrote:
As to two previous to-do items I just went ahead and did them.
FIRST item:
> Automation to do:
> 2. talk about static method page name (X/X.method versus X/method)
FIRST item resolution:
Someone adroitly pointed out that you can figure out if a method is a
static Object method or an instance method by simply reading the page,
so there is no need to declare it in the page name. Therefore,
changed all X/X.method to X/method:
javascript/Array/Array.isArray javascript/Array/isArray
javascript/Date/Date.now javascript/Date/now
javascript/Date/Date.parse javascript/Date/parse
javascript/Date/Date.UTC javascript/Date/UTC
javascript/JSON/JSON.parse javascript/JSON/parse
javascript/JSON/JSON.stringify javascript/JSON/stringify
javascript/Math/Math.abs javascript/Math/abs
javascript/Math/Math.acos javascript/Math/acos
javascript/Math/Math.asin javascript/Math/asin
javascript/Math/Math.atan javascript/Math/atan
javascript/Math/Math.atan2 javascript/Math/atan2
javascript/Math/Math.ceil javascript/Math/ceil
javascript/Math/Math.cos javascript/Math/cos
javascript/Math/Math.exp javascript/Math/exp
javascript/Math/Math.floor javascript/Math/floor
javascript/Math/Math.log javascript/Math/log
javascript/Math/Math.max javascript/Math/max
javascript/Math/Math.min javascript/Math/min
javascript/Math/Math.pow javascript/Math/pow
javascript/Math/Math.random javascript/Math/random
javascript/Math/Math.round javascript/Math/round
javascript/Math/Math.sin javascript/Math/sin
javascript/Math/Math.sqrt javascript/Math/sqrt
javascript/Math/Math.tan javascript/Math/tan
javascript/Object/Object.create javascript/Object/create
javascript/Object/Object.definePropertes
javascript/Object/defineProperties
javascript/Object/Object.defineProperty javascript/Object/defineProperty
javascript/Object/Object.freeze javascript/Object/freeze
javascript/Object/Object.getOwnPropertyDescriptor
javascript/Object/getOwnPropertyDescriptor
javascript/Object/Object.getOwnPropertyNames
javascript/Object/getOwnPropertyNames
javascript/Object/Object.getPrototypeOf
javascript/Object/getPrototypeOf
javascript/Object/Object.isExtensible javascript/Object/isExtensible
javascript/Object/Object.isFrozen javascript/Object/isFrozen
javascript/Object/Object.isSealed javascript/Object/isSealed
javascript/Object/Object.keys javascript/Object/keys
javascript/Object/Object.preventExtensions
javascript/Object/preventExtensions
javascript/Object/Object.seal javascript/Object/seal
javascript/String/String.fromCharCode javascript/String/fromCharCode
Great! Unless anyone objects?
[julee] I’m good with this!
SECOND item:
> 3. talk about Global/* (nobody says "Global.decodeURIComponent" so maybe hide the Global prefix)
SECOND item resolution:
Same as above, you can figure out it's in the Global object by reading
the page, I changed all Global.X page names to X. However, we should
contemplate keeping the Global page:
BEFORE --> AFTER
javascript/Global (do not change)
javascript/Global/Infinity javascript/Infinity
javascript/Global/NaN javascript/NaN
javascript/Global/null javascript/null
javascript/Global/undefined javascript/undefined
javascript/Global/decodeURI javascript/decodeURI
javascript/Global/decodeURIComponent javascript/decodeURIComponent
javascript/Global/encodeURI javascript/encodeURI
javascript/Global/encodeURIComponent javascript/encodeURIComponent
javascript/Global/escape javascript/escape
javascript/Global/eval javascript/eval
javascript/Global/isFinite javascript/isFinite
javascript/Global/isNaN javascript/isNaN
javascript/Global/parseFloat javascript/parseFloat
javascript/Global/parseInt javascript/parseInt
javascript/Global/unescape javascript/unescape
I'll do another full delete (to clean up old pages) and full upload
soon to the test wiki.
Note that the 381 page names are all still unique after all these changes.
Unique now does not mean unique later... ECMAScript is evolving and new built in objects can be (and are) added to the language. I really think we should be forward compatible here. What is ECMAScript 7 adds an "operators" property that lists all of the developer defined operators? we want to handle everything and be as unambiguous as possible, without having to change paths (SEO, bookmarks, familiarity, blabla...).
[julee] Phistuck: I think it’s a bit tricky to predict future language structure. We just as likely will need different versions of the docs to reflect different versions of the language. Max: I do prefer to have a “global" node in the URL (of course, it should be lowercase). But at this time, unless there’s strong opposition, let’s go with what you have here. We can always move them later if need be.
On Sun, Dec 1, 2013 at 10:48 PM, Max Polk <maxpolk@gmail.com<mailto:maxpolk@gmail.com>> wrote:
Done. Per Renoir:
BEFORE --> AFTER
javascript/JavaScript Reference javascript/reference
javascript/Math/Math Constants javascript/Math/constants
javascript/Number/Number Constants javascript/Number/constants
We should remember to discuss folding constants into the page of the object. Either -
- A page for every constant property (too verbose)
- All of the constants within the page of the object (compact and sensible), with redirects from the path of the individual properties (bla/CONST_NAME would redirect to bla#CONST_NAME).
[julee] Redirects might be a good idea, but I’m good with what Max has here.
javascript/RegExp/1 9 Properties javascript/RegExp/1 to 9 properties
The exception above is that the RegExp "x.1, x.2, ..., x.9" properties are numbered properties, so I couldn't remove the 1, 2, ..., 9, so I made it "1 to 9 properties" instead. Maybe good, maybe not so good.
We seem to be missing a dollar sign. It should be RegExp/$1 to $9 (or perhaps RegExp/$1..$2) with redirects from the individual paths.
[julee] please use underscores for spaces in URL. (see separate thread with Jen & Renoir)
Per Julee pages are lower-cased when they are descriptive words:
javascript/regular expression
javascript/operators/addition assignment
javascript/operators/addition
javascript/operators/assignment
javascript/operators/bitwise and assignment
javascript/operators/bitwise and
javascript/operators/bitwise left shift
javascript/operators/bitwise not
javascript/operators/bitwise or assignment
javascript/operators/bitwise or
javascript/operators/bitwise right shift
javascript/operators/bitwise xor assignment
javascript/operators/bitwise xor
javascript/operators/comma
javascript/operators/comparison
javascript/operators/compound assignment
javascript/operators/conditional ternary
javascript/operators/delete
javascript/operators/division assignment
javascript/operators/division
javascript/operators/in
javascript/operators/increment and decrement
javascript/operators/instanceof
javascript/operators/left shift assignment
javascript/operators/logical and
javascript/operators/logical not
javascript/operators/logical or
javascript/operators/modulus assignment
javascript/operators/modulus
javascript/operators/multiplication assignment
javascript/operators/multiplication
javascript/operators/new
javascript/operators/right shift assignment
javascript/operators/subtraction assignment
javascript/operators/subtraction
javascript/operators/typeof
javascript/operators/unsigned right shift assignment
javascript/operators/unsigned right shift
javascript/operators/void
I feel like operators, statements and literals should be within a "language" sub path and the objects/properties/methods should be in another sub path (the suggested "api" perhaps?). Two might be an exaggeration, I know. I am not sure about that, too.
[julee] Unless there’s a strong preference, I’m good with what Max has here.
Received on Tuesday, 3 December 2013 19:55:23 UTC