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 2624aa7922df1fb786dc7f0bf73193dfb54e17c0
tree 65134fc12244e1227c61e3796cdaa8481b4ce11f
parent da6bdad7e0f9b94b0b995398f296878374d91c04
tree 65134fc12244e1227c61e3796cdaa8481b4ce11f
parent da6bdad7e0f9b94b0b995398f296878374d91c04
README.txt
== merb_radiant A try to move radiant on merb Merb is a framework equivalent to Action Pack. It can use Active Record. For generator we can use Rubigen, it s an extract of RailsGenerator. For this we will use: * Radiant trunk r742 * Merb (core and more) 0.9.0 * Merb helpers 0.9.0 * Merb ActiveRecord 0.9.0 * ActiveRecord 2.0.2 * Rubigen 1.2.0 The repository tree was build with: * Hoe (modified) generated skeleton * Merb application * Radiant source 1. Move Radiant base: * use plugins as gem: * radius 0.5.1 * highline 1.4.0 * rubypants 0.2.0 * use other plugins as ruby libraries: * redcloth * bluecloth * using active record: nothing to do * radius and other ruby libs: nothing to do * replace RailsGenerator with Rubigen (Radiant bin) * work on initializer * desactivate extension dependencies (first step we move only the base) * manage Controller and libraries using controllers * check routes management * work on views to replace Rails specific code 2. Replace extension system with gems: * first, activate gem with only code features * second, deal with extension providing assets








