I reject your position entirely.
1. We do not need to conceed change for the sake of change. Change should only happen when there is an improvement.
2. Metro has flopped. Even MS can't move the market. It's wrong to assume that they dictate UI, or UX culture. Culture is a societial construct. We all participate in it, and no one of us owns it.
3. Accepting "that's just the way it is" does nothing to improve th situation, and I an apalled at your resignation to it. There's a great quote "Well-behaved women seldom make history". The status quo is never an improvement or news worthy.
4. I'm not saying things were better. As I've stated gloss was getting out of hand and information density was too high. But that doesn't mean that we shouldn't have to sacrifice up buttons of the most important actions to the design gods, and hide that functionality behind a right click.
5. As as 35 year vetern of computer UIs, I've seen changes over time, and it is natural for big changes to be resisted. But I don't really care about flat, skeumorphic, gloss, material, metro, I care that the UI is /intiutive/. The primary use cases should be obvious and easy to perform. While the kit/build "buttons" at the top pf the Projects editor were getting out of control, the clean up is very welcome. But the two things that I want to do when I'm in this view are change the build/run settings (which survives, thank goodness) or add a kit. No where is there a button for adding a kit. There is no way to tell there is a context menu availible. Also, having the context menu availibl e when over project settings is bad design. Basic UX is that when I'm right clicking on something I get a context menu for that something. But the contect menu doesn't apply to what I'm clicking on, it applies to the whole frame. Very simply, the context menu shuold be removed and two buttons added under "Build & Run" which are "Import build" and "Add Kit". You added a non-obvious required click between me and the function I want.
6. Furthermore, you could have extended the "tree" (I still don't see a tree) to also include the build configuration (Release, Debug) under the Build or Run items for that kit. Why did the tree terminate where it did? You added another 2 clicks for me. I could have just clicked on "Release" in the tree, but now I have to click on Build, then click the drop-down (+1) , then click again to select the one I want (+1).
Does anyone do usability studies any more? I can't be the only one that is appauled by this [industry wide] regression of UX. I remember when click depth (counts) was a thing.
_______________________________________________ Qt-creator mailing list Qtemail@example.com http://lists.qt-project.org/mailman/listinfo/qt-creator