Go to file
Jeff Avallone 773fd5c1a6 Refactoring how _position is called to be promise-based
The render method now returns a promise. Once this promise is resolved,
the _position method for that node will be called (if applicable). This
promise must be resolved only after all subordinate nodes have completed
their render phase (the promise returned by subordinate node's render
method has resolved). Node that do not have subordinates can return the
result of calling terminalRender, and proxied renders only need to
return the result of calling proxy.

With this change, it is no longer necessary to explicitly position
subordinate nodes. They will already be positioned once their render
promise is resolved.
2014-12-13 09:09:58 -05:00
lib Integrating canopy (with a demo parser from the canopy docs) 2014-11-24 22:31:20 -05:00
spec/parser Beginning to add some functionality to the parser 2014-11-26 18:24:40 -05:00
src Refactoring how _position is called to be promise-based 2014-12-13 09:09:58 -05:00
.gitignore Adding initial compass integration 2014-11-23 16:16:10 -05:00
.ruby-gemset Adding initial compass integration 2014-11-23 16:16:10 -05:00
.ruby-version Adding initial compass integration 2014-11-23 16:16:10 -05:00
config.js Tweaking browserify setup to get all es6 features working 2014-12-04 18:34:35 -05:00
Gemfile Adding initial compass integration 2014-11-23 16:16:10 -05:00
Gemfile.lock Adding initial compass integration 2014-11-23 16:16:10 -05:00
gulpfile.js Switching Karma test browser to Chrome 2014-12-04 19:11:30 -05:00
karma.conf.js Switching Karma test browser to Chrome 2014-12-04 19:11:30 -05:00
LICENSE.txt Adding basic readme and license 2014-11-23 11:41:53 -05:00
package.json Switching Karma test browser to Chrome 2014-12-04 19:11:30 -05:00
README.md Updating gulpfile to run karma separately. 2014-11-25 08:51:22 -05:00
template.html Adding Regexper markup and styles 2014-11-23 17:13:05 -05:00

Build Status

Regexper

Code for the http://regexper.com/ site.

Contributing

I greatly appreciate any contributions that you may have for the site. Feel free to fork the project and work on any of the reported issues, or let me know about any improvements you think would be beneficial.

When sending pull requests, please keep them focused on a single issue. I would rather deal with a dozen pull requests for a dozen issues with one change each over one pull request fixing a dozen issues. Also, I appreciate tests to be included with feature development, but for minor changes I will probably not put up much of a fuss if they're missing.

Working with the code

Node and Ruby are required for working with this site. It is recommended to use rbenv or rvm to manage your Ruby installation, and configuration files are included to set the Ruby version and gemset.

To start with, install the necessary dependencies for Node and Ruby:

$ bundle install
$ npm install

There are several gulp tasks available to build various parts of the site, but to get started you only need:

$ gulp

This will build the site into the ./build directory, start a local start on port 8080, and begin watching the source files for modifications. The site will automatically be rebuilt when files are changed. Also, if you browser has the LiveReload extension, then the page will be reloaded.

To automatically run Karma test, run the following:

$ gulp karma

To build the site for deployment, run the following:

$ gulp build

The site will be built into the "build" directory.

License

See LICENSE.txt file for licensing details.