Re: [cdt-dev] proposal: move references tab

[Doug Schaefer <dschaefer@xxxxxxx>]

Exactly. Eclipse has traditionally had poor support for workspace level
things. But from my experiences, workspaces usually do have semantic level
meaning (just like VS solutions).

On 12-06-26 3:49 PM, "Cortell John-RAT042" <RAT042@xxxxxxxxxxxxx> wrote:

>That sounds like a good idea to me. Users should be able to do both:
>manage references for a particular configuration via the current
>UI/workflow, and then one that lets you manage it at the workspace level
>(all projects).
>
>John
>
>> -----Original Message-----
>> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
>>On
>> Behalf Of Doug Schaefer
>> Sent: Tuesday, June 26, 2012 2:44 PM
>> To: CDT General developers list.
>> Subject: Re: [cdt-dev] proposal: move references tab
>> 
>> I'd like to see project reference management more visible. One idea I've
>> had the last few days working with project teams that are struggling to
>> set up their builds is to create a dialog that could be launched from
>>the
>> Manage Configurations icon that lets you manage and visualize the
>> references for all your projects at once.
>> 
>> I need to understand the right visualization, maybe a tree on the right
>> for each project/config and a tree on the left that shows the dependency
>> for the selected config. But I found myself painfully bringing up the
>> properties for each project a few times over to make sure I had the
>> dependency tree set up correctly.
>> 
>> I guess the point is that it is a dependency tree when you have more
>>that
>> two projects involved and that requires a new workflow to manage easily.
>> 
>> (my 2c)
>> Doug.
>> 
>> On 12-06-26 3:02 PM, "Cortell John-RAT042" <RAT042@xxxxxxxxxxxxx> wrote:
>> 
>> >Hm. I'm not seeing how that would work (with good usability). If you
>> >have a more concrete idea, I'd like to hear it.
>> >
>> >I really don't like that there's two pages for roughly the same thing.
>> >There's no doubt it's confusing. But as with Memory Browser and Memory
>> >View, sometimes logistics and the hierarchical nature of Eclipse
>> >projects makes duplicity difficult to avoid. Again, single-focus
>> >commercial products can remove the platform page to at least solve the
>> >problem for their users.
>> >
>> >John
>> >
>> >> -----Original Message-----
>> >> From: cdt-dev-bounces@xxxxxxxxxxx
>> >>[mailto:cdt-dev-bounces@xxxxxxxxxxx]
>> >>On
>> >> Behalf Of Eugene Ostroukhov
>> >> Sent: Tuesday, June 26, 2012 1:50 PM
>> >> To: CDT General developers list.
>> >> Subject: Re: [cdt-dev] proposal: move references tab
>> >>
>> >> Could this functionality be split in two? CDT could use platform
>> >>property  page for establishing coarse-grained references (e.g. make
>> >>all build  configurations for given project depend on "Active" build
>> >>configuration  for the referenced project) and have another "Advanced"
>> >> page for the users wishing to fine-tune project dependencies.
>> >>
>> >_______________________________________________
>> >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
>
>
>_______________________________________________
>cdt-dev mailing list
>cdt-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/cdt-dev