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/tooky/merb-core.git
name age message
file .gitignore Thu Jan 31 17:06:29 -0800 2008 rake rcov works now with the individual spec ru... [Yehuda Katz]
file CONFIG Sat Jan 12 13:30:36 -0800 2008 Parts of Merb::Controller ported over [wycats]
file LICENSE Sun Jan 13 17:50:05 -0800 2008 Updated rack adapters, added Merb::Config and m... [ezmobius]
file README Thu Jan 31 08:34:10 -0800 2008 Applied most of patch by hcatlin (excepting log... [wayneeseguin]
file Rakefile Tue Feb 12 20:20:24 -0800 2008 Allow for running specs with different Ruby imp... [dudleyf]
file TODO Sun Jan 13 17:50:05 -0800 2008 Updated rack adapters, added Merb::Config and m... [ezmobius]
directory autotest/ Fri Feb 01 11:32:29 -0800 2008 A few more tweaks [Hampton Catlin]
directory bin/ Mon Jan 28 22:12:40 -0800 2008 Now that 0.5.x is end-of-lifed, merb-core insta... [ivey]
directory docs/ Fri Feb 01 11:31:17 -0800 2008 Repairing a little of the damage by Hater. [Hampton Catlin]
directory lib/ Wed Feb 13 20:54:34 -0800 2008 Not sure how this didn't get commited [ivey]
directory simple_benches/ Tue Feb 05 13:41:08 -0800 2008 Adds new paths and makes render work in dev mode. [Yehuda Katz]
directory spec/ Wed Feb 13 20:33:01 -0800 2008 added test plugin dependency call to use_test [benburkert]
directory 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, reference the /sample directory