On Tue, Jan 10, 2012 at 6:21 PM, amir e. <[email protected]> wrote:
> >> > > Study "Rails Guides" http://guides.rubyonrails.org/ > > * Getting started > > * Migrations > > * check for "generators" > > * ... > > > > HTH, > > > > Peter > > I study it , and if I didn't understand. > OK, great. A good way to get better responses on a mailing is to mention e.g. "what did you read", "what did you try", "what was the outcome", "why do you think that is not correct" etc. E.g. from this guide: http://catb.org/~esr/faqs/smart-questions.html " Before You Ask Before asking a technical question by e-mail, or in a newsgroup, or on a website chat board, do the following: Try to find an answer by searching the archives of the forum you plan to post to. Try to find an answer by searching the Web. Try to find an answer by reading the manual. Try to find an answer by reading a FAQ. Try to find an answer by inspection or experimentation. Try to find an answer by asking a skilled friend. If you're a programmer, try to find an answer by reading the source code. When you ask your question, display the fact that you have done these things first; this will help establish that you're not being a lazy sponge and wasting people's time. Better yet, display what you have learned from doing these things. We like answering questions for people who have demonstrated they can learn from the answers. " Hope This helps and welcome :-) Peter -- Peter Vandenabeele http://twitter.com/peter_v http://rails.vandenabeele.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.
