[PyQt] Re: RAD with PyQt?

Alberto Berti alberto at metapensiero.it
Sun Jun 15 15:15:12 BST 2008

>>>>> "David" == David Boddie <dboddie at trolltech.com> writes:

    David> On Thu Jun 12 11:11:46 BST 2008, Alberto Berti wrote:
    >> I forgot to mention that:
    >> dev news are at http://www.pypapi.org/rdg/timeline and source
    >> code and changes browser is at
    >> http://www.pypapi.org/rdg/browser .

    David> Does this project share some of the same goals as PyDADL?

    David>   http://pydadl.sourceforge.net/

Not really, from what i can say looking at PyDADL's tutorial, it is a
framework for building "rich xml clients", with a runtime that
marshalls and unmarshalls data and events to http/xml, with gui
composed by customized widgets. It's  sort of a web application
framework which uses a runtime different from standard browsers.

Compared to this, PyPaPi is an application framework in a more
"classic" meaning. Its role is to make standard python objects
hierarchies viewable and editable using standard Qt widgets, the same
you use to build forms in Qt Designer (really, Qt Designer _is the
preferred way_ to build forms in PyPaPi). PyPaPi then goes further and
offers support and more features if your objects are persisted using
SQLAlchemy (it then supports a wide range of RDBMS backends).

In PyPaPi, an application is a standard pyqt application, which runs
on the client with (if needed) a classic db connection (it is not
three tier), the only xml used are for form description (.ui files
made by designer) and for configuration syntax.  Our thoughts are that
with modern vpn technologies, all the xml rich clients fashion loses
most of it's meaning, and we do love writing python, not xml.

For who asked for pypapi docs, i'm preparing a tutorial (still to be
finished) that shows some PyPaPi features: it's here

any comment is welcome:)


More information about the PyQt mailing list