Community
Participate
Working Groups
The current new project wizard is very restrictive. All templates have to live under a category named after one of the built-in artifact types. [I don't want to create my own artifact type...] In my workflow I'd like to create projects with: 1) Custom categories (where I define the layout) 2) Mixed toolchains: Linux + embedded 3) Multiple artifact types: archives & executable. 4) Tie a project creation template to a specific project type I can do this today by: - Defining an IProjectType with the project hierarchy I want [ covers: 1, 2, 3, ] - Registering an AbstractCWizard to return EntryDescriptors from my project types - Create my own WizardHandler which ties the entry to a specific template. If I don't register an AbstractCWizard + Wizard Handler, I end up with: + Project Type + Template Where both project type and template are selectable in the UI. However I really only want one entry: i.e. the user should always run the template when creating the project. By registering custom UI hooks I can associate the template with the project type, but I still end up with the above hierarchy duplicated under "Other..."
