I notice you cannot access another controller method from a view, eg.
:action => "othersec/list"
is no good; the action must belong to the corresponding controller
That being the case, I might as well just have one controller, "main",
with methods like "list_that" and "list_this", ie, there is not much
point in defining a controller for each table -- all that is needed is
class definition in models/
However "what seems to be the case" to me is not necessarily the way
that it is -- I'm worried I may diverge too much from anything
resembling *Best Practices* here, particularly since this means going
script/generate controller this
then erasing everything but the model definition (I tried erasing those
two, and creating one "main.rb" with all the classes in, but then there
is an error).
Anyone have any thoughts on this? After a bit of googling I found some
stuff about inheritance governing this -- does that mean I should put
the methods I want globally accessible in