[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Thanks Sascha. Feel free to raise bugs on things you'd like to see changed,
especially the, well, bugs.
I'm still trying to debate in my mind what the layout of the wizard
categories should be. We've discussed this off and on over the years. I
think at issue is how do we blend in with the other language plug-ins for
Eclipse. Java has its own category, so we took that as the lead to create
one for each language project type. But as the number of languages Eclipse
supports grows, this will become a bit cumbersome.
Probably C/C++ won't make sense either when we start adding more languages
like Fortran, C#, Ada. Would you change it to C/C++/Fortran/C#/Ada/... I'm
also not fond of calling it CDT project, since unless you know you're
explicitly using the CDT, you won't know what that is.
At any rate, the topic is still open for debate and it'll be hard to come to
any sort of consensus, but we do need to discuss it more.
Cheers,
Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, http://cdtdoug.blogspot.com
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Sascha Radike
> Sent: Friday, March 30, 2007 11:41 AM
> To: 'CDT General developers list.'
> Subject: [cdt-dev] Feedback
>
> Hi,
>
> I'd like to provide some feedback regarding the new project model. I have
> not had an in depth look yet but here's a collection of bugs and
> questions.
> I haven't had the time to raise individual bugs yet.
>
> ***
> * Wizards
> ***
>
> --- Is it really neccessary to have three different wizard categories for
> C/C++/CDT ?
>
> Instead of...
> C++
> C++ Project
> C
> C Project
> CDT
> CDT Project
>
> Maybe something like ...
> C/C++
> C Project
> C++ Project
> CDT
> CDT Project
>
> --- When selecting "Advanced settings" on the configurations page of the
> new
> project wizard, a new (temporary) project gets created. When cancelling
> the
> wizard, the project gets deleted. But when starting the wizard again and
> setting the project to the same name again, an error message appears "File
> with specified name already exists".
>
> ***
> * CDTWizard extension point
> ***
>
> --- ICNewWizard: Why does a "Tree" get passed to createItems(Tree tree,
> boolean supportedOnly) ? Isn't this a bad design? I noticed the wizard
> calling this method is interested in ICWizardHandlers only anyway and
> these
> handlers provide name and icon (getName(), getIcon()). So is there a
> reason
> why the raw tree gets exposed to implementors of this extension point
> instead of asking them for an arrary of ICWizardHandler[] ?
>
> ***
> * Build
> ***
>
> --- Are build properties supposed to be used only for values being defined
> via extension point or is possible to set custom data ? I'd like to
> associate custom data via API. And it looks like it is possible if the
> property type has been defined:
> IBuildProperties.setProperty("myProperty.id", "Random...custom...data"); I
> just wonder if it is officially supported. Hope so.
>
> --- Better API doc would be really nice :) There alot of non-doc methods
> in
> IConfiguration and other build interfaces. The ManagedBuildManager is
> missing docs, too. I know, APIs haven't been freezed yet.
>
> ***
> * Build UI
> ***
>
> --- All build ui combo boxes are editable, but they shouldn't be.
> (Artifact
> Type, Builder type, tool chain edit, ...)
>
> --- Why can't the build directory bet set for managed build? This is a
> feature I was looking forward to. I'd prefer setting \bin as my root
> output
> folder rather than having all my output folders right in the project root.
> It should be possible to select at least a workspace folder.
>
> --- Small stylistic enhancements: Properties: 'C/C++ ToolChain edit'
> should
> be something like 'C/C++ Tool chain editor' / 'Language mappings' should
> have 'C/C++' prefix.
>
> --- Tool chain editor: Current builder might be confusing. In 'C/C++ Buld
> settings' the builders are called 'Internal' and 'External' builder. But
> in
> the tool chain editor they are called 'CDT internal builder' and 'Gnu Make
> Builder'. It is also possible to select the Gnu Make Builder, even when
> the
> 'External builder' is not selectable in the build settings (This does
> enable
> the external builder. But switching back to internal does disable it
> again).
>
>
> ***
> * Other
> ***
>
> Just as a reminder: :) I really hope the user help/docs will be rewritten
> or
> updated. Alot of topics are pretty much out of date.
>
> Anyway, I think CDT made a big step forward for 4.0. Rock on.
>
>
> Sascha
>
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
