Guys I wonder if you ever come across a guy called RSL.
telling ppl the first rule of programming is Its All Your Fault,
the codinghorror page enclosed.
I am very alleged
by him as he doesn't
present solution to people,
and indeed just try to insult people with
this ITS ALL YOUR FAULT MAN.
Even the comment which I think I have put
reasonable effort to discuss about scaffold problem, I am being
insulted on my blog.
I feel disappointed about such member in rails,
despite he did finally help on fixing a weird problem on my leopard
rails (for some reason the gem source for rubyonrails is being
Sorry if I try to write something a bit personal here, but I just feel
I should voice it out.
On Apr 9, 12:02 am, goodwill <william.yeung...@gmail.com> wrote:
> I come across this thread when I try to share my point of view about
> the new Rails 2.0 scaffold.
> Again like most of us, we dont disagree with the RESTful approach,
> despite the fact I haven't even totally understand that yet.
> There are a few issues involved from this new scaffold. From the
> different thinking approach direction- I personally think about the
> data setup first before I generate the scaffold, so usually I would
> just do a model generation first, then scaffold. The approach really
> has nothing wrong IMHO. So demolish this original way to work and then
> use the new one obviously would cause quite a bit people disappointed.
> Furthermore, indeed this new scaffold really have some issues one the
> URL handling. While the new active_resource approach creates great
> looking URL (especially when you look at the Akita On Rails tutorial
> on how the has_many thing works together on Post/Comments), but for
> example, to move the scaffold from root to a subfolder (i.e.
> namespace) would cost significant amount of work.
> I have listed the work required in my blog, you may have a look:http://bugthis.blogspot.com/2008/04/rails-20-hurts-on-scaffold.html
> I only hope there would have a more balanced solution patched in
> future version of rails.
Rather, it is an art. The discovery of how to express a thought within
the constraints of the medium chosen.
Posted via http://www.ruby-forum.com/.
Please understand that none of us are criticizing you and most of us
have felt similar frustration at various times with Rails and Ruby and
similar technologies. Nor are we saying that you should just "suck it
What you are being told is that your problem is ignorance. Now, do not
get upset at this because each and every programmer alive is far more
ignorant than they are knowledgeable. It is just that all of us possess
some small patch of intellectual property that we comprehend better than
anyone else and sometimes we imagine that patch is much larger than it
Rails 2.0 broke with its past and went down the road of ReST, taking
those of us who cared to follow along with it. The change to
scaffolding from 1.2 to 2.0 is one of the consequences of that decision.
It is not as simple as rewriting your own scaffold generator, it is a
matter of coming to understand that there is an entirely different way
of accomplishing what you wish to do than was previously the case.
The conceptual change that ReST presents can be hard to grasp,
particularly when one is familiar with a fundamentally different way of
accomplishing the same things. It is much the same as breaking from
procedural languages and coming to understand object programming. The
difference is profound but the all the evident distinctions are often
subtle and hard to appreciate.
Instead of immediately writing your own generator to do what you think
that you want, you are should reconsider how you would accomplish what
you desire within the new constraints of Rails 2.0. This, in the end,
will prove the more profitable and enlightening course. And that is why
the advice you have been given is essentially to reflect deeply on what
you are saying and how you might alter your approach to your problem.
The pain will pass if you persevere.
> I understand like most wizard feature, scaffold probably are just some
> code candy. But then it has been a helpful servant, so I still miss
> it. I won't give up rails afterall as its way lot better than PHP to
> me (I always feel dizzy trying to find out where to start on a php
> project, but rails is so natural to just find the controller which
> does the task I am concern about).
The scaffold is still there, in a sense, it just will not respond
dynamically to changes in the underlying table as in version 1.2. If
you simply want a quick and dirty admin form to do direct DB maintenance
then take a look at:
Is 90% of the people you encounter annoying you, because they think it's
someone else's fault? Then gtfo of the community, you're the minority.
You're pissing people off.
Learn Ruby on Rails! Check out the FREE VIDS (for a limited time)
VIDEO #3 out NOW!