[13:06]<JohnnyL> What the progress for JS on the server? [13:09]<Wes-> JohnnyL: suggest scanning the commonjs google group, search for jsgi [13:09]<JohnnyL> ok] [13:09]<JohnnyL> ok [13:11]<JohnnyL> looks like a major work in progress. [13:11]<JohnnyL> how many years? [15:27]<Wes--> anybody here connected to mozilla's IRC? ashb? [15:28]<ashb> Wes--: yeah still alive [15:29]<Wes--> ashb: Wierd, I can't connect. Must be a network routing thing. [15:31]* ondras is connected as well [15:32]<ondras> trying to find out how to create a symlink via xpcom :) [15:35]<Wes--> Looks like there was an interruption in the force [15:35]<Wes--> I mean, the 'net [15:35]<Wes--> between Chicago and Sandy Eggo [19:32]<sid3k> hi all. I've been thinking on a new documentation tool and documentation notation. [19:32]<sid3k> here is an example: http://gist.github.com/405394 [19:32]<sid3k> any ideas and suggestions are welcome [19:36]<kriszyp> is the intent to make the documentation available through AST? [19:43]<sid3k> kriszyp: nope, my main intent is to make code more clean, readable [19:49]<deanlandolt> sid3k: then what's the different between your syntax and comments? it's effectively the same [19:57]<sid3k> deanlandolt: still I'm thinking on a better one. There should be better ways to document javascript [20:11]<Wes--> sid3k: It would also be nice to have a tool which can document javascript-modules-as-implemented-by-native-code [20:12]<Wes--> sid3k: We (gpsee) have a documentation generator which does exactly that; it's a WIP but very useful nonetheless. In an ideal work, we could use the same tool on any input language to document what happens from the JS perspective. [20:43]<sid3k> Wes--: I wasn't aware of gpsee, thank you for pointing [20:44]<Wes--> sid3k: FWIW - our documentation generator is here - http://code.google.com/p/jazzdocs/ - same output here: http://www.page.ca/~wes/opensource/gpsee/docs/modules/jazzdocs.html [20:45]<Wes--> sid3k: re. sample output -- signal and gffi are commonjs modules implemented in C; shellalike is a commonjs module implemented in JavaScript. I FIRMLY believe that it should be possible to generate docs describing the javascript interface with a single tool regardless of input language. [20:46]<Wes--> sid3k: JazzDocs (hdon author) does this by scanning for jazzdocs-formatted comments, which are different than javadoc -- that way we have C-level docs, too, for the C stuff. [21:11]<sid3k> Wes--: looks very helpful. I'm going to dive in as soon as possible