Just write a Makefile to help you during development. I really don't think it's worth burdening your users with the extra load time. Also if you plan on going multi-platform, you will have to write platform specific hacks to figure out the loaction of the ui files.
Kovid. Kovid. On Friday 15 June 2007 08:34:19 Dirk Reiners wrote: > Hi Everybody, > > as I said already I'm just starting out using PyQt and therefore I would > like to tap into the experience pool on the list to avoid making > fundamental mistakes early in the project that are hard to fix later. > > I'm trying to decide whether to a) use pyuic4 to generate a python module > to include, or b) use uic.loadUi() to load the .ui file directly. > > As far as I can see the only possible disadvantage of b) is the time it may > take to create the ui compared to just loading the .pyc file. The advantage > is not having to remember to run the build system (scons in my case, thanks > to Patrick Hartling for the pyuic builder!). A difference (neutral) is not > being able to derive from the module and avoid having to add .ui to access > the ui variables, but that doesn't look like a big deal. > > Is there something more that I'm missing? > > Thanks > > Dirk > > _______________________________________________ > PyQt mailing list [email protected] > http://www.riverbankcomputing.com/mailman/listinfo/pyqt > > !DSPAM:2,4672b21b235121694714482! -- _____________________________________ Kovid Goyal MC 452-48 California Institute of Technology 1200 E California Blvd Pasadena, CA 91125 home : +01 626 390 8699 office: +01 626 395 6595 (449 Lauritsen) email : [EMAIL PROTECTED] web : http://www.kovidgoyal.net _____________________________________ _______________________________________________ PyQt mailing list [email protected] http://www.riverbankcomputing.com/mailman/listinfo/pyqt
