This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
commit 0e36b591f46eaecdba168f03b36b87388eb5cfa3
tree 90fc8765e50963e7ac4d7d0c6e8064b30a16fe5c
parent e8c05531659c45f918f17b7627886bf3e9a40556
tree 90fc8765e50963e7ac4d7d0c6e8064b30a16fe5c
parent e8c05531659c45f918f17b7627886bf3e9a40556
| name | age | message | |
|---|---|---|---|
| |
.gitignore | Thu May 29 18:34:49 -0700 2008 | |
| |
CHANGELOG | Sun May 04 17:49:15 -0700 2008 | |
| |
CONFIG | Sat Jan 12 13:30:36 -0800 2008 | |
| |
LICENSE | Sun Jan 13 17:50:05 -0800 2008 | |
| |
README | Mon Jun 02 22:37:48 -0700 2008 | |
| |
Rakefile | Tue May 27 06:56:03 -0700 2008 | |
| |
TODO | Sun Jan 13 17:50:05 -0800 2008 | |
| |
autotest/ | Fri Feb 29 08:57:47 -0800 2008 | |
| |
bin/ | Thu May 01 22:57:14 -0700 2008 | |
| |
docs/ | Sat May 17 07:12:47 -0700 2008 | |
| |
lib/ | ||
| |
merb-core.gemspec | Thu May 08 11:32:22 -0700 2008 | |
| |
simple_benches/ | Thu May 15 09:59:22 -0700 2008 | |
| |
spec/ | ||
| |
tools/ | Mon May 12 17:39:34 -0700 2008 |
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








