On May 27, 11:42 am, Ed W <[email protected]> wrote: > Hi > > > Maybe it would be better to add a method add_active_scaffold_path > > which add a view path between active_scaffold_overrides and > > active_scaffold_frontends. > > I misread your suggestion on the other thread. I guess if the plugin > always overrides the main AS views then this covers 99% of situations > because the plugin is free to choose sensible names to avoid breaking > AS, but can still override AS if it's necessary. > > Yes, lets go with that solution then. Can I recommend that we have both > a getter and a setter so we can do introspection and also that the > setter burst the memoised value for the full pathlist so that we don't > get any bugs due to initalisation ordering?
Are those getter/setter going to be added to AS repository or something. I'm porting some old AS modules and I need them, but I don't want to duplicate code if it's already been worked. > Cheers > > Ed W Cheers --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
