RE: [cdt-dev] Convert To a C or C++ Project

["Judy N. Green" <jgreen@xxxxxxx>]

I agree that the workflow does seem a little odd.

The reason that the convert wizards are in the New Project Wizard is
because we were trying to follow what the JDT does. The wizard to
convert a Java Plugin into an Eclipse Plugin Project is in the New
Project wizard.

Always open to ideas

-Judy


-----Original Message-----
From: Schaefer, Doug [mailto:dschaefer@xxxxxxxxxxxx] 
Sent: Monday, February 24, 2003 3:52 PM
To: 'cdt-dev@xxxxxxxxxxx'
Subject: [cdt-dev] Convert To a C or C++ Project


Could someone explain to me why the workflow to convert a project
between C and C++ takes the user through the New Project wizard?  Could
the same thing be accomplished by through the Project property page or
through an action in the Navigator (you should be able to add/remove
natures from anywhere)?

 

Sorry, but the workflow just seems a little bit odd, especially since
you start with the New Project wizard and then end up not making a new
project.

 

We are thinking that the best way to activating the new build system is
to create a new project wizard as a peer to the "Standard Make Project"
wizard and the "Convert..." wizard just doesn't seem to fit in to me.

 

Opinions?

 

Doug Schaefer

Senior Staff Software Engineer

Rational Software - IBM Software Group

Ottawa (Kanata), Ontario, Canada