On Sunday, June 12, 2011 02:06:45 pm Wolfgang Keller wrote: > Hello, > > > It also includes the ability to bind GUIs created using traditional > > means (ie. standard PyQt calls or Qt Designer) to models so that > > those models are automatically updated by the GUI and vice versa. > > Would dip be suitable (i.e. make it easier than "naked" PyQt) to put a > GUI onto a bunch of SQlAlchemy objects?
I am actively working on a project (https://bitbucket.org/jbmohler/qtalchemy) to make form creation from SQLAlchemy-based models easy. The models are augmented by non-persisted column declarations for virtual columns (or entire non-persisted models). I believe that SQLAlchemy with PyQt offer a very compelling combination for writing line-of-business apps as rapidly as specialized tools, but with less limitations. QtAlchemy is still in a very early stage and API refinement is continual, but check my other bit bucket repositories for examples of functional applications which use it. In addition, you may be interested in http://www.python-camelot.com/ . The stated goals of Camelot and QtAlchemy are the same, but I was put off by Camelot's heavy use (as I understood it) of auto-generated forms. I'd rather see a stronger library encapsulating logic rather than auto-generated stuff. Yes, this is a shameless plug for QtAlchemy. Joel > > TIA, > > Sincerely, > > Wolfgang _______________________________________________ PyQt mailing list [email protected] http://www.riverbankcomputing.com/mailman/listinfo/pyqt
