These are chat archives for dthree/wat

7th
Sep 2015
Jason Stallings
@octalmage
Sep 07 2015 04:25
Lol nothing.
Antti Korpi
@anko
Sep 07 2015 14:34
With reference to @dthree's comment on #17: Do we have a Big List of Everything That Needs Doing™ somewhere? Or should I just PR whenever I check wat for something I think it should know but doesn't?
Jason Stallings
@octalmage
Sep 07 2015 14:36
We put together a list the other day, I don't think it's online though.
@dthree wants to have a handful of popular/core modules documented.
Jason Stallings
@octalmage
Sep 07 2015 14:42
I was going to work on nan, async, and nw.js/electron.
Jason Stallings
@octalmage
Sep 07 2015 14:47
But really anything could be submitted, so have at it!
Antti Korpi
@anko
Sep 07 2015 14:49
Cool, I'll keep eyes open for stuff I wish was in there.
I'll certainly be watching and proofreading PRs. :)
dc
@dthree
Sep 07 2015 16:13
:) thanks! Yeah, any contributions are helpful. Honestly, the most important are the bigger libs / langauges, like JS, HTML, CSS, React, etc.
On smaller libs, I'm I/P building a scraper that auto-generates docs in the right format for small projects. This is great for npm modules or libraries that are well documented on Github in their readme, and I expect it to cover 90% of the content on wat.
Larger projects, such as what I mentioned above, can afford manual docs and maitenance by the community and generally have their own doc site and so are harder to scrape.
dc
@dthree
Sep 07 2015 19:10
@octalmage @anko This is my idea on tabbed-autocompletion traversal on auto-build libraries. How does this sound?

? robotjs [tab]

  Methods           Properties        Docs
  ----------------  ----------------  ----------------
  mouseToggle       isBlah            readme/
  moveMouse         length            wiki/
  ...               imMakingTheseUp
                    ...

? robotjs wiki building [tab]

  ubuntu    mac    windows

? robotjs wiki building ubuntu [enter]

`node-gyp build` will fail without these headers present, you can install with:

?
methods, properties and docs would be colored different colors btw
readme and wiki docs drill in using a hierarchal tree built by ## headers