Idea of documenting js code inspired by python and EcmaScript 5 "strict mode"; Works on narwhal, firefox, chromium, safari (not tested on ie)
Below is the example of usage in this in the the shell
gozala@ijarti:~/Projects/meta-doc (master)$ narwhal
Rhino 1.7 release 3 PRERELEASE 2009 04 05
js> require("meta-doc/toolkit").doc()
toolkit module
provides utilities for getting a live docs
| // Here is a proposal for minimalist JavaScript classes(?), that does not | |
| // introduces any additional syntax to the language, instead it standardizes | |
| // approach already used by majority of JS frameworks today. | |
| // !!! What is a PROBLEM!!! | |
| function Dog(name) { | |
| // Classes are for creating instances, calling them without `new` changes | |
| // behavior, which in majority cases you need to handle, so you end up with | |
| // additional boilerplate. |
| Function.prototype.runOnBackgroundThread = function (aCallback) { | |
| var _blob = new Blob(['onmessage = '+this.toString()],{"type":"text/javascript"}); | |
| var _worker = new Worker((webkitURL.createObjectURL || URL.createObjectURL)(_blob)); | |
| _worker.onmessage = aCallback; | |
| _worker.postMessage(); | |
| } | |
| var _test = function () { | |
| postMessage((1+1).toString()); | |
| } |
| // Content scripts will be able to require modules, only | |
| // high level ones that are E10S friendly and can do | |
| // everything via data that is serialize. | |
| $(function() { | |
| // what we have now | |
| self.on('event-name', function(data) { | |
| // ... something | |
| }); | |
| self.port.emit('something'); |
| (function(exports) { | |
| // Simple, tiny, dumb module definitions for Browser JavaScript. | |
| // | |
| // What it does: | |
| // | |
| // * Tiny enough to include anywhere. Intended as a shim for delivering | |
| // browser builds of your library to folks who don't want to use script loaders. | |
| // * Exports modules to `__modules__`, a namespace on the global object. | |
| // This is an improvement over typical browser code, which pollutes the | |
| // global object. |
| var npm = require("npm") | |
| var path = require("path") | |
| npm.load({ prefix: path.join(process.env.HOME, ".orchestrator") }, function(e, npm) { | |
| npm.commands.ls([], function(err, _) { | |
| // this time it's nothing but probably results are cached | |
| npm.commands.install(["method"], function(err, _) { | |
| // now there is something but it still thinks there is nothing. | |
| npm.commands.ls([], console.log) | |
| }) |
| let { Cc, Ci } = require('chrome'); | |
| let appShellService = Cc['@mozilla.org/appshell/appShellService;1']. | |
| getService(Ci.nsIAppShellService); | |
| let service = Cc["@mozilla.org/observer-service;1"]. | |
| getService(Ci.nsIObserverService); | |
| let window = appShellService.hiddenDOMWindow; | |
| let document = window.document; | |
| let XUL = 'http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul' |
| var obj = { | |
| _discoverScriptsAndSources: function TA__discoverScriptsAndSources() { | |
| let scriptsAdded = []; | |
| for (let s of this.dbg.findScripts()) { | |
| if (!this._allowSource(s.url)) { | |
| continue; | |
| } | |
| scriptsAdded.push(this._addScript(s)); |
| // This is in response to https://gist.github.com/Peeja/5284697. | |
| // Peeja wanted to know how to convert some callback-based code to functional | |
| // style using promises. | |
| var Promise = require('rsvp').Promise; | |
| var ids = [1,2,3,4,5,6]; | |
| // If this were synchronous, we'd simply write: |