| Re: [tcf-dev] TCF Feature Descriptions for Juno (again) |
|
Many thanks Uwe ! Martin From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Stieber, Uwe Hi Martin, I’ve updated the Target Explorer feature accordingly to your proposal. Best regards, Uwe From:
tcf-dev-bounces@xxxxxxxxxxx
[mailto:tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Oberhuber, Martin Hi all, As we are nearing our 1.0 release for TCF, I’m still not exactly happy about the way our features are presented on Juno. Find attached what we currently have. Here is my proposal to improve it: ------------------------------------------------------------------------------------------------------ TCF C/C++ Debugger A full-featured C/C++ debugger for local or remote systems running a TCF agent. TCF is an extensible, lightweight protocol for universal target access. TCF Remote System Explorer add-in Remote file system and process browsing, and shell access in RSE for systems running a TCF agent. TCF is an extensible, lightweight protocol for universal target access. TCF Target Explorer Dynamic target discovery and configuration, remote file system and process browsing, terminal access and debugger launch for systems running a TCF agent. Does not require RSE. ------------------------------------------------------------------------------------------------------ My rationale is that by shortening the descriptions and making them more map to what end users want, we may well get better exposure and adoption with the Community. I expect lots and lots of people to browse into the Juno sim.rel repository in the coming weeks, so making us look good here is relevant, even if TCF appeals more to WR partners and other vendors who decide adopting TCF for other reasons. Any thoughts or concerns ? Can we add this for a TCF RC2 build ? Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River direct +43.662.457915.85 fax +43.662.457915.6 |