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 (
Run the following if you haven't already:
gem sources -a http://gems.github.com
Install the gem(s):
sudo gem install wycats-merb-core
commit f9b8d869671346f68f64c01db29106e0e56ed20c
tree 9244f3a93f5f83fcb6c4c95eb8df5803596fc5fe
parent 39973931efc14ed19445b64dc3ee4296e8c5b82f parent bdfa396c8c4c6dda7a9a4a3a7adaa30b8d39fb85
tree 9244f3a93f5f83fcb6c4c95eb8df5803596fc5fe
parent 39973931efc14ed19445b64dc3ee4296e8c5b82f parent bdfa396c8c4c6dda7a9a4a3a7adaa30b8d39fb85
| 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/ | Wed Feb 13 11:48:05 -0800 2008 | [wycats] |
| |
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




