Okay sure, you can make it simpler, but you still have to type a bunch of
stuff when you are making a controller.
And now that we have 'set :views' I think it comes with to add the other
stuff because you immediately think, oh well then I can set controllers to
right? But you can't. That was
Hey,
a few days ago I was having a hard time splitting up my controllers in to
different folders.
With views you can just do:
set :views, *path*
in the module App
I think it would be nice if we could do the same thing for controllers,
models and helpers and whatever.
like:
set :controllers,
What I am doing now is basically the same as requiring. If I do require
with all the files, they don't become a part of the controllers module.
The problem is that having to require (or in my case 'add') ever
controller is *not* a very good way to work. It would be much better to be
able to just
Sure, but say that you want to have lots and lots of controllers, I don't
think anyone wants to sit there and write a module for each one to be
honest.
And with that way of thinking we shouldn't even be able to set :views. We
would have to write a module App::Views for every view.
set :views is
4 matches
Mail list logo