Ok I admit , the screencasts and from what I have seen so far got me
excited. I am an experienced PHP, C++, Assembly, etc programmer.
I have been around this block many times. I know you need to "pay your
dues" before it "clicks".... ie. researching, tutorials, and awesome
answers from groups like this....
IN CONTEXT - Let's say we are talking about a site that caters to ,
ahm... roofers. Yeah, that should be a curve ball.
1. Am I understanding ROR correct ( high level ) where the index page,
the estimate page, the job page, etc should have it's own controller?
Have it's own view?
2. I read how ROR can magically map table names to classes. Cool. But
what about when I have a SQL statement on a page that contains a ton
of joins , group by, etc. ??
3. This one is really perplexing... I think I understand the app
"layout". But what if I want to include the same header, but with some
conditional logic in my css, such as "if we are on this page, then
make this button's class "xyz". ?
4. Lastly, regarding the "migration".... I must say, it looks cool,
but I cannot see how it would differ from someone like myself saving
multiple sql files with version numbers, and dropping my db and
creating a new one? Am I missing something?
Again... so excited!