Hi All:
So I've discovered by more code-browsing that the new tm terminal view
makes their internal viewer public API. This should easily allow someone
like Lars to use the viewer and embed it into their own view. I havent'
yet discovered if their public API is sufficient for Lars to simply call
and open a specific connection type in the existing view.
I have learned, however, that o.e.remote does not plan to use their
view, but rather will use the viewer itself and create 'consoles' out of
it... via IConsoleManager and the associated UI. You can find their
code in
git://git.eclipse.org/gitroot/ptp/org.eclipse.remote.git in
the bundles/org.eclipse.remote.console/ folder.
I've also opened bugs to ensure that this plugin at least has public API
to open a console for a given o.e.remote IRemoteConnection object, which
I've just had accepted.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=467350#add_comment
Either way, whether Lars in the future wants to make his servers
exposable via o.e.remote and implement an IRemoteCommandShellService
(which I haven't investigated how easy this part is yet, but I suspect
its not difficult) or if he wants to simply keep his view but change the
implementation to use the new public API viewers inside, it should work
as expected.
There's enough code in existence now that provide PoCs and should make
converting his console fairly easy.
It would be really nice if Lars had a Mars branch and TP available,
though. But it seems he won't get that far for quite a while, so I took
the lead on making sure API was sufficient.
Does anyone else depend on the terminal situation other than Lars? It'd
be great if specific usecases could be laid out for how it's being used
right now and what fucntionality is needed in future impls.
- Rob Stryker