You can now do:
from gluon import *
to import the entire API (except for request, response, session, and T,
which are on the "current" object).
I think something like this should get you code completion:
if 0:
from gluon import *
from gluon.globals import *
request = Request(); response = Response(); session = Session()
Perhaps others know a better way.
Anthony
On Sunday, January 15, 2012 7:59:51 AM UTC-5, glimmung wrote:
>
> Hi Alan,
>
> On Sun 15 Jan 2012 12:37:26 GMT, Alan Etkin wrote:
> > An open source integrated software for development with RAD and
> > support for web2py is being developed by M. Reingart here:
> > http://code.google.com/p/rad2py .He participates in this group, so
> > maybe he can explain in more detail the features of the project.
> >
>
> Thanks for that - definitely worth a mention.
>
> However, what I'm more focused on is being able to point people using
> their existing development tools towards some docs that they'll
> understand.
>
> I have a couple of files (one for models, one for controllers), with a
> great long list of imports and what have you to support the editing
> process, and I import from those files. It works fine for me, but it's
> not pretty, and it rather undermines Massimo's statement in the book
> that "web2py is trying to avoid the annoying characteristic of other
> frameworks that force the developer to import the same modules at the
> top of every model and controller" if I'm doing exactly that to support
> editing, even if the code is "dead" in production!
>
> In reality, I've been asked to give a short informal talk to a friendly
> group, but the intemperate nature of some of the negative comments
> about web2py makes me feel like an ambassador for web2py venturing into
> potentially hostile territory...
>
>
