public
Rubygem
Description: Merb Core: All you need. None you don't.
Homepage: http://www.merbivore.com
Clone URL: git://github.com/wycats/merb-core.git
wycats (author)
Mon Feb 18 19:19:26 -0800 2008
commit  3d023b06e4da0bfc9edbb28ee92fd2bec762b31a
tree    6249c26c22c40bbe8dc6953e55d7382a290622ec
parent  a952c9895541975ee64689782f9a6023e9416f28
name age message
file .gitignore Thu Feb 14 09:16:02 -0800 2008 ignore DS_Store files [tdreyno]
file CHANGELOG Sun Feb 17 06:55:18 -0800 2008 fix date for 0.9.0 [ivey]
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 Feb 14 08:28:57 -0800 2008 better docs for sample apps [ivey]
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/ Mon Feb 18 19:19:26 -0800 2008 Fixes for capture/concat [wycats]
directory simple_benches/ Mon Feb 18 19:19:26 -0800 2008 Fixes for capture/concat [wycats]
directory spec/ Mon Feb 18 19:19:26 -0800 2008 Fixes for capture/concat [wycats]
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,
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