Re: First full upload of MSDN-contributed JavaScript pages

Thank you very much!

I believe there is a lot more work to be done, we need to create (or use
existing) templates for JavaScript property, method and function pages.
Then we should map the textual representation of the types, parameters and
return values to the template syntax, so the SemanticMediaWiki magic could
kick in as appropriate.

I do not think we should import without this process, because it is a
tremendous amount of manual work otherwise...


☆*PhistucK*


On Wed, Jun 12, 2013 at 2:28 AM, Max Polk <maxpolk@gmail.com> wrote:

> The methodology is explained in the Strategy section of my notes page:
>
>     http://dev.maxpolk.org/msdnjs/MSDN-JS_development
>
> Basically I'm using the original structure:
>
>     https://github.com/webplatform/msdn-js/blob/master/js_toc.html
>
> And simplifying page names to avoid duplication.  I first said a bit
> about it here:
>
>
> http://lists.w3.org/Archives/Public/public-webplatform/2013May/0261.html
>
> And you can see PhistucK's response, where a modification was
> suggested.  I was focused mainly on getting something out there so far
> and didn't address renaming things yet.  The scripts used are public
> at:
>
>     https://github.com/maxpolk/msdn-js-conversion
>
> And it's a Bash script that uses Linux tools for fixing filename
> anomalies, fixing internal links, renaming pages, removing unusual UTF
> characters, doing the page to final location mapping, calling the
> Python conversion script to actually convert the HTML into Mediawiki
> markup with proper escaping, and afterward uploading everything to the
> right location using a modified wpd tool.
>
> Page names are a bit tricky.  Some functions (isArray) are not called
> on objects, but on the prototype, such as Array.isArray(x), so its
> page name is "Objects/Array/Array.isArray Function".  This differs
> from the normal page name for functions called on instances like
> x.concat(b, c) with page name "Objects/Array/concat Method."
>
> We already have some good candidates for naming improvements from this
> untouched original structure by PhistucK, and as long as there is a
> deterministic process to arrive at the right name, it can be coded to
> use that.  I have no preference as to final structure at the moment,
> so whatever is desired I'm here to make it happen.
>
> On Mon, Jun 10, 2013 at 2:49 AM, Doug Schepers <schepers@w3.org> wrote:
> > Hi, Max-
> >
> > Great work!
> >
> > This is an excellent first pass. Can you talk a bit about your
> methodology,
> > and maybe point us to your import script?
> >
> > We'll need to get serious about discussing how we want the pages to be
> > structured, and what the templates should look like. This first pass
> will be
> > a great boon in having something concrete to talk about.
> >
> > I'm really excited about this!
> >
> > Best Regards-
> > -Doug
> >
> >
> >
> > On 6/10/13 12:18 AM, Max Polk wrote:
> >>
> >> The first full upload of the MSDN-contributed JavaScript pages can
> >> be found for review and comments at:
> >>
> >> First set:
> >>
> >>
> >>
> http://dev.maxpolk.org/msdnjs/index.php?title=Special:AllPages&from=Constants&to=Objects%2Farguments
> >>
> >>  Second set:
> >>
> >>
> >>
> http://dev.maxpolk.org/msdnjs/index.php?title=Special%3AAllPages&from=Objects%2Farguments&to=&namespace=0
> >>
> >>  This was an automated process and if there are glitches in
> >> formatting you see, please let me know.  The next step is to make
> >> fixes based on comments, then upload to the test wiki for a final
> >> review, and afterwards to webplatform.
> >>
> >
> >
>
>