Hi Doug,
My two cents on the topic. I generally agree with Bill Swanson that the wizard should reflect user intentions, so redesign should start from understanding use-cases.
So, here's my case. We are using CDT for game console development, using the tools provided by manufacturer. The project is built by OMake, so most of the elements in the wizard don't make any sense for us. So every time I need to create a new project, I'm looking through the first page panels to choose "Makefile Project" > "Empty Project" at left and "Other Toolchain" at right.
The thing is that here for me "makefile" means not "built with make" but rather "not managed by CDT".
I generally agree with Martin Runge that main thing for me is "who would manage the project". So my proposal is choosing the "manager" for the project first.
- how do you want the project to be managed?
( ) by CDT built-in manager
( ) executable
( ) shared library
( ) static library
( ) by Make
( ) custom makefile
( ) template for executable
( ) template for shared library
( ) by CMake
( ) <whatever makes sense for CMake>
(o) by other system (i.e. you manage it yourself)
Also I would like to have some way of making my own project template without creating a new plugin. Imagine that I make all the choices for a new project once, and then press "save as template" button. And next time I want to create a project, I have this template listed somewhere on the first page of wizard, so I don't have to make same choices again.
Best regards,
Mikhail