On 12 April 2010 15:07, RVince <rvinc...@hotmail.com> wrote:
> Seems the best solution is the straight OOP solution:
>
> class Y < X
> ...
> something = some_method
> ....
> end
>
I'd say it depends on whether Y really IS AN X. If not, but they have
similar roles, I'd say you're better of doing this:
class Z < ApplicationController
def some_method
...
end
end
class X < Z
...
end
class Y < Z
...
end
or more simply:
module Z
def some_method
...
end
end
class X < ApplicationController
include Z
...
end
class Y < ApplicationController
include Z
...
end
You could also instantiate an X controller, but depending on the method
you're trying to call, you may need to do a bit of setup (pass in the
request/response somehow so it can take over).
Cheers,
Andy
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-t...@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
