Admittedly, splitting a lot of the functions into a module would be the best solution.
We recently had the same challenge, and moved a bunch of functions from our default controller into their own functions, without having to change frontend calls. This only worked because the functions were in the default controller, which was hidden in URLs by default. Function "whatever" in default.py became function "index" in whatever.py. so any call to website.com/whatever still worked Alternately, you can move the support functions into a model file(s) that only gets loaded for that controller. On Wednesday, 21 August 2019 21:45:38 UTC+1, clara wrote: > > Hello, > > Maybe this may sound trivial (bear with me, please) but here is my > question: I have a long controller module that I would want to split up or > make more manageable . Most of the functions in this controllers are > controller functions called from the frontend. > > Now, I guess I could refactor the module and have some support functions > and create a new module in the "modules" folder. This has brought me > problems in windows environment, so I would try to avoid it. > > I could create other controller modules and move some controller functions > to them, but then I would need to update the frontend ajax calls. > > Any ideas? > > Thanks in advance. > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/d69eef3d-cac8-4a9f-9c91-468cc7ab766a%40googlegroups.com.
