wycats / merb
- Source
- Commits
- Network (101)
- Issues (3)
- Downloads (25)
- Wiki (1)
- Graphs
-
Tree:
0ae3b0c
Matt Aimonetti (author)
Mon Oct 13 13:18:53 -0700 2008
merb / merb-core
| name | age | message | |
|---|---|---|---|
| .. | |||
| |
.gitignore | Sun Oct 12 19:17:19 -0700 2008 | |
| |
CHANGELOG | Sun Oct 12 19:17:19 -0700 2008 | |
| |
CONTRIBUTORS | ||
| |
LICENSE | Sun Oct 12 19:17:19 -0700 2008 | |
| |
PLUGIN_API_CHANGELOG | Sun Oct 12 19:17:19 -0700 2008 | |
| |
PUBLIC_CHANGELOG | Sun Oct 12 19:17:19 -0700 2008 | |
| |
README | ||
| |
Rakefile | ||
| |
TODO | Fri Jan 18 11:25:19 -0800 2008 | |
| |
autotest/ | Sun Oct 12 19:17:19 -0700 2008 | |
| |
bin/ | Sun Oct 12 19:17:19 -0700 2008 | |
| |
docs/ | Sun Oct 12 19:17:19 -0700 2008 | |
| |
experimentation/ | ||
| |
lib/ | ||
| |
merb-core.gemspec | ||
| |
spec/ | ||
| |
tools/ |
merb-core/README
merb-core
A new branch of Merb (sometimes referred to as merb-next) which aims to provide
a stable, stripped down API for the Merb 1.0 release.
This branch was based off the 0.5 release series 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

