Laim Bee wrote:
[...]
> Yea I noticed this and now I'm leery about buying more books. Does Rails 
> break
> compatibility often?

It's not so much a question of breaking compatibility as of introducing 
better ways to do things.  Rails is constantly introducing new shortcuts 
and abstractions, so if you're using an old version's way of doing 
things, you may be working too hard.


> Do you have a link for the site? 

Um, you could have found it in about 5 seconds with Google.  I think 
it's http://guides.rubyonrails.org .

> The reason that I want to learn Ruby on 
> Rails is because I have developed a site in HTML/CSS. I want to add a 
> very simple blog type application that lets a user enter text and create 
> a blog (I know there are plenty of free blogging programs, but I want to 
> build something simple for myself). I would also like visitors to leave 
> simple comments. I figure this is a great project to learn and practice 
> the fundamentals. I also figure this is a good project to practice using 
> a database. Will these guides help me in this regard?

Probably.  But why don't you read them and find out?

[...]
> When I go into MySQL Administrator, I see the columns in my table.

Great.  Are you looking at the right database for the environment you're 
running in (test, dev, or production)?  If so, then just use your 
version control system (you *are* using one, right?) to roll back to 
before you generated the scaffold, and run script/generate scaffold 
again.
[...]
> Does a scaffold look at the columns and put in the appropriate field? 
> For example if it sees you have a column which is a string, will it 
> display a textbox then?

Yes.
[...]
> I originally started off using notepad++ but switched over to using the 
> ide when I had to jump into the dummies book and follow one of the 
> tutorials. I'll try going back to my editor. The thing I liked about the 
> IDE was that it's more visual and it's easier,

That's why I recommend something like KomodoEdit.  It is helpful without 
forcing your hand.

> but the easiness becomes 
> a handicap and when something doesn't work, you have more trouble 
> figuring out why.

Often true.  Some types of automated tools (HTML editors are another 
good example) are more helpful when you understand what's being 
automated.

> 
>>> Ruby 1.8.6
>>> and I believe Rails 2.2
>>> 
>> 
>> Why start off on an old version of Rails?  2.3.2 is current.  Use it 
>> instead.
>> 
> 
> Is there a command I can run to check what version I have?

rails -v will tell you what version will get put into a new app. 
script/about will tell you what your app is using.

> 
>> Best,
>> --
>> Marnen Laibow-Koser
>> http://www.marnen.org
>> [email protected]
> 
> Thanks!

You're welcome.

Best,
--
Marnen Laibow-Koser
http://www.marnen.org
[email protected]
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to