> > No, this is backwards. The hosting application's user model will override > the engine's model. This is why you can override devise's views in your app. > You should be including a module from your engine into ApplicationController > if you want to add additional functionality to it. >
Mmm. I don't know if this is true in all cases. When I added the ApplicationController into my engine it broke things in the app that was using the engine because it seemed to override the apps ApplicationController. Then again it was 2:00 AM in the morning on a Sunday so maybe I was a bit loopy at that time. I think the safest thing to do at this point is to put my libraries in modules and then have the application include them. On a related note I remember a couple of apps used https://github.com/pivotal/desert as their plugin architecture and it was rather nice. IIRC it mixed in the desert classes with yours. -- 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.
