We could potentially consider pushing down some of this into the agnostic (non-TCF) part if you are interested. Similar Services and constants exist for FileTransfer and Terminals service – see here for the generic (non-TCF) services:Īnd here for some basic core TCF services which I referenced above:Īs you see, the dropdown and locator (target address) API’s are currently in the non-agnostic i.e. getInstance().getService( newLocatorNode. Use the IPropertiesAccessService to get the IP address and port of the currently active connection. getInstance().getService(IDefaultContextService. Use the IDefaultContextService to get the currently active connection. Note how – thanks to the service architecture – different service implementations are possible for a “UI Driven Eclipse” versus a different configuration that might get the IDefaultContextService fromġ. Here is some sample code to obtain the currently selected default connection,Īnd then query some properties like IP Address and port. In terms of the code, TCF/TE follows a modern service-oriented architecture. Using the IPropertiesAccessService, these are easily obtained. But any target connection (“peer” in terms We don’t currently have support for matching the architecture of targets against the architecture of projects. Since target explorer is very generic and agnostic, it should be possible to implement a bridge for RSE type of connections, or JSch type of connections for PTP. Webpack to build Cockpit UI packages - Update the Cockpit Vagrant development box to use Fedora. But we’ve already extended this for our commercial product to provideĭifferent connection types. It duplicates the manual pages and their.
Right now, the only type of connections supported in Open Source are TCF connections. This is what it looks like when you install “TCF Target Explorer” from Luna Simrel into the Luna C/C++ Package – it seems nicely aligned with the toolbar We recently added a toolbar dropdown to TCF Target Explorer, for creating new target connections, choosing a “current target connection”, connecting and performing You might consider using the TCF Target Explorer as a generic container / API to unify the various target management systems that CDT / PTP may want to support.
0 kommentar(er)
