|
From what I’ve seen the TCF terminal is built on top of the TM terminal. It seems TCF just replaces the View and has a different settings setup. I still need to take a deeper look at why all this was necessary, especially for the Local terminal which apparently
wasn’t possible with the TM terminal on it’s own.
On a related note, I’m about to try and hook up the TM terminal to the o.e.remote command shell service to see if it works. I have my Arduino C++ IDE using the new o.e.remote-ized launchbar and will bring my serial port implementation over as the command
shell. Interesting to see where it takes me.
BTW, you can see the o.e.remote-ized launch bar in the cdt/org.eclipse.launchbar git repo on the oeremote branch. Also in there is the current state of my thinking for the o.e.remote 2.0 API. They’ll be released with the preview of the launchbar in Luna
SR-2 next month. LaunchBar 2.0 will release with Remote 2.0 with Mars to complete the work. So the theory goes :).
Doug.
I’ve been looking at TCF terminal and it seems that there is a dependency on org.eclipse.tm.terminal. I though it was supposed to be independent of TM? Can someone clarify this?
Thanks,
Greg
Hi Greg,
Well, I can speak only for Terminal and the Terminal is definitely under active development. There might be just 2 active committers left, myself and Martin Oberhuber
from time to time, but we still do changes and we still need releases. I would be OK to move out the Terminal from the TM project but the proposed common project where things like the Terminal could live does not exist yet. I’m also fine with moving the Terminal
widget to the TCF project container, but that’s something Martin Oberhuber needs to decide.
For the Terminal, the main complains are not necessarily bugs at this point of time, the main complains are about the fact that you do have multiple Terminal
views in Eclipse once RSE is installed. 2 views are at least deprecated and only the “Terminals” view provided from the TCF project is maintained and where new features requested by the users are added. We have to get the 2 other Terminal views out of Eclipse
to stop the user confusion. The plan for doing this is outlined below, but this work does have some effect on EPP packages. I can do everything outlined below, but I don’t know how to get the EPP packages updated to include the correct features.
The cleanup of the multiple Terminal views should happen for the Mars release.
Regarding the committer meetings, at least for me time is limited and discussing things here instead of a shared conference call is easier to manage.
Thanks, Best regards, Uwe J
Hi Uwe,
I’m not sure of the plans at this point. I’ve asked this list about the 3.6 version a couple of times but received no reply. I’ve also invited everyone to the PTP developers conference call to discuss plans, but no one from TM ever attended. At this point,
I’m assuming that the current release is the final release for TM.
I’m not a developer on the project, so I don’t know what anyone’s plans are unless they let me know. Also, developer’s will need to step up and update the project plan, documentation, and anything else that needs to be done. I can fix the outline of the plan,
but someone else will need to fill in the details. Finally, we need people to test the builds before they are released, or we can’t say we’re meeting Eclipse quality. This didn’t seem to be happening for the SR1 release.
Greg
Can you confirm that I’m right in assuming that the master branch is leading to the TM 3.7 release? When will it be released? I’ve checked the TM project pages under eclipse.org/tm,
but this pages are not up to date.
If master is leading to the 3.7 release, I would like to change at least the TM Terminal feature version numbers accordingly. Also I want to tackle a few Terminal related releasing issues
we keep pushing ahead of us for a long time now. Not sure if you need to announce them in some project lead meeting.
1. Deprecation
of unused or no longer supported features
a. Take
out the o.e.tm.terminal.view and the o.e.tm.terminal.local from the build and repositories
b. Move
the source of this features to terminal/deprecated folder to keep the source around for reference
c. Remove
the o.e.tm.terminal.core.sdk feature as without the terminal.view feature, the usual SDK feature is the same as the core.sdk feature
2. Work
on replacement for org.eclipse.rse.terminal feature
a. Remove
this feature from the org.eclipse.rse feature
b. Create
an replacement providing the same entry points from the RSE System Explorer as the org.eclipse.rse.terminal plug-in does but use the newer and maintained TCF Terminals view. The new RSE terminal feature will be provided by the TCF project like the TCF based
file system and process RSE contributions.
All effort is related to address the many complains about having up to 3 different terminals views available in Eclipse. Final goal is to bundle all terminal related effort, bugfixing
and feature development, into the superior TCF Terminals view.
_______________________________________________
tm-dev
mailing list
tm-dev@xxxxxxxxxxx
To
change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tm-dev
|
