W3C home > Mailing lists > Public > public-webplatform@w3.org > November 2013

Re: First JS bulk upload

From: PhistucK <phistuck@gmail.com>
Date: Sat, 23 Nov 2013 10:41:53 +0200
Message-ID: <CABc02_Jtqjqz0pgt8R1oP0pe2x-2uTcfoBX9-VS5T96ZucwR1g@mail.gmail.com>
To: Max Polk <maxpolk@gmail.com>
Cc: Webplatform List <public-webplatform@w3.org>
Thank you very much!

I am sorry I was not able to join the meeting.
I will be reading the summary once it gets posted
http://docs.webplatform.org/wiki/WPD:Community/Meetings/General, unless
anyone wants to fill me in sooner.

Is there a consensus regarding Array/Array.isArray (and
Object/Object.freeze and friends)?
Is there a consensus regarding having an additional "Global" path? why is
that there? everything should be under global, not just non object members.

More things to drop -
Debug (and its members)
ScriptEngine (and its members)
prototype, constructor (from anything other than Object)
valueOf, toString (from anything other than Object, unless it is
overridden, like Date.toString() which I think is the only exception?)

Future content issues (I guess no automation would do these) -
arguments/0 n Properties and RegExp/1 9 Properties should be encapsulated
within arguments and RegExp, respectively, I believe.

Any constant (or multiple constant pages) should be encapsulated within the
its containing object and if not, the " Constant" suffix should be dropped.

String/HTML Tag Methods should really be separated into pages for the
individual methods.


On Sat, Nov 23, 2013 at 4:45 AM, Max Polk <maxpolk@gmail.com> wrote:

> Good news, the first round of test wiki uploads of JavaScript pages just
> completed.  The batch upload took about 21 minutes to complete.  The root
> of the upload is:
>     http://docs.webplatform.org/test/Tests/javascript-b
> If you take the "all pages" link a special page listing all the files can
> be used to look around.  There are too many to list so the "Next page" link
> will show you the remainder.
> The first very obvious problem is that I have to update all the internal
> links.  One example is that I uploaded a page as:
>     Tests/javascript-b/Future Reserved Words
> But the internal link to that page (from the "JavaScript Reference" page)
> points to the root of the wiki:
>     [[Future Reserved Words|JavaScript Future Reserved Words]]: Provides
> ....
> That's an easy fix, I'll get that in within a day.
> The automation priorities are probably in this order:
> 1.  IT WORKS -- the links will be fixed and I'll upload again tomorrow
> (Saturday 11/23)
> 2.  IT'S IN THE RIGHT PLACE -- the paths should be right, so have a look
> at where things are.
> 3.  CONTENT FILTERING -- there are things to fix with page content like
> lots of empty "see also" sections, or vendor-specific information, or links
> we don't want, and so forth.  Much of this can be automatically fixed.  If
> it's just one or two pages, we can do that by hand later.
> 4.  TEMPLATES -- add semantic form templates
> 5.  ANYTHING ELSE -- any large-scale fix-ups that should be programmed
> before we declare the import effort finished.
> As each of the above progress, I'll re-upload everything all over again,
> so it will undergo incremental improvements.
> --Max
Received on Saturday, 23 November 2013 08:43:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:13:55 UTC