RE: [cdt-dev] Run Configuration cleanup

[Marc Khouzam <marc.khouzam@xxxxxxxxxxxx>]

I believe the arguments tab already has "Program Arguments", so, from that point
of view, it makes sense to me to use the word "Program" in the main tab as well.

But the launch configurations type is called "C/C++ Application".

And we use C/C++ _all_ over the place.

So personally, I'm not against this change, but I wonder if it really makes a
difference, considering the 'inconsistencies' remain in many other places.

So, either way, I don't mind.


Marc



________________________________________
From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Alena Laskavaia [elaskavaia.cdt@xxxxxxxxx]
Sent: May 7, 2010 3:59 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Run Configuration cleanup

While we cleaning up UI there is couple of labels there bothering me
C/C++ Application on main tab
C/C++ Program Arguments on the arguments tab

First of all it is inconsistent.
Second of all use of word Application to pick a "Binary" or "Program"
is improper IMHO.
Third why it is "C/C++"? If we compiled it from any other language it
would run too as long as it is elf binary (or whatever binary platform
supports).

I suggest to call it
"Program" on the main tab
and
"Program Arguments" on the arguments tab

On Fri, May 7, 2010 at 3:51 PM, Marc Khouzam <marc.khouzam@xxxxxxxxxxxx> wrote:
>> I've been consistent with my opinion. We should have one C/C++ Local
>> launch configuration type and have the debug integrations plug in after the
>> fact.
>> The UI should be the same no matter what integration your debugger wants
>> to use.
>>
>> So if this is a step in that direction, I'm all for it.
>
>
> Yes, this is in line with that approach, but only for the Run case (for
> now).
>
> I have posted a patch at
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=281970
>
> The solution does the following:
> - make the current CDI local launch no longer support Run mode
> - creates a new launch delegate dedicated for the Run mode
> - For Run mode, only display the following tabs Main, Arguments,
> Environment, Common (no more Debugger, Refresh or Source)
> - Use the "Connect process I/O to a terminal" option since it seems to make
> sense for Run mode.
> - enable to cleanly use the same launch for Debug mode or Run mode.
>
> I'll wait a couple days for more comments before committing the patch
>
> Thanks
>
> Marc
>
>
> ________________________________
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Doug Schaefer
> Sent: Friday, May 07, 2010 10:46 AM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] Run Configuration cleanup
>
> I've been consistent with my opinion. We should have one C/C++ Local launch
> configuration type and have the debug integrations plug in after the fact.
> The UI should be the same no matter what integration your debugger wants to
> use.
> So if this is a step in that direction, I'm all for it.
> Doug.
>
> On Thu, May 6, 2010 at 3:13 PM, Marc Khouzam <marc.khouzam@xxxxxxxxxxxx>
> wrote:
>>
>> Hi,
>>
>> Running a Local C/C++ Application is not done very cleanly right now.
>>
>> The same launch configuration can be used for Debug or Run.  Each of our 3
>> CDT debuggers
>> use slightly different launch tabs.  Therefore, when the user takes a
>> Debug configuration
>> and wants to run it, which set of tabs should we show?  Currently we show
>> the CDI tabs.
>> But this is confusing because the tabs won't necessarily match.
>>
>> Look at this EDC configuration (bottom of mail) when I open it as a Run
>> config.
>> When did EDC start using GDB? :-)
>>
>> I think we can fix this by simply removing the Debugger tab when we Run.
>>
>> We had a brief discussion about this in
>> http://dev.eclipse.org/mhonarc/lists/cdt-dev/msg17304.html
>> and John explained that using a debugger to run a program makes sense for
>> an embedded
>> system.
>>
>> The problem is that when we Run, we completely ignore the Debugger tab.
>> It doesn't
>> matter what the user puts in there.  So it is only confusing to have that
>> tab.
>> And embedded systems will still need to use Debug As... instead.
>>
>> What do people think about removing that tab when doing a Run?
>>
>> There are two other smaller differences:
>> 1- CDI has a Refresh tab.  DSF-GDB and EDC do not.  Is this a tab we want
>> to show when
>>    doing a Run?
>> 2- CDI and EDC have a "Connect process I/O to a terminal"
>>    I don't quite understand this option.  Can any shed some light?
>>
>> Please let me know of other opinions.
>>
>> Thanks
>>
>> Marc
>>
>>
>>
>>
>> _______________________________________________
>> 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