public
Description: Merb Core: All you need. None you don't.
Homepage: http://www.merbivore.com
Clone URL: git://github.com/wycats/merb-core.git
commit  8cd7aae5b2d8385eeff04b99bb40b29bb87cdb65
tree    99c1b260e4662e1cc0efb9284b00b84ccd302874
parent  170b54198484c0422c922544b56096d422c3a043
name age message
file .gitignore Thu Mar 06 05:03:45 -0800 2008 Adds specs and changes for compatibility with A... [hassox]
file CHANGELOG Tue Mar 04 22:25:17 -0800 2008 update changelog [ezmobius]
file CONFIG Sat Jan 12 13:30:36 -0800 2008 Parts of Merb::Controller ported over _attr_acc... [wycats]
file LICENSE Sun Jan 13 17:50:05 -0800 2008 Updated rack adapters, added Merb::Config and m... [ezmobius]
file README Thu Feb 14 08:28:57 -0800 2008 better docs for sample apps [ivey]
file Rakefile Mon Mar 03 20:00:18 -0800 2008 Install gem with --local so it won't poll remot... [lsegal]
file TODO Sun Jan 13 17:50:05 -0800 2008 Updated rack adapters, added Merb::Config and m... [ezmobius]
directory autotest/ Fri Feb 29 08:57:47 -0800 2008 get autotest working for merb-core Extracted r... [ivey]
directory bin/ Sun Mar 09 21:26:58 -0700 2008 Set mongrel as default adapter unless other alt... [daikini]
directory deps/ Fri Feb 29 13:50:54 -0800 2008 remove rbc files from rubinius experiments. [ezmobius]
directory docs/ Fri Feb 01 11:31:17 -0800 2008 Repairing a little of the damage by Hater. Fix... [Hampton Catlin]
directory lib/ Loading commit data...
directory simple_benches/
directory spec/
directory tools/ Fri Feb 01 11:31:17 -0800 2008 Repairing a little of the damage by Hater. Fix... [Hampton Catlin]
README
merb-core is a new branch of Merb (also referred to as merb-next or the 0.9 series) which aims to provide a stable, 
stripped down API for a future Merb 1.0 release.

This branch is based off the 0.5 release series but with significant rewrites.

Goals of this release:

  * Stabilize the @public interface methods to provide for a more consistent application development experience.
  * Remove features until nothing except a central application API is left
  * Improve comments on methods using a standard documentation methodology as described in DOCUMENTATION_STANDARDS
  * Separate the tests into two sections... "private" and "public"
    * Public methods are methods tagged with @public that will be part of the standard, stable Merb API
    * Private methods are implementation methods that might 
  * Implement a new render API
  * Build more extensions to regain selected features when needed
  
To familiarize yourself with how a merb-core application might look,
use merb-gen (from merb-more) to generate a few apps:
$ merb-gen myapp                   # a "normal" merb app
$ merb-gen myapp --flat            # a flattened app
$ merb-gen myapp --very-flat       # a single-file app