On Wed, Mar 20, 2013 at 6:35 AM, <jle...@socit.co.uk> wrote: > Thank you for the suggestion, yes of course I would have given up years ago > without RBs fantastically clear material. > > However edit multiple does not work on multi-level nested attributes. Yet > edit a single multi-level nested attribute (using update_attributes) works > fine. > > My main point is that of newcomer accessibility. TDD may make a development > more agile but there is nothing better than an example app that exercises > all the simple/minimum/core functionality and use-cases. > > Just how long do you think it would take a true expert involved in edge > rails development to write a small app ? > > I suspect that it does'nt exist because it is too hard to do. > > Another point is that an example app is like a picture being worth a > thousand words. It proceeds the documentation lag and displays a best > practice approach that is clearly comprehensible by a much broader ability > level. > > I would gladly write one and give it back to the community if I could get it > all to work and if I was sure that my approach was in line with the current > version of rails best practice. > > An example app should execute without error and be a minimum requirement > before a new release is issued. This is another example where TDD has > pushed out verifying the basic use-case requirements. > > Sorry if this sounds like a rant but I am almost at the end of my tether > after giving up on rails 2.x, starting again on 3, and again on 3.2 and now > on 4.0.0.beta1. Rails is becoming so agile that you are lucky to complete > an application before the next version is released. > > Just one last time - can anyone knock out a simple app displaying core > use-cases I have highlighted ? > > > On Monday, 18 March 2013 19:32:57 UTC, jle...@socit.co.uk wrote: >> >> Hi All, >> I have 30 years as a self employed software engineer and have been >> experimenting with rails for several years but !! >> >> I would have made considerably more progress and been able to give back to >> the community if only there was a demo application that was released with >> each new rails release. >> >> I am sure that it would take no more than 15 minutes of someone within the >> core team to produce an app that provides just the basic of use cases: >> >> Edit of multi-level nested attributes in a single form. >> Edit several models on the same form. >> Edit multiple records from a single model on the same form. >> Basic authentication. >> Digest authentication. >> >> What do you think ? >> >> P.S. On ubuntu using rvm Ruby 2.0 and Rails 4.0.0.beta1 and Ruby Mine >> 5.0.2 the installation of each went without any problems. I just cannot >> find how to implement the simple examples listed above with Rails 4. >> > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to rubyonrails-talk+unsubscr...@googlegroups.com. > To post to this group, send email to rubyonrails-talk@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msg/rubyonrails-talk/-/2MHp73ESuvAJ. > > For more options, visit https://groups.google.com/groups/opt_out. > >
Sounds like it could be helpful. Go for it! -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.