Also, note that one advantage of having a "default" controller (which doesn't necessarily have to be named default.py) is that you can use the URL rewrite system to exclude that controller name from URLs, making your URLs a little shorter/cleaner. You can also exclude a default function within each controller. So, instead of /myapp/default/index, you would just have /myapp.
Anthony On Friday, September 13, 2013 8:14:17 AM UTC-4, Niphlod wrote: > > a controller is just a file. That file holds every function that > "generate" a page. > That being said, it's just how you lay out your url-scheme that usually > decides what controller to use: > > /appname/controllername/functioname > > in the end is the url where to retrieve the infos. > > On Friday, September 13, 2013 1:56:39 PM UTC+2, Andreas Wienes wrote: >> >> Hey guys, >> >> this is maybe a dumb question, but I'm asking myself, when I should use >> other controllers the "default.py". In the tutorials and the web2py-book >> the default-controller is used most of the time and every action is placed >> inside it. I assume to split my code into logical parts, so if I work with >> "project", "task" and "client" for instance, I have one controller for each >> of them, containing there relevant actions. Am i right? >> >> Again thanks for your help. >> Andreas >> > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
