[nlug] extending functionality of rails, components v plugins.. merits of both

From: andrewmcelroy (Yeah, right)
Date: 03/16/06

  • Next message: Paul Boniol: "[nlug] Re: [OT] Perl and SQL Server Stored Procedure"

    I was wondering what is considered better pratice when trying to add new functionality to ruby on rails.
    I was really excited about the acts_as_threaded plugin that I saw at railstie, but the helper file that
    does all the formatting is partly obscured in the video. Since there is no real documentation on
    any of the rest of the code, it makes it impossible to completly "follow along". Granted I
    can simply write my own helper file, but that's aside the point.

    The question I have is of those of you all who work with ruby on rails, have you ever extended
    functionality of rails, and if so were you more inclined to do it as a component or as a plugin, and why?
    There does not seem to a rule of thumb as when to use which.

    Thanks,
    Andrew

    -- 
    Send all requests to:  Yeah, right
     Put your command in the SUBJECT of the message:
       "subscribe" or "unsubscribe"
    Quick unsubscribe: <mailto:Yeah, right?Subject=3Dunsubscribe>
    Mailing list archives may be found at: <http://www.nlug.org/mail/>
    **********************************************************************
    This list is from your pals at NetCentral <http://www.netcentral.com/>
    

  • Next message: Paul Boniol: "[nlug] Re: [OT] Perl and SQL Server Stored Procedure"

    This archive was generated by hypermail 2.1.6 : 03/16/06 CST