Andrew Roth wrote: > Rails 2.3 has engines support built in: > > "# Engines: Share reusable application pieces complete with routes > that Just Work, models, view paths, and the works." > > Could ActiveScaffold be restructured to take advantage of that? >
This was my first thought also. Actually, probably not that much changes in terms of the actual code compared with now, but it might mean that support for inheritable paths for views etc finally requires far less code and tweaking with rails internals. I haven't looked at AS internals for a few months now, but right now the following seems to be a help - Rails tracks modified models and fields, so we can stop tracking that internally - Rails 2.3 is supposed to support directly updating related models. However, I can see a number of issues arising to do with the allowed attributes. Haven't looked too closely - Engines support would appear to simplify the view paths overrides Good luck Ed W --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ActiveScaffold : Ruby on Rails plugin" 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/activescaffold?hl=en -~----------~----~----~----~------~----~------~--~---
