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 bf38f7948cdcb9a05a1177604d80b87558777987
tree ef98abc73a26ebb068bbb8074e1869224cd49d5a
parent 66e0e524e72106234051371b859912befff7f670
tree ef98abc73a26ebb068bbb8074e1869224cd49d5a
parent 66e0e524e72106234051371b859912befff7f670
| name | age | message | |
|---|---|---|---|
| |
.gitignore | Thu Feb 14 09:16:02 -0800 2008 | [tdreyno] |
| |
CHANGELOG | Fri Feb 29 20:53:30 -0800 2008 | [ivey] |
| |
CONFIG | Sat Jan 12 13:30:36 -0800 2008 | [wycats] |
| |
LICENSE | Sun Jan 13 17:50:05 -0800 2008 | [ezmobius] |
| |
README | Thu Feb 14 08:28:57 -0800 2008 | [ivey] |
| |
Rakefile | Mon Mar 03 20:00:18 -0800 2008 | [lsegal] |
| |
TODO | Sun Jan 13 17:50:05 -0800 2008 | [ezmobius] |
| |
autotest/ | Fri Feb 29 08:57:47 -0800 2008 | [ivey] |
| |
bin/ | Fri Feb 29 08:57:47 -0800 2008 | [ivey] |
| |
deps/ | Fri Feb 29 13:50:54 -0800 2008 | [ezmobius] |
| |
docs/ | Fri Feb 01 11:31:17 -0800 2008 | [Hampton Catlin] |
| |
lib/ | Tue Mar 04 13:14:47 -0800 2008 | [ezmobius] |
| |
simple_benches/ | Mon Feb 18 19:19:26 -0800 2008 | [wycats] |
| |
spec/ | Tue Mar 04 12:36:35 -0800 2008 | [ezmobius] |
| |
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,
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




