On Sat, Dec 27, 2008 at 10:04 PM, Terry Brown <[email protected]> wrote:
> rather than having the generated .py file as well as the .ui file, not > sure of the pros and cons, but I didn't see how to make the .py file > anyway :-) Do generate the .py file, it's the cleaner solution if you don't need the dynamism. To take the example from ipython ui, you can create the .py file by: pyuic4 -o qt_ipython.py qt_ipython.ui > Assuming of course that all the wrinkles in Qt get ironed out ;-) I've I don't see why they wouldn't be ironed out, given some time (obviously there is no theoretical limit to how fast / stable it can be). I think various simplifications could be made to clean up many of the wrinkles, one of the most critical being creating the whole tree once and doing all the manipulations on that. -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
