Docking has improved too: https://wiki.qt.io/New_Features_in_Qt_5.6 https://wiki.qt.io/New_Features_in_Qt_5.6 - Allow programmatic resizing of dock widgets

Docking has improved too: https://wiki.qt.io/New_Features_in_Qt_5.6 https://wiki.qt.io/New_Features_in_Qt_5.6 - Allow programmatic resizing of dock widgets - Allow dropping dock widgets into floating docks - Allow the user to re-arrange tabified docks I haven't tried it out yet, or seen a demo, but in my previous company we spent some time finding out a solution for docking that mimicks to a degree what Visual Studio did, and we somehow did it, but it's not as good still as Visual Studio. It was very important for the artists/level builders/scripters to be able to use 3 monitors efficiently (something that the browser lacks in general), and a window spread on three of them is not what they needed. They really wanted one monitor with say the level (3d map), another monitor would have all assets for preview/selecting, and a third one for additional debugging. Then when you close, and open again the app it should remember the positions, sizes, etc. Autodesk Maya/MotionBuilder uses Qt, so if they switch to this version they'll benefit from it. As an alternative solution, but only in Python (PyQt, PySide) land, there is https://github.com/nucleic/enaml https://github.com/nucleic/enaml http://nucleic.github.io/enaml/docs/examples/ex_dock_area.html http://nucleic.github.io/enaml/docs/examples/ex_dock_area.ht... It's beautiful!