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/reframeit/merb-core.git
name age message
file .gitignore Sat Jul 19 19:12:59 -0700 2008 Ignore temp Emacs files. [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 _attr_acc... [wycats]
file LICENSE Thu Jun 19 16:47:25 -0700 2008 update license [ezmobius]
file PLUGIN_API_CHANGELOG Fri Jun 20 15:10:33 -0700 2008 Old stuff that should be committed. [wycats]
file PUBLIC_CHANGELOG Loading commit data...
file README Mon Jun 02 22:37:48 -0700 2008 Fix README for merb-gen app foo [ivey]
file Rakefile
file TODO Sun Jan 13 17:50:05 -0800 2008 Updated rack adapters, added Merb::Config and m... [ezmobius]
directory autotest/
directory bin/ Thu May 01 22:57:14 -0700 2008 Show merb usage if first argument is not a swit... [daikini]
directory docs/ Sat May 17 07:12:47 -0700 2008 Add links to source at GitHub to boot diagram [michaelklishin]
directory experimentation/
directory lib/
file merb-core.gemspec
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 app myapp                   # a "normal" merb app
$ merb-gen app myapp --flat            # a flattened app
$ merb-gen app myapp --very-flat       # a single-file app