wycats / merb-core
- Source
- Commits
- Network (60)
- Issues (0)
- Downloads (9)
- Wiki (3)
- Graphs
-
Tree:
92dcf72
commit 92dcf722b7e34f8562340b42ed9ada44201fea91
tree 67e69491ab02bf98b34347df1c0609c48736f106
parent 63aac504c23418b4c63f9f35b241061a256f0feb
tree 67e69491ab02bf98b34347df1c0609c48736f106
parent 63aac504c23418b4c63f9f35b241061a256f0feb
| name | age | message | |
|---|---|---|---|
| |
.gitignore | ||
| |
CHANGELOG | ||
| |
CONFIG | Sat Jan 12 13:30:36 -0800 2008 | |
| |
LICENSE | ||
| |
README | ||
| |
Rakefile | ||
| |
TODO | Sun Jan 13 17:50:05 -0800 2008 | |
| |
autotest/ | ||
| |
bin/ | ||
| |
deps/ | ||
| |
docs/ | ||
| |
lib/ | ||
| |
merb-core.gemspec | ||
| |
simple_benches/ | ||
| |
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 myapp # a "normal" merb app
$ merb-gen myapp --flat # a flattened app
$ merb-gen myapp --very-flat # a single-file app

