On Fri, Apr 24, 2009 at 5:43 PM, Edward K. Ream <[email protected]> wrote:
> The new code provides a proper basis for refactoring. For example, a > simple method to create checkboxes would eliminate 90% of the > (duplicated) text involved in setting up check boxes in the find tab. I agree - the find tab is an example of code that should *not* be done in the ui designer. > I haven't done this yet, but the refactoring will soon reveal that qt > designer does hardly any useful work. Moreover, a little more This also makes the dependency "lighter" in a sense. If it did lots of stuff, it would be a bigger liability (because parts of what it does could not be implemented in other way easily). > I'll leave the useUI switch in the code indefinitely for those who > want to use qt designer for experimentation, but I shall do all > further work in code. Don't try to talk me out of this approach--I'm > a happy guy again. I'm definitely not trying to talk you out of this, never were in the first place - you are the one doing all the hard work, and if you feel obstructed by stuff that is already there (because of not feeling comfortable modifying it - I agree that I had such aversion to editing the gui in designer, because it has grown very complex), you have the right & obligation to get rid of that stuff. What I've been saying is - don't throw the baby out with the bathwater. The "high level" ui could well be instantiated according to the code generated by the ui designer, while doing most of the work in raw code - just adding the widgets to the containers created by the qt designer. If you cut the ui designer out of the loop altogether, it's a one way road with no going back; whereas implementing the "complex" stuff in code while allowing the "big picture" be edited in ui designer (even if it was just about creating the qt_main.py by pyuic4) would not cut us off from the benefits of qt designer altogether. Trust me, the benefits are not negligible - they just appear to be so because the complexity of the ui description have outgrown what can be easily managed by multiple developers. What I'm basically saying is "go for it", though. Everyone will still be able to use qt designer, say, to create their own widgets for tab widget. Modifying the main ui will require more "inside" knowledge, but I'm not sure how big a problem that will be in practice. -- 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 -~----------~----~----~----~------~----~------~--~---
