Problem 2)
Another change I would like to see in Desktop Applications is that one does not have to program any UI logic (creating widgets, connecting events) at all, it just seems to be redundant. Why do we design a UI by writing *text* in 2015?
It should be possible to auto-generate a UI from the type of objects one wants to modify, from the constraints of the best practices in UI design, perhaps with a workflow definition. It's useless to have all this freedom when we always want it the same way (text boxes for text input, checkboxes for booleans, list for lists, buttons for actions) anyways. Why hasn't a library come along that does that. At least glade lets one draw UIs, producing a XML file that can then be loaded and populated by events. More work on making programming UIs trivial please.
This feature has existed for a very long time now. Microsoft Access has done exactly what you're looking for since the 90s. If you're happy just using Access apps, this should be fine for you. The flip side is that GUI designers are slower than writing code for most experienced developers. While you're wrestling Qt Designer, I'll be in the code editor manipulating the screen much more quickly.
Also, most non trivial apps will require specialized behavior at various points. That means writing code. Visual models don't work well for that. The code is easier to modify and to maintain, because it allows direct manipulation of the logic symbols, rather than manipulating an abstraction of the logic.
Seriously, we covered all of this ground in the 90s. A lot of money and programmer time was put into trying to make your vision a reality. We gave it up as a bad idea.