Hi,
Laurent Dufrechou wrote:
> User who use source install will not be bothered by using uic file or not.
> Since each time you generate a new ui file, you should regenerate the .py
> file.
> And commit _both_ of them.
Or introduce a trick to load ui file dynamically:
try:
from ui_foo import Ui_Foo
except ImportError:
from PyQt4 import uic
Ui_Foo = uic.loadUiType(os.path.join(os.path.dirname(__file__)),
'foo.ui'))[0]
It can ease the development process, since we don't need to type
`make ui` or `python setup.py build_ui` everytime you change ui file.
> From my experience, using ui file (and thus designer) for simple dialogs
> lower the level for people
> to participate to the project and also force people to derivate always from
> generated dialogs.
> (Well in my case it was for an in house tool, but still...).
> Looking behind, I gained a lot of time using Qt designer, instead of doing
> all by hand.
> The thing I loved, was that while using it, your code still stay very very
> clean, since qtdesigner only define widget not actions like classical GUI
> designer.
Yes, there's no magic pushbutton. :P
One possible drawback is it makes a bit harder to review changeset.
Yuya,
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Tortoisehg-develop mailing list
Tortoisehg-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
