Can you give me a link (or something searchable) so that I can read the
previous discussion?
thanks,
Bryan
Daniel Hahn wrote:
I've found a discussion about this from last August, and ran into the
same problem, so I wanted to see if there's any followup.
The point was that the automatic routing, surprisingly, does use the
*Model* class names and namespaces to create the routes. However,
since routes go to controllers, this makes it essentially impossible
to use a hobo controller with a model class of a different name.
I ran into that while trying to build an admin interface for an
existing set of model class, which, for this reason, doesn't really
work. I've already work around that, but it was a tad annoying.
While I saw that the previous discussion was successful to find a
solution for the original user, it wasn't conclusive on the problem
itself. As it is, I'd say the feature is broken for all but the
default case (ControllerName == ModelName).
I also haven't seen any reason why the routing is tied to the models
instead of the controllers. First, it creates additional dependencies
between the model and the presentation. Then all routing in Rails is
always to the controller classes and rewiring it appears to cause
pain.
My question is specifically if there are any plans to "fix" that, or a
fix is even wanted (say, if someone had a patch). Not quite sure if it
belongs here or on the dev list, but I took it here since there was
already a discussion on it.
Best,
Daniel
--
You received this message because you are subscribed to the Google Groups "Hobo
Users" 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/hobousers?hl=en.
