The current implementation of SQLFORM is nice for rapid prototyping, but the confines of SQLFORM do not work when dealing with ajax, lots of javascript controls, custom html, complicated forms (like word orders etc..).

A new form system would need to allow easy ajax integration, it can include reasonable defaults, but customization is the key.

the web2py book REALLY needs a plugin section. "here's how they work, what a plugin is, how you use it, how you create your own" etc.

BigTable is not like relational database, then sometimes we get lost or design inneficient apps.
Let´s compile the knowledge!

what do you think of having routes.py for each app? I think each app should be the "owner" of its URL.

example: if I create a wiki app and this app has its own routes.py then the user that install this app doesn't need to modify the "root" routes.py

Requires some API that queries the DB for existing tables, make a guess about mapping SQL field types into web2py types, returns some dict-like representation of the DB.

It would be nice to have plugins listed on the app admin screen and they could be sorted by catagory, popularity, votes, and so forth. then when an app is created or exisitng someone could easily select or remove the plugins. We could even have a tool that could search for it's uses when removed and warn about it.

I think this is the most important thing missing from web2py impressive feature list.

Support to use an inline table in the FROM field of a query, as described here: http://groups.google.com/group/web2py/browse_thread/thread/8d50fd87d0f2e233

Sometimes I need a small popup form which does not refresh the page. Would be great if SQLFORM somehow supported this use case.

There needs to be a good way to backup Google App Engine datastores... Even a tutorial on how to set this up on web2py would be great.

http://code.google.com/appengine/articles/gae_backup_and_restore.html

Often I have errors when migrating between databases because of different reserved words.

Would be good to have a central location where people can post jobs with an RSS feed.

Python's package index is a place a lot of people go to find things, and it is a very mature repository. Web2py deserves to be there.

Hello,
would it respresent a lot of effort to extend the DAL functionality to
spatial capabilities?

Examples can be found here:

* http://www.geoalchemy.org/tutorial.html#performing-spatial-queries
*
http://docs.djangoproject.com/en/dev/ref/contrib/gis/tutorial/#spatial-queries

Where could we start?

It would be nice if I could click on a file name on an error message, for example, and it would open my file in my favourite editor using the backend webserver. It would make opening and editing my various applications a make quicker process.

Would be helpful if a default index was created for ID because I often forget to do this.

Add block tag support to the web2py templating system. {{block hi}} {{endblock}}