[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Importing Existing Code
|
I'm one for "Verboseness" when it comes to things like this. Where
ever the menu items or buttons or what ever I think they should read
something like:
Import existing Makefile project
Import Existing CMake Project
Import Existing QMake project
In addition (again, just brain dumping.. ), the wizard should clearly
indicate the following:
Create NEW Directory in Eclipse Workspace
or
My Project already Exists in the Eclipse Workspace
or
Move/Copy Project Directory into Eclipse Workspace
That's all for now.
___________________________________________________________
Mike Jackson www.bluequartz.net
On Mar 10, 2010, at 3:19 PM, James Blackburn wrote:
Sounds great! Users get this wrong all the time -- often remembering
the 'create new project' step, but forgetting makefile project type
and getting auto-magic makefiles for the default configuration.
The distinction between Import and New has always been murky, if
Import can do what users expect, this will be a step in the right
direction.
Cheers,
James
On 10 March 2010 19:16, Doug Schaefer <cdtdoug@xxxxxxxxx> wrote:
Hey gang,
One of the activities that I'm planning on and starting is to add
usability
features where I find I need them. As I muck around with different
side
projects, I am going to assume if I see the need for something
other CDT
users would too. Might be a reach, but at least I'll be happier :).
The first one I'm working on is a quick way of getting an existing
code base
into the CDT. Right now, the only way I know to do that is to
create a new
project and specify the location as the same location as that code
base and
then set the project type to Makefile. The warning that shows is
scary but a
sign that this wasn't a first class citizen scenario.
What I'm proposing and coded up is an Import wizard for Existing
Code. It's
a simple one page wizard that lets you select the name of the
project, the
location of the existing code, the language, and the tool chain for
the
indexer. Makefile project is assumed since it's unlikely you'd use
this
feature to add managed make to existing code (if you need to, you
can use
the previous workaround).
It's checked in now. You can find it in the Imports dialog under
the C/C++
category and called "Existing Code". I'd love to hear your feedback
and
bugs.
As a side affect I'm learning more how to make these kind of wizards,
something I'll be doing for other scenarios, like Qt, Android, Mac
(maybe).
The code to set up the build settings for a Makefile project are
troubling,
but now I know that first hand.
Cheers,
Doug.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
