public
Fork of wycats/merb-core
Description: Merb Core: All you need. None you don't.
Homepage: http://www.merbivore.com
Clone URL: git://github.com/drnic/merb-core.git
Search Repo:
name age message
folder .gitignore Thu Mar 06 05:03:45 -0800 2008 Adds specs and changes for compatibility with A... [hassox]
folder CHANGELOG Tue Mar 04 22:25:17 -0800 2008 update changelog [ezmobius]
folder CONFIG Sat Jan 12 13:30:36 -0800 2008 Parts of Merb::Controller ported over [wycats]
folder LICENSE Sun Jan 13 17:50:05 -0800 2008 Updated rack adapters, added Merb::Config and m... [ezmobius]
folder README Thu Feb 14 08:28:57 -0800 2008 better docs for sample apps [ivey]
folder Rakefile Mon Mar 03 20:00:18 -0800 2008 Install gem with --local so it won't poll remot... [lsegal]
folder TODO Sun Jan 13 17:50:05 -0800 2008 Updated rack adapters, added Merb::Config and m... [ezmobius]
folder autotest/ Fri Feb 29 08:57:47 -0800 2008 get autotest working for merb-core [ivey]
folder bin/ Sun Mar 09 21:26:58 -0700 2008 Set mongrel as default adapter unless other alt... [daikini]
folder deps/ Fri Feb 29 13:50:54 -0800 2008 remove rbc files from rubinius experiments. [ezmobius]
folder docs/ Fri Feb 01 11:31:17 -0800 2008 Repairing a little of the damage by Hater. [Hampton Catlin]
folder lib/ Fri Mar 14 02:46:51 -0700 2008 Logger now works as expected, fixed ReloadClass... [fabien]
folder simple_benches/ Mon Feb 18 19:19:26 -0800 2008 Fixes for capture/concat [wycats]
folder spec/ Tue Mar 11 01:47:18 -0700 2008 Added Merb.testing? method [fabien]
folder tools/ Fri Feb 01 11:31:17 -0800 2008 Repairing a little of the damage by Hater. [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