Hi, One example of a change I've made in my vendor/plugins/activescaffold is the code posted here, i.e. my last post in the thread: http://groups.google.com/group/activescaffold/browse_thread/thread/36b9aa197b3aa332/1eccbd1e14cf0abe?hl=en#1eccbd1e14cf0abe
thanks in advance On Sep 12, 6:02 am, Sri Sri <[EMAIL PROTECTED]> wrote: > Greg, > > In AS terms, overriding means writing code in our own app/... folders. > You don't need to update the actual AS methods. I thought may be you > misunderstood the overriding part. > > Sri > > naaano wrote: > > i still don't have the need to change the core itself, so i'm > > interested in what you might be needing to change, since AS is very > > open to adapt many things, and i've been doing it widely. care for > > telling us? > > > On Sep 9, 7:04 pm, greghauptmann <[EMAIL PROTECTED]> wrote: > > >> bump (still interested if someone has an opion) > > >> On Sep 8, 9:16 am, greghauptmann <[EMAIL PROTECTED]> wrote: > > >>> Hi - mind if I double check the following. If I am overridding some > >>> ActiveScaffold code, and also noting I was to keep updating to the > >>> latest ActiveScaffold edge code periodically: > > >>> Should I move my changes from within the vendor/plugin code area to > >>> say the "/lib" area and make a ruby file with the model/class and just > >>> that method I'm overridding. Is this correct? Or should I learn > >>> about how ActiveScaffold plugins work and try to following this > >>> approach? (currently I've just modified the code in the "vendor/ > >>> plugin/activescaffold" area itself) > > >>> thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
