this has been on my list of things I want (or think maybe I want) for ... a while.
Basically, I couldn't justify an sqldesigner app because of two things - one of them being
the global routes which sqldesigner seems to (really) need for at least 2 purposes.
This kind of admin / helper app would then require routes.py at a global level for every
installation, which just isn't acceptable.
The second problem (Massimo) that sqldesigner showed, which I haven't thought of yet:
- the 3rd party (sqldesigner) static source contains a link to it's own documentation / help
within that static tree, and the generated link always fails (the implicit "index.html" for the
directory is omitted from the link). Historically, this is common enough practice in static web pages
that we should think about how to accomodate this in web2py.
It will be important for porting static pages to dynamic web2py use - all static
should work first, then pieces replaced w/ dynamic functionality - so this last part
seems like a basic pre-requisite.
P.S. - Robin - let me know if you start on a patch for routes; I may eventually, but will announce on list if / when I start work on it; my todo list is a mile high, so it may be a while.