From what I have read, Rails is not extending a special api to engines other than models, routes, and controllers. AS doesn't use any of these, it extends your existing ones.
We love patches that show how to make use of new rails features. However I think the current strategy works fine for what we're doing and Engines doesn't give us anything. Please prove me wrong. -Mike Ed W wrote: > Mike Gaffney wrote: > >> I don't think engines will help at all with the view paths. The issue is >> that rails doesn't have the idea of a "Generic View" eg that if you >> can't find a specfic _list.rhtml then you look in root view path >> directories. We're currently using the rails view paths but the patches >> are to add this "Generic" logic in. >> >> > > The way I read the engines stuff is that this is exactly what it does allow? > > >> I don't using an engine or a plugin makes a difference to your first two >> points. >> >> > > Never said it did. Just saying that some other useful features have or > will become part of rails and hopefully we can loose the code out of the > plugin? > > 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 -~----------~----~----~----~------~----~------~--~---
