So,
Many older tutorials (and books) suggested a method of working models
and relations like:
generate model, scaffold, migrate, check, migrate, check... (e.g. the
original blog-video and the depot tutorial)
That is all deprecated and replaced by... what?
How will the rewrites look?
What is the new preferred way of working?
I was quite comfortable with this way of working myself and I haven't
really found something to fill the void yet.
I don't want to sound critical. I would just love to get the scoop on
what has made scaffolding more or less obsolete in the eyes of the
core team.
My current guess is that I should start using the console more when
being interactive with models.
cheers.
Martin Westn
On Jan 5, 12:05 pm, "Thibaut Barrère" <
thibaut.barr...@...>
wrote:
> > All this about backward compatibility is all fine and good; but at the
> > very least i should get a deprec message instead of having to hunt
> > through the erb files in the vestigialscaffoldremnants that don't
> > work, re-rake, see that nothing changed, question my own sanity, then do
> > a Google search and come here. It doesn't make sense.
>
> I suggest to delegate the scaffolding to a plugin which specializes
> with this task, for instancehttp://activescaffold.com/.
>
> (yeah that doesn't answer the philosophical question for sure!)
>
> best wishes !
>
> Thibaut Barrère / LoGeek
> --
http://blog.logeek.fr- about writing softwarehttp://evolvingworker.com- tools for a better day
--~--~---------~--~----~------------~-------~--~----~
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
rubyonrails-talk@...
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe@...
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en-~----------~----~----~----~------~----~------~--~---
