Hi Marnen,

You'll probably unsurprised to hear that I ran into problems following
http://activescaffold.com/tutorials/getting-started. Let's take just
one:

Getting Started says:
=============================
2. Add this to your layout:

<%= javascript_include_tag :defaults %>
<%= active_scaffold_includes %>
=============================

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

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.
But I inadvertently lost the URL for those instructions.  I'd like
some kind soul to point me to them.

I posted these questions on 
http://groups.google.com/group/activescaffold/topics,
but its awaiting admin. approval before being displayed.  Hence this
post in this thread.

Any ideas are most welcome.

Regards,
Richard




On May 17, 5:36 pm, Marnen Laibow-Koser <[email protected]> wrote:
> RichardOnRails wrote:
> > Hi paving,
>
> > 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?
>
> Best,
> --
> Marnen Laibow-Koserhttp://www.marnen.org
> [email protected]
> --
> Posted viahttp://www.ruby-forum.com/.
>
> --
> 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 [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group 
> athttp://groups.google.com/group/rubyonrails-talk?hl=en.

-- 
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 [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en.

Reply via email to