substance/application

Build Substance apps using Views, Controllers and Modules (CommonJS)

Substance.js

Substance is a JavaScript library for web-based content editing. It provides building blocks for realizing custom text editors and web-based publishing system. It is developed to power our online editing platform Substance.

Development

Install the dev dependencies.

npm install

Run the dev server.

npm start

Navigate to http://localhost:4001/test for the running the browser test suite. The test suite is rebuilt as you make changes to the source files.

To run the test-suite headless.

$ npm test

application's Issues

Regarding CommonJS dance, I've found this

http://esa-matti.suuronen.org/blog/2013/03/22/journey-from-requirejs-to-browserify/

Debugging

Well this one was easy. Just build the bundle with --debug flag

$ browserify --debug main.js > bundle.js
and Browserify will inline source maps into the bundle and then just fire up Chrome >with source maps enabled from developer tools and it will display the original files as >they where separate files.

But currently this seems to work only with Chrome. In others you get just a huge >bundle of Javascript. Source maps are coming to Firefox but I wouldn’t put my hopes >up for IE…

I wonder how this source maps approach compares to ours?

Maybe also worth consideration: What if we had a static compile workflow where we traverse the dependency tree as usual but then create static versions of the compiled files. We could then also replace the require('..') stuff in the output file and replace with global module equivalents.

Like:

var util = require ('substance-util')

would be replaced with:

var util = Substance.util;

(given that we can map those names...)

Well not sure... just a thought..