Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] proposal: move references tab

On Tue, Jun 26, 2012 at 2:04 PM, Cortell John-RAT042 <RAT042@xxxxxxxxxxxxx> wrote:

The Project References page comes from the platform. The platform supports one project referencing another. It now (as of Indigo) also supports build configurations and, at least at the API level, a build configuration having dependencies on other build configurations. Problem is that the platform references page was no enhanced to support that granularity. I.e., from strictly a UI perspective, the platform continues to only allow a project to reference other projects.

 

CDT has given users, for quite some time now, the ability to establish config-level relationships and that’s what the CDT references UI is for. And so, yes, we’ve had two “references” UI, which is very confusing. Unfortunately, until the platform’s UI is enhanced to support config-level dependencies, his duality is unavoidable. Commercial CDT-based IDEs can of course look at hiding the platform page if they are confident their users won’t need it for non-CDT things.

We can easily add our preferences page under platform's page to keep them close at least. You are breaking "established config-level relationships" anyway. And if platform page is hidden the CDT page would pop on the top level.

Andrew

 

John

 

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrew Gvozdev
Sent: Tuesday, June 26, 2012 12:07 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] proposal: move references tab

 

+1 for moving it out of "Paths and Symbols".

 

There is also "Project References" page (from the platform) and the users frequently confused where to look and why there are 2 pages in different places. Maybe we should keep "C/C++ References" under  "Project References"?

 

 

Andrew

On Tue, Jun 26, 2012 at 12:43 PM, Cortell John-RAT042 <RAT042@xxxxxxxxxxxxx> wrote:

The CDT project-references properties tab is not only deeply buried but grouped unintuitively. We’d like to bring it up a level and house it in a page that makes more sense. Please see attached before-n-after screenshot.

 

Objections? Obviously, this would be done for Kepler.

John


_______________________________________________
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



Back to the top