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 2668a7dc953d2b32f2a76e522988b9aefccc9d39
tree 80707e81f89d15df65d1cd4c38f298206a2cbda6
parent ecf073ffefe9b59d490f4ab3be2784ea8818b7fc
tree 80707e81f89d15df65d1cd4c38f298206a2cbda6
parent ecf073ffefe9b59d490f4ab3be2784ea8818b7fc
| name | age | message | |
|---|---|---|---|
| |
.gitignore | Thu Jan 31 17:06:29 -0800 2008 | [Yehuda Katz] |
| |
CONFIG | Sat Jan 12 13:30:36 -0800 2008 | [wycats] |
| |
LICENSE | Sun Jan 13 17:50:05 -0800 2008 | [ezmobius] |
| |
README | Thu Jan 31 08:34:10 -0800 2008 | [wayneeseguin] |
| |
Rakefile | Tue Feb 12 20:20:24 -0800 2008 | [dudleyf] |
| |
TODO | Sun Jan 13 17:50:05 -0800 2008 | [ezmobius] |
| |
autotest/ | Fri Feb 01 11:32:29 -0800 2008 | [Hampton Catlin] |
| |
bin/ | Mon Jan 28 22:12:40 -0800 2008 | [ivey] |
| |
docs/ | Fri Feb 01 11:31:17 -0800 2008 | [Hampton Catlin] |
| |
lib/ | Tue Feb 12 21:16:53 -0800 2008 | [Janne Asmala] |
| |
simple_benches/ | Tue Feb 05 13:41:08 -0800 2008 | [Yehuda Katz] |
| |
spec/ | Tue Feb 12 20:38:25 -0800 2008 | [ivey] |
| |
tools/ | Fri Feb 01 11:31:17 -0800 2008 | [Hampton Catlin] |
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, reference the /sample directory




