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/somebee/merb-core.git
fabien (author)
Tue May 13 07:10:45 -0700 2008
commit  b69535fb0ab77faf2b6fe8d1284003f8dcd16e24
tree    3a7ce384cc6dff80c913160ef26a54eda5daa21e
parent  7857f9f4fcf218c4840907d12629e9262d059223 parent  2f703e0d99902edf9abaa411d4fc0a33697fa7eb
name age message
file .gitignore Loading commit data...
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 _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
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/ Thu May 01 22:57:14 -0700 2008 Show merb usage if first argument is not a swit... [daikini]
directory deps/ Fri Feb 29 13:50:54 -0800 2008 remove rbc files from rubinius experiments. [ezmobius]
directory docs/
directory lib/
file merb-core.gemspec Thu May 08 11:32:22 -0700 2008 Update GitHub gemspec. [michaelklishin]
directory simple_benches/
directory spec/
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