| Summary: | C/C++ active build configuration as project decorator | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Salvatore Culcasi <salvatore.culcasi> | ||||||
| Component: | cdt-build | Assignee: | cdt-build-inbox <cdt-build-inbox> | ||||||
| Status: | RESOLVED WONTFIX | QA Contact: | Andrew Gvozdev <angvoz.dev> | ||||||
| Severity: | enhancement | ||||||||
| Priority: | P3 | CC: | cdtdoug, freidin.alex | ||||||
| Version: | 4.0.2 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Salvatore Culcasi
Created attachment 179639 [details]
Patch proposing the enhancement
Patch which proposes the enhancement and fixes a refresh problem when changing the active configuration from the toolbar
Created attachment 179640 [details]
This is what appears in the Common Navigator views
I have a couple of questions: 1. In your particular workflow, why do you need to visualize that besides being nice and looking pretty? Is there a situation when a user would make a different decision based on that information? 2. If some other decorators like that are there (i.e. CVS branch decorator), what will be the order? I'm definitely not in favor of this. Decorators in the project explorer are generally reserved for source control information. Once we have Configurations in the Resource tree we can highlight the active on there. (In reply to comment #3) > I have a couple of questions: > 1. In your particular workflow, why do you need to visualize that besides being > nice and looking pretty? Is there a situation when a user would make a > different decision based on that information? > 2. If some other decorators like that are there (i.e. CVS branch decorator), > what will be the order? 1) yes, we have still customers reluctant to adopt Eclipse/CDT, these people complains that some information are not quickly accesible and requires user actions to access them 2) not checked anyway the Comment 4 made this proposal obsolete (In reply to comment #5) > 1) yes, we have still customers reluctant to adopt Eclipse/CDT, these people > complains that some information are not quickly accesible and requires user > actions to access them > 2) not checked anyway the Comment 4 made this proposal obsolete That is not really answering the questions but if the proposal is obsolete I close the bug. (In reply to comment #4) > I'm definitely not in favor of this. Decorators in the project explorer are > generally reserved for source control information. > > Once we have Configurations in the Resource tree we can highlight the active on > there. While the motivation for this request is clear and the decorator looks good by its own, it doesn't play well with the CVS decorator. I didn't find anything about "Configurations in the Resource tree", so I opened a general ticket for this topic - bug 331870. BTW, I still plan on adding build configurations into the Project Explorer tree. We can use various techniques to highlight the active configuration that way. |