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 0aa3adaf5af6bb554a06cfff0e645afad404db07
tree 015db498e931a6d14ef969db59c5ae17bc1527b5
parent 68fea9a7c2e4f9ff9dc9d1bc991473d37b2c6033 parent f1c3336ad22fde9b4e0ecf639be7edded24e3e01
tree 015db498e931a6d14ef969db59c5ae17bc1527b5
parent 68fea9a7c2e4f9ff9dc9d1bc991473d37b2c6033 parent f1c3336ad22fde9b4e0ecf639be7edded24e3e01
| name | age | message | |
|---|---|---|---|
| |
.gitignore | ||
| |
CHANGELOG | ||
| |
CONTRIBUTORS | ||
| |
LICENSE | Thu Jun 19 16:47:25 -0700 2008 | |
| |
PLUGIN_API_CHANGELOG | ||
| |
PUBLIC_CHANGELOG | ||
| |
README | Mon Jun 02 22:37:48 -0700 2008 | |
| |
Rakefile | ||
| |
TODO | Sun Jan 13 17:50:05 -0800 2008 | |
| |
autotest/ | Thu Aug 21 18:09:14 -0700 2008 | |
| |
bin/ | ||
| |
docs/ | Sat May 17 07:12:47 -0700 2008 | |
| |
experimentation/ | ||
| |
lib/ | ||
| |
merb-core.gemspec | ||
| |
spec/ | ||
| |
tools/ |
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








