Thanks very much for your response to my complaint about lack of Rails
support for handling changes.
Bottom line: I think you've shown that the approach I wished Rail's
offered is, in fact, at hand. I'll try it today!!
What you keep talking about wanting to do is impractical for an
automatic procedure.
I accept your assessment about impracticality of automated updating of
scaffolding in the general case.
However, I'm focused on apps in early stages of development after
scaffolding and migration. After making changes to a table in the
database, complementary changes in the Rails implementation are
limited to four files in app\views. They have a straight-forward
pattern that are susceptible to analysis by one or two regexp's per
views That lets me present an abstract layout that I can modify and
supplement with new code. That can be feed to a generator for each of
the views.
delete the existing view files and generate the scaffolding again.
Wow! I thought of trashing the current state of the whole thing, but
rejected it because it was too tedious and boring.
Thanks very much for your response to my complaint about lack of Rails
support for handling changes.
Bottom line: I think you've shown that the approach I wished Rail's
offered is, in fact, at hand. I'll try it today!!
What you keep talking about wanting to do is impractical for an
automatic procedure.
I accept your assessment about impracticality of automated updating of
scaffolding in the general case.
However, I'm focused on apps in early stages of development after
scaffolding and migration. After making changes to a table in the
database, complementary changes in the Rails implementation are
limited to four files in app\views. They have a straight-forward
pattern that are susceptible to analysis by one or two regexp's per
views That lets me present an abstract layout that I can modify and
supplement with new code. That can be feed to a generator for each of
the views.
Why not try ActiveScaffold, as I suggested in an earlier post?
Mea Culpa: I thought you were talking about Rails' scaffolding. I
didn't realize Active Scaffolding was "Scaffolding on Steroids"
Thanks for suggesting it again.
Regular scaffolding didn't work out as simply as I naively thought,
i.e. I couldn't just invoke with a list of a dozen fields and have it
create any thing close to what I already have.
For the moment, on the basis of a fast scan of the docs, it looks
like a promising tool for doing things like Frank Sinatra, i.e. "my
way". I'm trying out this evening.
No matter what, this has been a beneficial odyssey for my Ruby/Rails
growth.
I've got a bunch on layouts in app\views\layouts, in particular:
- expenses.html.erb, where I'm particularly interested in handling
with Active Scaffold
- standard.html.erb, which sounds important but I'm not aware that my
app uses it
- some-other-file-I-know-of
Okay, so what's the problem?
One other question: I stumbled on an alternative guideline on the
A.S. website for employing Active Scaffold functionality. This
guideline offered macros for insert A.S linkages into a Rails app.
What do you mean?
But I inadvertently lost the URL for those instructions. I'd like
some kind soul to point me to them.
Thanks for suggesting it again.