-----Original Message-----
From: cdt-dev-admin@xxxxxxxxxxx
[mailto:cdt-dev-admin@xxxxxxxxxxx] On Behalf
Of Sean Evoy
Sent: Wednesday, March 03, 2004
4:24 PM
To: cdt-dev@xxxxxxxxxxx
Subject: RE: [cdt-dev] Suggested
change to String option command generation.
Minus the round-trip part, I wanted to provide a
summary page that would aggregate all the option settings together and display
it to the user back in 1.2. There is even a skeletal "summary" option
page ready to go. The problem of updating the summary page in response to UI
events was a bit more complex than I had time to deal with back then. The
complexity is still there, but I haven't thought about it in a while and it
might not be all that bad with enough time to do the job right. If you guys at
TI are interested in doing this, let me know and maybe I can point you in the
right direction.
I
can state with certainty that round-tripping is going to be virtually
impossible given the current architecture.
Sean
Evoy
Rational Software - IBM Software Group
Ottawa, Ontario, Canada
"Treggiari, Leo"
<leo.treggiari@xxxxxxxxx>
Sent
by: cdt-dev-admin@xxxxxxxxxxx
03/03/2004 02:35 PM
Please
respond to
cdt-dev
|
|
To
|
<cdt-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
|
RE: [cdt-dev] Suggested change to String
option command generation.
|
|
Regarding
round-trip editing and Visual Studio. Visual C++ used to support that,
but hasn't since Visual Studio .NET. I don't know if they gave it up
because they didn't think it was used by many people, or because it was
"too hard". Visual C++ still does display the entire command
line and has an edit box for "Additional Options".
Regards,
Leo
-----Original Message-----
From: cdt-dev-admin@xxxxxxxxxxx
[mailto:cdt-dev-admin@xxxxxxxxxxx]On
Behalf Of Chris Wiebe
Sent: Wednesday, March 03, 2004 2:27 PM
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] Suggested change to String
option command
generation.
> As a related topic, something we at TI were
thinking of doing sometime
> down the road was extending the "catch
all" box so that it would show
> the full command line string that would be
passed to the tool (i.e. it
> would pick up the output of all the other
options based on their states)
> so that the user a) could actually see
everything that would be passed
> to the tool and in what order, and b) so in
theory the user could edit
> whatever they wanted in that box and
theoretically have it parsed back
> and reflected in the other options in the GUI
(e.g. if you turned on the
> symbolic debug checkbox, and then in the
"full command to tool" box you
> removed the -g flag, then the symbolic debug
checkbox would get
> unchecked).
This is a great idea, especially the round-trip
editing which is very
nice to have. I believe MS Visual Studio
does this as well...
Cheers,
Chris
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev