Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] How to create a CDT Standard Make Project

I would vote for having the folder still selectable, but having an "Empty project" under the folder that does the same thing.
Less clicks for the experienced, most obvious selections for the less experienced.


...Beth

Beth Tibbitts (859) 243-4981 (TL 545-4981)
High Productivity Tools / Parallel Tools http://eclipse.org/ptp
IBM T.J.Watson Research Center
Mailing Address: IBM Corp., 745 West New Circle Road, Lexington, KY 40511
Inactive hide details for "Schaefer, Doug" <Doug.Schaefer@xxxxxxxxxxxxx>"Schaefer, Doug" <Doug.Schaefer@xxxxxxxxxxxxx>


          "Schaefer, Doug" <Doug.Schaefer@xxxxxxxxxxxxx>
          Sent by: cdt-dev-bounces@xxxxxxxxxxx

          05/30/08 10:50 AM

          Please respond to
          "CDT General developers list." <cdt-dev@xxxxxxxxxxx>

To

"CDT General developers list." <cdt-dev@xxxxxxxxxxx>

cc


Subject

RE: [cdt-dev] How to create a CDT Standard Make Project

The easiest solution would be to create an Empty template for each of the project types that don't have one. Creating templates is documented in CDT's ISV docs. Or you can follow the examples of the ones that are already there.

Cheers,
Doug.


From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Oberhuber, Martin
Sent:
Friday, May 30, 2008 10:37 AM
To:
CDT General developers list.
Subject:
RE: [cdt-dev] How to create a CDT Standard Make Project

Dear all,

Thanks for the very positive responses to this message.

I didn't find a proper existing bug in bugzilla, so I filed
https://bugs.eclipse.org/bugs/show_bug.cgi?id=234860

Vladimir, attaching your patch on that bug would be highly
appreciated. I encourage all interested parties to CC on
the bug.

What I'd be looking for in the Ganymede timeframe, is
    • Instructions how adopters of CDT can fix the problem in their products, without changing CDT itself
    • Ideas for what can be done in plain CDT (documentation? additional default wizard types?)
Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm




From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Schaefer, Doug
Sent:
Friday, May 30, 2008 3:34 PM
To:
CDT General developers list.
Subject:
RE: [cdt-dev] How to create a CDT Standard Make Project

+1. We've had issues with that all along (this has been there for over a year now). We had proposed having an Empty template so you could select that. Or at least change the icon for the project type so you wouldn't confuse it as being a folder. This all fits in with the clean up we need to do for CDT 5.1. In the mean time, Martin, please raise a bug so we don't lose this. There may already be one there if you can find it.

Cheers,
Doug

    From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Oberhuber, Martin
    Sent:
    Friday, May 30, 2008 7:57 AM
    To:
    CDT General developers list.
    Subject:
    [cdt-dev] How to create a CDT Standard Make Project

    Hi all,

    I just came across what I find a MAJOR hurdle for
    CDT Newbies, or people upgrading from earlier versions.

    I wanted to create a CDT Standard Make project; looking
    for the corresponding project type that used to be there,
    I didn't find it so I chose "C Project".

    On the page where I can select Project types, I found a
    folder "Makefile Project" and below it an item "Hello world
    C++ Project". So, no way to create a normal Makefile
    Project?

    It took a CDT committer (Markus) to tell me that I can
    actually select the FOLDER named "Makefile Project"
    and it's a valid project type. It might be obvious for
    CDT committers and power users, but I don't think that
    any newbie would ever find that out by himself.

    What about making the folders non-selectable and adding
    separate items below them for the normal config? Or,
    going with a tree like this:

    Managed Build Executable/
    +- CDT Executable Project
    + Examples/
    Hello World C++ Project
    ...
    Managed Build Shared Library/
    + CDT Shared Library Project
    Makefile project/
    + CDT Makefile Project
    + Examples/
    Hello World C++ Project

    Or, even a tree like this:

    Managed Build/
    + Executable
    + Shared Library
    + Static Library
    + Empty Project
    + Examples/
    Hello World C++ Project
    Hello World ANSI C Project
    Makefile Project/
    + CDT Makefile Project
    + Examples/
    Hello World C++ Project


    Where the folders (boldface) are not selectable but just
    expandable containers for the subnodes.


    Cheers,
    --
    Martin Oberhuber, Senior Member of Technical Staff, Wind River
    Target Management Project Lead, DSDP PMC Member
    http://www.eclipse.org/dsdp/tm

    _______________________________________________
    cdt-dev mailing list
    cdt-dev@xxxxxxxxxxx
    https://dev.eclipse.org/mailman/listinfo/cdt-dev

GIF image

GIF image

GIF image


Back to the top