massimodipierro71 at gmail.com
Tue Oct 20 19:51:55 CEST 2009
One more clarification to avoid confusion. Django has "admin" and it
is great. Web2py also has something called "admin" but that is not
apples to apples.
The closest thing to Django "admin" in web2py is called "appadmin" (it
comes with it).
For example consider the following complete program:
appadmin is a controller that comes with each web2py app and provides
a web based interface to the database, that can be customized at the
app level, and that inherits the layout of the app.
The Django "admin" can be customized more and it is designed for
users. It is very sleek. The web2py "appadmin" is designed for the
administrator not users, and allows you to insert DAL queries
web2py also has something called "admin" which has nothing to do with
Django "admin". It is instead a web based IDE including web based
tools for installing apps remotely, packaging apps, editing apps,
debugging, running doctests, etc. via the web interface.
On Oct 19, 4:54 pm, Emmanuel Surleau <emmanuel.surl... at gmail.com>
> > Django : very strong integration, excellent documentation and support,
> > huge community, really easy to get started with. And possibly a bit more
> > mature and stable...
> One strong point in favour of Django: it follows Python's philosophy of
> "batteries included", and features a large array of plugins. There are also
> numerous other add-ons created by the community.
> Also, it has a pretty great administration interface.
> It still manages to retain flexibility, but you're basically stuck with
> Django's ORM (which is OK for simple things) and templating language (which is
> OK as long as you don't need custom tags).
> > Pylons : more loosely coupled (imply: less integration), based on
> > "standard" components - which is both a blessing and a curse, specially
> > wrt/ documentation -, requires a good knowledge of Python and the HTTP
> > protocol to get started with. Very powerful and flexible but this comes
> > with a price...
> Haven't used Pylons, but the documentation has improved the last few years
> with the Pylons book (http://pylonsbook.com/en/1.0/), while still not being up
> to par with Django's. It has also a methodology for deployment, which Django
> decidedly lacks.
More information about the Python-list