Sorry reread you silly long elitest rant and just had to comment on one or two more things > > Umm... perhaps because long-time readers and posters on the forum assume > that you come to this forum to learn from people who have already > traveled the road you seem to be on... perhaps because restful routes > is a big thing in Rails, which happens to prefer convention over > configuration, and you seem to be thinking configuration, so perhaps a > redirect was in order...
I just wanted to test each page.. you know throw the url in the address to see if it looked right ..to see if it was throwing the right variables...it had nothing to do with a redirect or a link_to ... but the url in the address bar wasn't working and I couldn't find the answer on line or in "ruby cook book" The pic axe ruby book or in agile Web development ... I just wanted to know why it didn't work...thats it... But dude went off the deep end..and I asked him... just don't respond...but he did again... > > A great place for information is api.rubyonrails.org; another great > place is your own machine in the console window, and your development > log. Look in the dev log to see what the parameters are that your app > is receiving. Read the api (particularly the routing part) to better > understand that piece. When you used scaffold, did you just scaffold > the full deal (something like: script/generate scaffold person > last_name:string first_name:string ). That'll generate the controller, > model, views, routing - rake that migration then play with that basic > app - read through the generated code to learn how it all fits - it is > amazingly educational about the Rails conventions. Generally, if it is > hard to do, you're doing it wrong. Simple as that. DID YOU READ ANY OF THE OTHER POSTS!!!! I figured out the problem long before Marnen came along with his break down of my code...and thats the thing .... I had figured out why and I posted why so that if any other morons like me messed up route file with map.resources.... urls won't work right! I was trying to be helpful... > > I don't always agree with Marnen's opinions, and he does tend to state > things a bit strongly for my taste, but I do always read his posts. > Why? Because he knows more than I, and a hell of a lot more than you. > > But as your later posts have indicated, you are not interested in > learning from anyone more knowledgeable than you in Ruby and Rails, you > just want an answer to your 'user_loggin' question so you can write the > code your way, however against the conventions of Ruby and/or Rails it > might be. ?? did apple stick with Microsofts conventions?? does apple stick with flash conventions?? I could stick to ruby convention better if they didn't fricken change it every 8 months.... and just for the record I've programmed in ruby enough that I was one of the only people to find a naming convention foul up in the ror with Ruby 2.0 I had a model called test_drive for a car lot I was building a sight for and ruby turned test_drives from the DB to test_drifes instead of test_drives because its english converstion of lives is to life .. so drives was to drife.. and I'm sure I just got lucky finding that ..wasn't cuz I knew the Controller, model veiw theory, or ever looked at my output screens.. or looked at what error was returned.... But now I know...if I ever have a simple question...if it's answered here..It comes with a handy dandy type till your blue in the face ..greater then thow lecture on ruby conventions..no extra charge or nothing -- 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.
