https://forum.librecad.org/Segmentation-fault-in-RS-EntityContainer-optimizeContours-tp5651061p5660826.html
On Apr 23, 2012, at 1:31 PM, dxli [via LibreCAD] wrote:
I know we are getting OT here.
In my experience UI work is only a very small part of the total development time of a application.
However, when a UI was build programmatically you can get into a lot of re-compile and test stages because
you cannot always see the UI and of the underlaying framework responds to the changes you make.
Additionally, little changes in the UI, even build programmatically can also result in a larger set of changes,
eg, not only the XY/Y position of the button changes.
For example when you move a button from one area to a other area, you will see multiple lines being changed.
You would need to move code around and put the button in a different area of your program.
Given ofcourse you build the UI with proer spacers and 'fluid' rater then fixed positions.
Within QT a UI is build within .ui file that get's compiled into a cpp+h file. However, any change in
the UI file doesn't get reflected into the program separating the concerns of UI (view) and program
even better. If a button is moved we really don't care about how this was reflected in the UI file. We only
care about the bugtrack entry showing the reasons. Our code would even stay exactly the same so
in my opinion, building the UI graphically, in our case with UI designer would be more of a benefit
and even allows for auto-creating connections between the slots and the UI. This allows writing
even less code and plain simple this reduces maintenance.
Ries