public
Rubygem
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/famoreira/merb-core.git
name age message
file .gitignore Sun May 04 05:49:53 -0700 2008 Add Emacs TAGS to ignore [michaelklishin]
file CHANGELOG Sun May 04 17:49:15 -0700 2008 0.9.3 changelog [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 May 27 06:56:03 -0700 2008 Better usage of merb_rake_helper.rb [fabien]
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 [ivey]
directory bin/ Thu May 01 22:57:14 -0700 2008 Show merb usage if first argument is not a switch [daikini]
directory deps/ Fri Feb 29 13:50:54 -0800 2008 remove rbc files from rubinius experiments. [ezmobius]
directory docs/ Sat May 17 07:12:47 -0700 2008 Add links to source at GitHub to boot diagram [michaelklishin]
directory lib/ Tue May 27 06:56:03 -0700 2008 Better usage of merb_rake_helper.rb [fabien]
file merb-core.gemspec Thu May 08 11:32:22 -0700 2008 Update GitHub gemspec. [michaelklishin]
directory simple_benches/ Thu May 15 09:59:22 -0700 2008 Merge branch 'master' of git@github.com:wycats/... [wycats]
directory spec/ Tue May 27 00:07:36 -0700 2008 Merge branch 'master' of git@github.com:wycats/... [fabien]
directory tools/ Mon May 12 17:39:34 -0700 2008 remove :nodoc: from merb-core DO NOT USE :nodoc... [ezmobius]
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