cadorn

Objective

Revive active development of createjs.org to fix bugs and enable new features including wider compatibility with modern web technology and frameworks.

Background

CreateJS was originally developed as part of Midgard and has since been integrated into several CMS systems including Symfony. Work originally started in 2011/2012 but has since faded as initial functionality has been accomplished. Many bugs and wishes have been collected for CreateJS and various sub-projects and it is time to reboot this effort.

cadorn

pio deplo┌──────────────────────────────┬────────────────────────────────────────┬────────────────────────────────────────────────────────────────────────────────┐
│ Group                        │ Service                                │ Host                                                                           │
│ 0-pio                        │ pio.server                             │                                                                                │
│ 0-pio                        │ pio.postdeploy                         │                                                                                │
│ 0-sm                         │ smi.cache                              │                                                                                │
│ 0-sm                         │ smi.cli                                │                                                                                │
│ devcomp.meta                 │ io.devcomp.meta.profiles               │            

cadorn

<script src="http://fireconsole.github.io/harviewer/fireconsole/bundles/loader.js"></script>

<div id="content" version="@VERSION@"></div>

<script>
  PINF.sandbox("http://fireconsole.github.io/harviewer/fireconsole/bundles/plugin.js", function (sandbox) {
      sandbox.main();
  }, function (err) {
      console.error("Error while loading plugin.js bundle':", err.stack);

cadorn

let { Cc, Ci, Cu } = require('chrome');


/* const FileUtils = */ Cu.import("resource://gre/modules/FileUtils.jsm");

const TIMERS = require("sdk/timers");
const WINDOW_UTILS = require("sdk/window/utils");
const PROMISE = require("sdk/core/promise");

cadorn

PINF.bundle("", function(require) {
    require.memoize("/main.js", function(require, exports, module) {
        exports.main = function(options) {
            console.log("Hello from PINF loader");
            document.write("Hello from PINF loader</br>");

            function load() {
                console.log("Load remote bundle...");
                require.sandbox("https://s3.amazonaws.com/static.cadorn.net/cross-domain.js?t=" + Date.now(), {
            		onInitModule: function(moduleInterface, moduleObj) {

cadorn

You activate a workspace by placing environment variables into your shell and modifying the PATH.

Shell environment variables represent the root config layer and all config resolving must happen from this base layer. If any code in your codebase must resolve config info it MUST have access to environment variables directly or indirectly or at the very least to the root path of the workspace so the environment variables may be established by loading and parsing the raw files.

Any config resolution logic must in its entirety be seeded by the environment variables and may then branch out with arbitrary logic. Ideally further config resolution layers follow rules and patterns that me be shared across implementations.

pio conventions

Given a file tree such as:

cadorn

Collaboration on packages is the precursor to an entire new paradigm of collaborative system development.

Join a group of people interested in collaborative realtime distributed system development and associated tooling.

You recognize that it takes many small components to make a large system and that there is no adequate open source tooling to assist with the creative process of modelling complex systems and making them a reality.

Time: Every Wednesday 10am - 11am PST

Where: Google Hangouts on Air (links will be sent to mailing list every week)

cadorn

nwjs/nw.js#132

cadorn

The promises based implementation is much slower than the callback based implementation.

I am wondering why exactly that is the case.

Usage

var Q = require("q");
var SCANNER = require("./promises");

//var SCANNER = require("./callbacks");

cadorn

/**
 * Copyright: 2012 Christoph Dorn <christoph@christophdorn.com>
 * License: MIT
 * Source: https://gist.github.com/1725325
 * 
 * NodeJS Example:
 * 
 *     // Requirements: `npm install q`
 *     
 *     var Q = require("q");