well, I think he didn't made it clear but I see many ways: - create a component for web2py that instead of generating the html/ css/js source you use to see it in a website, it would generate the GUI application (controllers+view) as well as linking it to a shared model. This is a lot of work but would be awesome...
- create an independent app that communicate with web2py just like you mentioned. - bind a Qt interface to the same hooks currently used by the web interface that allows you to do pretty much everything web2py supports. One idea would be to put the admin application with a native look and extend, in example, monitoring properties (graphs, stats, plots). Qt is good for that. - web 6.0 - my idea (not so web2py specific, but appliable) best regards On Jan 21, 12:03 am, Stefaan Himpe <[email protected]> wrote: > Hello, > > It's not clear to me how you would combine PyQt (or PySide) with web2py > in the same application, it doesn't seem to make much sense to me. > > Provided you could actually make this work, a PyQt UI embedded in a > web2py application would only be visible on the server (e.g. some google > data center), not on the client (user of the web application). > > Of course I could have misunderstood: you could make a PyQt UI that > requests services from a web2py web application using xmlrpc. > In that case both applications are completely separate from each other. > > If you want to make both a web and desktop version of the same > application (e.g. a bug database that can run both in your web browser, > or as a standalone desktop program), perhaps pyjamas is something worth > looking at:http://pyjs.org/ > > Best regards, > Stefaan.
