| [tm-dev] o.e.remote and Terminals |
|
Hey gang,
I have experimented with opening command shells in the Console view using the Terminal control. It works OK, but it really overloads the Console View. We’re already moving towards removing the Debug Console into it’s own view to help alleviate the problem.
At the end of the day, the Console is good for showing messages, but not good as a View where user input is also required.
What I’d like to do instead is come back to the Terminal View and do some work on it to bring it forward. I see a couple of issues that will need some work and would like your thoughts.
First, we represent the Remote Terminal as a single terminal launch delegate. And, in fact, it only has support for the SSH connection type. I have been adding new connection types for different types of Serial connections and would like them supported
as well. My thinking is that each connection type that has a command shell service should have it’s own delegate. There’s lots of code they could share since it’s a common API, but have them listed separately with their new wizard content available for each.
This also brings up another point. There is obviously a lot of duplication between the terminal types and the remote connection types. Do you think it makes sense to consolidate them? I don’t see why they have to be different.
In particular, the Serial terminal uses rxtx still. CDT now has serial port support and the org.eclipse.remote Serial connection type is using it. It doesn’t make that much sense to duplicate it in the terminal plug-in.
Thoughts?
Doug.
|