Hi All, I don''t think I saw this mentioned in the list yet: Ruby on Rails is making the top story at IBM developerworks site: http://www.ibm.com/developerworks The article itself is yet another tutorial going thru the building of a simple app with scaffolding. http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/ The ball keeps rolling! -- Eduardo Fernández Corrales
It would be nice if it wasn''t just more articles showing the same ball rolling in the same way though! sam On 6/16/05, Eduardo Fernandez Corrales <eduardo.fernandez-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Hi All, > > I don''t think I saw this mentioned in the list yet: > > Ruby on Rails is making the top story at IBM developerworks site: > http://www.ibm.com/developerworks > > The article itself is yet another tutorial going thru the building of > a simple app with scaffolding. > > http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/ > > The ball keeps rolling! > -- > Eduardo Fernández Corrales-- sam http://www.magpiebrain.com/
On 6/16/05, Sam Newman <sam.newman-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> It would be nice if it wasn''t just more articles showing the same ball > rolling in the same way though!I''ve got an opportunity to write some articles (mostly about Ruby, but I think I could fit Rails in). So far I''ve either published, written, or started articles about writing Ruby code test first, profiling and optimizing Ruby code, and debugging Ruby code. What Ruby or Rails topics would you like to see beyond these?> > sam > > -- > sam > http://www.magpiebrain.com/-- thanks, -pate ------------------------- We are often unable to tell people what they need to know, because they want to know something else, and would therefore only misunderstand what we said - the Raven (George MacDonald, Lilith)
On Thu, 2005-06-16 at 13:40 -0700, pat eyler wrote:> What Ruby or Rails topics would you like to see beyond these?Speaking as a newcomer to both Rails, Ruby and this mailing list, I''m probably the least qualified to answer this. But that won''t stop me :) I personally would like to see more indepth articles. What do I mean? Everything seems to show off scaffolding, and how that''s great to get started with, but my understanding is that you still have a long way to get before you have a web-app that looks good too :) Personally, a walkthrough that traces the same-old "addressbook" or "weblog" from start to finish would be good. Don''t just show scaffolding working and walk away - there''s got to be more to Rails than just that. Forget about telling us how to install and configure Rails, we can work that out from the other dozen tutorials that have sprung up on our Google search. Obviously this would be a hefty sized tutorial, so delivering it over several articles might work better. We could build the app up over a few weeks. Ohh, and "hi everyone". -- Thanks, Matthew Lambie Technical Director THE FRONTIER GROUP, PTY. LTD. Suite 17/44 Kings Park Road West Perth, WA 6005 Australia w: http://thefrontiergroup.com.au e: mlambie-1oeH2xJOviyE8ue59/1CjzSf8X3wrgjD@public.gmane.org f: +61 (08) 6263 4444 m: +61 408 866 997
On 16-Jun-05, at 5:06 PM, Matthew Lambie wrote:> Obviously this would be a hefty sized tutorial, so delivering it over > several articles might work better. We could build the app up over > a few > weeks.+1. It would be nice to structure the tutorial so that each subsequent article represented an iteration. At the end of each iteration (article), having ''working software'' would be a must. /Jeff
> Obviously this would be a hefty sized tutorial, so delivering > it over several articles might work better. We could build > the app up over a few weeks.Hey Matthew, I''m new to Ruby, Rails and even OO-programming, too. Since you''ve just joined us (welcome!), you may not have heard about Dave Thomas'' book, "Agile Web Development w/ Rails". I''ve read through the first three chapters and it contains what I think you''re looking for: a step-by-step process for building a full-blown Rails application. The book is obviously not offered as a free series of articles on a web site but (a) you can get it now[1] and (b) from what I''ve seen so far, it''s pretty complete weighing in at 500+ pages. [1] Dave''s blog should point you in the right direction for obtaining the Beta 2 version of the book: http://blogs.pragprog.com/cgi-bin/pragdave.cgi HTH, ..dean
On Thu, 2005-06-16 at 14:20 -0700, Dean Matsueda wrote:> > Obviously this would be a hefty sized tutorial, so delivering > > it over several articles might work better. We could build > > the app up over a few weeks. > > Hey Matthew, > > I''m new to Ruby, Rails and even OO-programming, too. Since you''ve just > joined us (welcome!), you may not have heard about Dave Thomas'' book, > "Agile Web Development w/ Rails". I''ve read through the first three > chapters and it contains what I think you''re looking for: a step-by-step > process for building a full-blown Rails application.I''d heard that Ruby hackers were a friendly bunch - thanks for reinforcing that :) I have heard of the pick axe book and it''s on my shopping list. Now this is too. July 4th isn''t too far away so I will get a copy of the paper book when it''s printed. Thanks again, -- Thanks, Matthew Lambie Technical Director THE FRONTIER GROUP, PTY. LTD. Suite 17/44 Kings Park Road West Perth, WA 6005 Australia w: http://thefrontiergroup.com.au e: mlambie-1oeH2xJOviyE8ue59/1CjzSf8X3wrgjD@public.gmane.org f: +61 (08) 6263 4444 m: +61 408 866 997
Matthew Lambie wrote:> I personally would like to see more indepth articles. What do I mean? > Everything seems to show off scaffolding, and how that''s great to get > started with, but my understanding is that you still have a long way to > get before you have a web-app that looks good too :)+1.... that''s EXACTLY what I''m looking to read right about now! I totally grok the scaffolding stuff, but I want to see a demonstration of it taken to the next stage. In fact, the title of the ideal article would be something like: "Rails: Beyond Scaffolding" But of course "write us an article" is rather a lot to demand, so I''m remaining hopeful albeit realistic. As it happens, I''m about to do this beyond scaffolding stuff myself anyway, but it would be good to have seen a demonstration of it first so I at least knew I was going the right way about it. One thing I do love about Ruby / Rails is that it''s really got me interested in my programming and thinking about my programming methodologies again. I also feel like if I had to design my ideal language, really knew what I was doing with language design, and also got a lot of trial and error to get it right, I''d probably be heading in the direction of Ruby but still wouldn''t manage to get it nailed as elegantly as Ruby does. It really is the nicest programming language I''ve ever encountered, and as far as I''m concerned is knee-tremblingly close to programmer''s heaven. I really do weep with joy at some of the code examples in the Pickaxe book... however nerdy that may be!! ;-) ~Dave (Ordering the Rails book tomorrow!) -- Dave Silvester Rent-A-Monkey Website Development Web: http://www.rentamonkey.com/
Well, since you asked: 1. Keeping Ajax accessible (what if the browser doesn''t support XmlHtpReqeust?) 2. Seperating rails models from the DB (or: introducing Domain Driven Design to Rails) 3. Supporting legacy databases (especailly important given the number of people porting existing apps to PHP) 4. How to scale Rails (or: what to do if your startup goes nuts overnight) If no-one else does it, I''ll be doing 2 and 3 - but right now I''m in the middle of educating Java and C# programmers in the merits of ruby (http://www.magpiebrain.com/archives/2005/06/13/java_to_ruby, http://www.magpiebrain.com/archives/2005/06/15/java_to_ruby2, http://www.magpiebrain.com/archives/2005/06/16/java_to_ruby3). Any chance of links to the stuff you''ve written? sam On 6/16/05, pat eyler <pat.eyler-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> On 6/16/05, Sam Newman <sam.newman-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > It would be nice if it wasn''t just more articles showing the same ball > > rolling in the same way though! > > I''ve got an opportunity to write some articles (mostly about Ruby, but > I think I could fit Rails in). So far I''ve either published, written, or started > articles about writing Ruby code test first, profiling and optimizing Ruby > code, and debugging Ruby code. > > What Ruby or Rails topics would you like to see beyond these? > > > > > sam > > > > -- > > sam > > http://www.magpiebrain.com/ > > > -- > thanks, > -pate > ------------------------- > We are often unable to tell people what they need to know, because > they want to know something else, and would therefore only > misunderstand what we said > - the Raven (George MacDonald, Lilith) >-- sam http://www.magpiebrain.com/
As a newcomer who''s now read a couple scaffolding tutorials, what I''d like to see is a conceptual overview: Here are the parts of Rails, here''s what they''re for, here''s how they fit together. The aim would be to leave the reader with enough of a mental framework for how Rails works that he could take it from there with just the API reference docs. Maybe something in a similar vein to the Ruby User''s Guide, though maybe a little more in-depth. Also, what is the Pickaxe book and where do I find it? --Dave
On 6/16/05, David Feldman <mailing-lists-fDpYTK8McCwok6x7qy236gC/G2K4zDHf@public.gmane.org> wrote:> As a newcomer who''s now read a couple scaffolding tutorials, what I''d > like to see is a conceptual overview: Here are the parts of Rails, > here''s what they''re for, here''s how they fit together. The aim would > be to leave the reader with enough of a mental framework for how > Rails works that he could take it from there with just the API > reference docs.this sounds like a bigger topic than a tutorial, but something worth having.> > Maybe something in a similar vein to the Ruby User''s Guide, though > maybe a little more in-depth. > > Also, what is the Pickaxe book and where do I find it?here''s the pickaxe http://www.pragmaticprogrammer.com/titles/ruby/index.html and here''s the ruby book you want http://www.pragmaticprogrammer.com/titles/rails/index.html> > --Dave > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-- thanks, -pate ------------------------- We are often unable to tell people what they need to know, because they want to know something else, and would therefore only misunderstand what we said - the Raven (George MacDonald, Lilith)
On 6/16/05, David Feldman <mailing-lists-fDpYTK8McCwok6x7qy236gC/G2K4zDHf@public.gmane.org> wrote:> As a newcomer who''s now read a couple scaffolding tutorials, what I''d > like to see is a conceptual overview: Here are the parts of Rails, > here''s what they''re for, here''s how they fit together. The aim would > be to leave the reader with enough of a mental framework for how > Rails works that he could take it from there with just the API > reference docs. > > Maybe something in a similar vein to the Ruby User''s Guide, though > maybe a little more in-depth.For the Rails side, you can get the beta book: http://www.pragmaticprogrammer.com/titles/rails/index.html> Also, what is the Pickaxe book and where do I find it?The pickaxe comes as a CHM file with the Ruby One Click Installer for windows. You can surf it at ruby-doc.org, or search google for ruby and pickaxe, you''ll probably find other flavors. http://www.ruby-doc.org/docs/ProgrammingRuby/> --Dave > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-- Bill Guindon (aka aGorilla)
On 6/16/05, Bill Guindon <agorilla-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> On 6/16/05, David Feldman <mailing-lists-fDpYTK8McCwok6x7qy236gC/G2K4zDHf@public.gmane.org> wrote: > > Also, what is the Pickaxe book and where do I find it? > > The pickaxe comes as a CHM file with the Ruby One Click Installer for > windows. You can surf it at ruby-doc.org, or search google for ruby > and pickaxe, you''ll probably find other flavors. > > http://www.ruby-doc.org/docs/ProgrammingRuby/that''s what I get for walking away before hitting submit... Pat''s link is to the new Pickaxe II - which I should have linked to, and strongly recommend. The above link is for the 1st edition, which is still a solid introduction to ruby, but not as comprehensive (or up to date) as the 2nd edition. -- Bill Guindon (aka aGorilla)
On 6/16/05, Bill Guindon <agorilla-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> On 6/16/05, David Feldman <mailing-lists-fDpYTK8McCwok6x7qy236gC/G2K4zDHf@public.gmane.org> wrote: > > > Also, what is the Pickaxe book and where do I find it? > > The pickaxe comes as a CHM file with the Ruby One Click Installer for > windows. You can surf it at ruby-doc.org, or search google for ruby > and pickaxe, you''ll probably find other flavors. > > http://www.ruby-doc.org/docs/ProgrammingRuby/ >This is the 1st edition though and describes Ruby 1.6. It''s worth shelling out the $ to get the second edition. Lots of new content and many language improvements.> > > --Dave > > > > _______________________________________________ > > Rails mailing list > > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > > http://lists.rubyonrails.org/mailman/listinfo/rails > > > > > -- > Bill Guindon (aka aGorilla) > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-- thanks, -pate ------------------------- We are often unable to tell people what they need to know, because they want to know something else, and would therefore only misunderstand what we said - the Raven (George MacDonald, Lilith)
On 17.6.2005, at 01:05, Matthew Lambie wrote:> > I''d heard that Ruby hackers were a friendly bunch - thanks for > reinforcing that :) > > I have heard of the pick axe book and it''s on my shopping list. Now > this > is too. July 4th isn''t too far away so I will get a copy of the paper > book when it''s printed.From what I''ve heard you won''t get the hardcopy in your hands before the end of July so I would recommend getting the beta book now. You''ll then get the dead trees version as soon as it''s off the press. //jarkko -- Jarkko Laine http://jlaine.net http://odesign.fi _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
Come to think of it, I wonder if what I''m looking for here is something similar to the PHP online manual. I''ve never needed to buy a PHP book because it strikes a good balance between tutorial and reference. I can look up functions quickly, but much of it is also laid out conceptually so if my question is along the lines of, "How do I do such-and-such?" I can usually find the answer, often just by looking at the table of contents. Definitely an ambitious undertaking but it might be a nice long-term goal. I''ll look at the Pickaxe and the other book and see if they fit the bill. Thanks for the links. --Dave On Jun 16, 2005, at 8:40 PM, pat eyler wrote:>> As a newcomer who''s now read a couple scaffolding tutorials, what I''d >> like to see is a conceptual overview: Here are the parts of Rails, >> here''s what they''re for, here''s how they fit together. The aim would >> be to leave the reader with enough of a mental framework for how >> Rails works that he could take it from there with just the API >> reference docs. >> > > this sounds like a bigger topic than a tutorial, but something > worth having. >
On 6/17/05, David Feldman <mailing-lists-fDpYTK8McCwok6x7qy236gC/G2K4zDHf@public.gmane.org> wrote:> reference. I can look up functions quickly, but much of it is also > laid out conceptually so if my question is along the lines of, "HowHeh, but the point with PHP is that, more often than not, you *need* to look up functions. At work I use PHP, and I cannot for the life of me remember the order of arguments. With Ruby, chances are less you''d require a function lookup. That''s not to say we don''t need a good tutorial/reference. Just that the rationale of having a "manual" sorta thing in PHP is justified. :-) -- Premshree Pillai http://www.livejournal.com/users/premshree/
Matthew Lambie wrote:> On Thu, 2005-06-16 at 13:40 -0700, pat eyler wrote: > > >>What Ruby or Rails topics would you like to see beyond these? > > > Speaking as a newcomer to both Rails, Ruby and this mailing list, I''m > probably the least qualified to answer this. But that won''t stop me :) > > I personally would like to see more indepth articles. What do I mean? > Everything seems to show off scaffolding, and how that''s great to get > started with, but my understanding is that you still have a long way to > get before you have a web-app that looks good too :) > > Personally, a walkthrough that traces the same-old "addressbook" or > "weblog" from start to finish would be good. Don''t just show scaffolding > working and walk away - there''s got to be more to Rails than just that. >Please not another Address Book or Blog app. There are plenty of tools already out there that can do that. I could cut and paste an address book together from my existing code base in less time than it would take to read the install docs for Rails. It seems to me, JMHO, that using Rails for a Blog app is a bit like using a cannon to swat a fly. A good example that would impress mature developers would be a ticket system that calcuates hours, generates a report on open, closed, in work tickets. Allows tickets to be assigned to a employee, tied to a client, and viewed historicaly for trends (how many tickets involved DSL outages in April?). Just using Rails for a week (got sidetracked already to other projects) I have the distinct feeling it would kick most other tools butt developing an app like that. DAve
On 6/17/05, DAve <dave.list-+JIuMJIPudMuIF41do6k7w@public.gmane.org> wrote:> Matthew Lambie wrote:> A good example that would impress mature developers would be a ticket > system that calcuates hours, generates a report on open, closed, in work > tickets. Allows tickets to be assigned to a employee, tied to a client, > and viewed historicaly for trends (how many tickets involved DSL outages > in April?). > > Just using Rails for a week (got sidetracked already to other projects) > I have the distinct feeling it would kick most other tools butt > developing an app like that. >It might be a lot easier to extend Trac - http://www.edgewall.com/trac/ -- sam http://www.magpiebrain.com/