on 2005-12-13 13:55
on 2005-12-18 20:05
On 12/13/05, Ed W <firstname.lastname@example.org> wrote: > Like many people I am trying to experimenting with writing new apps in > Rails and having some teething problems getting my head around how they > should be structured to take best advantage for Rails. It's a question > of how to *structure* the app once you go more complicated than those > easy "Todo list" examples (and I do own the Agile books) Have you gotten help with these questions yet? > Thanks > > Ed W Sincerely, Tom L. email@example.com http://AllTom.com/
on 2005-12-18 21:11
Ed / Tom, I am having the same difficulties. I have coded PHP for a few years and various other languages. I love the idea of Rails and have purchased the Agile book and the PickAxe. I was so enthused about Rails that I read the Agile book in a couple of days. The walk-through application presents a lot of useful information but, I feel, that the authors should have presented the non-scaffolding approach to beginning a project in later chapters. What is really needed is for someone to write a book that walks through the development of a larger-scale application. I've been contemplating going to one of the Rails seminars that walks through the development of BaseCamp but that's quite a bit of moolah. Now, I know that I will need to learn Ruby to take full advantage of everything that Rails has to offer and I've been devoting most of my time to that task. I've read the Rails wiki and numerous tutorials, watched the videos and read numerous blogs. I know that a lot of books are in the works and hopefully one of these books will address the real-world approach to developing a larger-scale application with Rails. Am I alone in this confusion about the best starting place for a big application? -Chris
on 2005-12-18 21:56
I've been using Ruby for a few years now (our company built a decent sized web application for a customer before rails ever came out), but I've just recently started to work with Rails. Even I had trouble getting my head around Rails when I first looked at it (many months ago). The way I finally jumped over that small learning curve was to just start writting something. Following the 'todo' application tutorial didn't really teach me anything. It's when I started writting my own application (simple blog with Blogger and MetaWeblog api's, and a utility to track milage for my motorcycle) that it finally clicked. And once you have something working, make sure you write tests for everything... then refactor everything using the knowledge you've gained. No tutorial is going to teach you what you'll need in order to write a large scale application. Actually writting something, and (more importantly) writting tests for it, will teach you what you need to know. Ken...
on 2005-12-19 01:59
It is a long fall from the scaffolding into real world apps. Your best bet is to just dive right in and use the #rubyonrails IRC group for support. We're nice there, cause you know, Matz is nice. Matz is the true programmer and DHH is his prophet. ;-) Mike P.
on 2005-12-19 03:02
On Dec 18, 2005, at 6:59 PM, Mike P. wrote: > It is a long fall from the scaffolding into real world apps. Your best > bet is to just dive right in and use the #rubyonrails IRC group for > support. We're nice there, cause you know, Matz is nice. I have to second that sentiment. Our community is phenomenal! >>> enthused about Rails that I read the Agile book in a couple of >>> walks through the development of BaseCamp but that's quite a bit >>> approach to >>> developing a larger-scale application with Rails. >>> >>> Am I alone in this confusion about the best starting place for a big >>> application? Ruby was ahead of it's time when it came out. I think maybe it still is. There are still a lot of sideline critics out there. I think that this is the result of the fact that outside of the tutorials and scaffolding there are concepts in our world that take some mental effort to wrap your head around. MOst people are just not willing to spend two days "figuring it out." For me it's because Ruby (and thus Rails) forces you to think different. With concepts like Mixins and code blocks I feel compelled to code more elegantly and expressively. The PickAxe Book is my best friend. I use it a lot more than the Agile Web Dev book. Actually, I refer more to the RoR API than anything for how to do something in Rails. The DevBoi Firefox plugin is invaluable. So, I would suggest study the PickAxe book, lean heavy on the RoR API, and when you get stuck come and join us at #rubyonrails. Ciao! - Scott aka <unix_cat>