Re: [PyQt] ANN: dip v0.3 Released
On Monday 13 June 2011 20:17:56 Hans-Peter Jansen wrote: > On Monday 13 June 2011, 10:12:03 Phil Thompson wrote: > > On Sun, 12 Jun 2011 20:06:45 +0200, 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? > > > > Having thought about this a bit more... > > > > No, but it's an interesting idea and may not be too difficult to do. > > I'll > > think about it a bit more... > > As an aside, SQLAlchemy is the most advanced and therefore popular SQL ORM > in the python world today. It would raise the "out of box" value of dip > greatly. > > I could imagine, that there's a need for a SQLAlchemy PyQt integration > module (QSql replacement) as a glue layer in between. > Not really, I've used sqlalchemy as is with pyqt before, just sub-classed a non sql model and used it as it's datasource for the model. I do think that intergration would be better, atleast for the areas of caching and pagination. But as it stands now, it's not bad. Mike ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] ANN: dip v0.3 Released
On Monday 13 June 2011, 10:12:03 Phil Thompson wrote: > On Sun, 12 Jun 2011 20:06:45 +0200, 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? > > Having thought about this a bit more... > > No, but it's an interesting idea and may not be too difficult to do. I'll > think about it a bit more... As an aside, SQLAlchemy is the most advanced and therefore popular SQL ORM in the python world today. It would raise the "out of box" value of dip greatly. I could imagine, that there's a need for a SQLAlchemy PyQt integration module (QSql replacement) as a glue layer in between. Lots of hand waving, I know. Pete ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] ANN: dip v0.3 Released
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 listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] ANN: dip v0.3 Released
On Sun, 12 Jun 2011 20:06:45 +0200, 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? Having thought about this a bit more... No, but it's an interesting idea and may not be too difficult to do. I'll think about it a bit more... Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] ANN: dip v0.3 Released
On Sun, 12 Jun 2011 20:06:45 +0200, 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 don't know - I've never used SQLAlchemy. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] ANN: dip v0.3 Released
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? TIA, Sincerely, Wolfgang -- Führungskräfte leisten keine Arbeit(D'Alembert) ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] ANN: dip v0.3 Released
dip v0.3 has been released and is available from the usual place. This release includes the dip.automate module and the dip-automate script. These allow the automation of dip applications, and ordinary PyQt applications for testing, debugging and demonstration purposes. 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. In previous versions you had to use the declarative UI features of the dip.ui module to do this. An introduction to dip can be found at... http://www.riverbankcomputing.com/software/dip/intro Documentation can be found at... http://www.riverbankcomputing.com/static/Docs/dip/index.html Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
