Today the VNC viewer in TmL project is totally independent of the rest of the projects.
There are three packages there:
org.eclipse.tml.protocol - Mechanism to implement generic protocols (RFB is implemented over this)
org.eclipse.tml.vncviewer - VNC viewer library, it is a SWT component that implements the frame buffer display using RFB protocol.
org.eclipse.tml.vncviews - Contain an eclipse view feeded by the SWT component from VNCViewer.
Only these packages are necessary to use the VNC Viewer capability. Even the other TmL components are client of this packages if they are using VNC features.
This week we are also working to provide a TML x TM integration using the most recent version of both projects. As soons as we have a first version of this proof of concept we will share it.
Thanks and Regards
De: Oberhuber, Martin
Enviada: ter 24/6/2008 14:23
Para: DSDP PMC list
Assunto: [dsdp-pmc] Move VNC Viewer core from TmL to TM?
a request was made to have a "Remote Display" kind of framework
in TM. A reporter argued that he doesn't want the whole TmL
functionality but just a VNC kind of remote display.
Christian, Eric (and other listening TmL members), what do you think --
would it make sense to move the TmL VNC implementation from the
TmL project to TM, in order to give it a "more generic" home?
Of course, the committers responsible for the VNC component would
be asked to earn commit rights on the TM project when this is done,
such that they can continue maintaining their code under its new home.
Please have a look at the bug mentioned and comment on it.
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member