Ken Wagner wrote: >> Left out? What do you mean? Do you have a concrete example? >> >>> Then I spend hours testing, digging and reading. Maybe I am just >>> thick-headed. > > Yes. Take form_tag. Even on RailsBrain. Go to the top of the page. > > It doesn't tell you What and Why. What, exactly, is a form_tag? > > I gather it is some sort of a shorthand. Why? If the regular form usage > is too long then why not just get rid of it? Besides, what, exactly, is > a "tag?" A helper? An abbreviation? If we need "helpers", maybe, the > superclass is somewhat antiquated? Hmmm?
This is a matter of "prerequisite." The Rails documentation assumes you know HTML, CSS, JavaScript, etc. It does not attempt to teach HTML. If you don't know what an HTML tag is, then study documentation on HTML. The Rails API documentation is a reference not a tutorial. There are Rails guides for that sort of thing, but better yet there are books, and other related information designed to teach this stuff. There are certainly areas of the documentation that could be improved upon, and are being improved upon. But, most of us wouldn't want to see the Rails API documentation cluttered up with a bunch of non-relevant information such as explaining what a particular HTML tag is. -- 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 -~----------~----~----~----~------~----~------~--~---
