I decided to create a Rails engine to move a lot of commonly used
models, helpers, and even gems into a gem I can include in my rails
apps.  Most things are working OK but I can't seem to make a shared
ApplicationController which can be re-opened by the app that us using
the gem.

I am also running into some issues with re-opening modules for some
reason so maybe the two issues are related.   For example...

I add the xebec gem as a dependency to my gem/engine. xebec requires
that I put "helper Xebec::NavBarHelper" into my ApplicationController
so I create a file in the engine like this.

/app/controllers/application_controller
class ApplicationController < ActionController::Base
  helper Xebec::NavBarHelper
end


When I do this nothing happens the controller code is not being
called. So I require the file explicitly in my gem but then all the
helpers in the application_helper of the parent app go away.

I think one way to solve this problem would be for the parent
ApplicationController to inherit from this one but I am wondering if
there a better way to deal with.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" 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/rails-oceania?hl=en.

Reply via email to