On Mon, Sep 27, 2010 at 2:08 PM, Lacko Roman <[email protected]> wrote: >> What about Qt Designer and other tools? Are they really necessary for >> PySide users? > > We must differentiate between the developers (users of "PySide Package") and > end-users (users of the "PySide Application"). > > Deployment for developers (the "PySide Package") must containt all the > necessary tools, including Qt designer. > > Deployment for end-users (the "PySide Application") is something different. > I can write some simple HOW-TO about deployment of "PySide Application" to > end-usres (under Windows), when i have time...
Sorry, Roman, I've mistaken your name and surname. But to me it still seems that PySide-x.x.x.zip package and PySideDev-x.x.x.zip packages is a viable compromise, especially if PySideDev will be marked optional. Many small packages like CuteHg are not built for Windows and work from Python site-packages - http://bitbucket.org/bfrog/cutehg/wiki/Installing Others are built with Distutils which AFAIR can't bundle multiple packages. Another example is Leo Editor that is installed with NSIS, but can work with either Qt or Tk, preferring Qt if it is installed. I wonder what is the minimum size (raw and zipped) of PySide to execute app on Windows platform? -- anatoly t. _______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
