Roys Gmail wrote:
> The best documentation is the source. Also read up on rack. Then your preferred templating and database libraries.
>
> Keep in mind that the subtitle for Ramaze should be "No magic, just ruby". Which probably explains why there are not books about it. You're free to do your app the way you want to, not artificially bound by the framework (there are no this goes here and that goes there expectations, instead you just use ruby to get the job done).
OK, sure. But aren't there some things that people have found work well
or better then other things?
I don't see how reading the source gives you a suitable big picture
about actual use and application of the code.
Any way, there's this:
http://ramaze.net/documentation/index.html
James
--
jamesbritt.com - Live curious
justthebestparts.com - Feed your head
neurogami.com - Hack your world