Community
Participate
Working Groups
Maybe the last item for feature-completeness compared to the legacy TM Terminal view: Support opening a terminal on the local host ("Local Program" terminal connector). Maybe by wrapping & interpreting the legacy TM Terminal connectors such that any 3rd party terminal connector could be made available (maybe with limited functionality compared to the dedicated TE terminal connectors)?
Well, "Local Terminal" is apparently usable only on host platforms where CDT provides PTY support. This excludes Windows hosts completely. On a Linux or Mac host, I'm not sure how important it is to have a terminal to your local host embedded within the Eclipse environment. Wouldn't most of the users find it more natural to open a full-featured native terminal on those hosts?
I had a closer look to the "Local Terminal" again and found that it is deeply integrated with the Eclipse launch configuration framework and even provides it's own launch configuration type to run local programs. As long as the connector implementation is not separated from the launch configuration implementation, I do not see any added value in integrating the "Local Terminal" connector with the Target Explorer "Terminals" view. Apparently, there exist a connector that can be used as replacement for the "Local Terminal" connector, and this one is integrated with the Target Explorer, the connector is just not exposed to the user but is the backbone for the "Remote Application" launch. Instead of integrating with the "Local Terminal", it will make much more sense to invest in adding Windows PTY support to CDT. Once this is done, it is only a very small effort to have something similar to the "Local Terminal" functionality, without the overhead of the "Local Terminal" implementation.
To be clear, we are still interested in providing a "local terminal view" inside Target Explorer. We just don't want to integrate it with "Launches" like the TM Local Terminal did.
