diff --git a/app/assets/javascripts/helpers/mixin.catcher.js.coffee b/app/assets/javascripts/helpers/mixin.catcher.js.coffee
index c5ca7e6f..26e23664 100644
--- a/app/assets/javascripts/helpers/mixin.catcher.js.coffee
+++ b/app/assets/javascripts/helpers/mixin.catcher.js.coffee
@@ -5,9 +5,9 @@
#
# @mixin
#
-class Mixin.Catcher
+Mixin.Catcher =
- @ClassMethods:
+ ClassMethods:
catchable: ( fns ) ->
for name, fn of fns
@::[ name ] = ( ) ->
@@ -17,13 +17,4 @@ class Mixin.Catcher
@_catcher.apply( @, [ @, e ] )
return undefined
- @InstanceMethods: {}
-
-
-
-
-
-
-
-
-
+ InstanceMethods: {}
\ No newline at end of file
diff --git a/doc/README.md.html b/doc/README.md.html
index c40003f7..2dfdfecf 100644
--- a/doc/README.md.html
+++ b/doc/README.md.html
@@ -2,7 +2,7 @@
- Broyologramming Life API Documentation
+ CoffeeScript API Documentation
@@ -130,21 +130,20 @@
Programming Life: Gigabase
Gigabase: Synthetic Biology Cell Modeling
which is modeled by one or more differential equations. The proposed model describes
an av- erage cell in a growing population of cells. Ordinary Differential Equations (ODEs)
in this model describe the change of molecule concentrations in time.
Installation
Gigabase runs on Rails. You can load this repository onto your hard drive and directly use
-it as a rails app. Just run bundle install and rake db: setup and you are good to go.
+it as a rails app. Just run bundle install and rake db:setup and you are good to go.
For windows users, some gems might not install and display a message such as not native build.
Download the Ruby Devkit and run the bundle install command in mysys terminal. All the
gems will then perfectly build. Don't forget you might need administrator rights.
Build Status
-
develop
master
Pull Requests
We are always open to pull requests. After June 2013 the project will no longer be
-fixed in direction, so more freedom on where to go. We do not allow pull requests on master
-or release branches. Fork the repository, create a patch/feature/issue branch and
-merge to develop.
Your code should be rdoc or codo/coffeedoc commented, assets should be /spec/ tested
+
develop
master
Pull Requests
After June 2013 the project will no longer have constraints so we could go any direction.
+We do not allow pull requests on master or release branches. Fork the repository, create
+a patch/feature/issue branch and merge to develop.
Your code should be rdoc or codo/coffeedoc commented, assets should be /spec/ tested
and when applied should have /test/functional integration tests. Server side code should
also be /test/ unit tested.