File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Ruby and the fly likes Rails plugin namespace strategy Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Languages » Ruby
Bookmark "Rails plugin namespace strategy" Watch "Rails plugin namespace strategy" New topic

Rails plugin namespace strategy

Wirianto Djunaidi
Ranch Hand

Joined: Mar 20, 2001
Posts: 210

I am interested to know what is the best namespace strategy in developing rails plugins to prevent collision. I know it is common theme in ruby development, but it seems to be much more important with rails plugins as it rely a lot of rails behavior and a lot of magic metaprogramming going on.

How can we make sure we are not stepping on each other toes?
Nick Plante

Joined: Sep 01, 2008
Posts: 13
It's certainly possible to create conflicts if unique module/class names aren't used. My advice would be to use nested modules in your plugin code to create a namespace. Then, in your init.rb hook, you can graft these methods onto ActiveRecord (or any other pre-existing piece of Rails) by referencing them thusly:

I agree. Here's the link:
subject: Rails plugin namespace strategy
Similar Threads
output of DTD Validation.
Top three (or more) plugins
Usage of CalendarDateSelect in Ruby
Rails plugin extension to rails app
What is Rails ?