On Jun 7, 3:16 pm, frizbe1605 frizbe1...@gmail.com wrote:
Okay, I'm chaining methods. I want access to my class. I can access
SomeClass with a method like some_class. Now with engines in Rails
3.1, I can use modules to break apart my codebase. So now, SomeClass
would beEngine::SomeClass. If
If I call Engine::BlogPost everything is gravy,
If I call BlogPost then I get...
uninitialized constant BlogPost
On Jun 8, 11:35 am, Frederick Cheung frederick.che...@gmail.com
wrote:
On Jun 7, 3:16 pm, frizbe1605 frizbe1...@gmail.com wrote:
Okay, I'm chaining methods. I want access to my
Okay, I'm chaining methods. I want access to my class. I can access
SomeClass with a method like some_class. Now with engines in Rails
3.1, I can use modules to break apart my codebase. So now, SomeClass
would be Engine::SomeClass. If I try to access Engine::SomeClass with
a similar style method
On Tuesday, June 7, 2011 8:16:02 AM UTC-6, frizbe1605 wrote:
Okay, I'm chaining methods. I want access to my class.
Access your class as in: obj.class (or something else)?
I can access
SomeClass with a method like some_class.
Do you mean you can take a string some_class and call:
On Jun 6, 3:34 pm, frizbe1605 frizbe1...@gmail.com wrote:
EngineBlogPost == @blog.engine_blog_post
Engine::BlogPost ==
You might want to elaborate - to me at least your question makes no
sense.
Fred.
Thanks!
--
You received this message because you are subscribed to the Google
5 matches
Mail list logo