documents/userman/umstkeclipse.tex

66   Unless it is attached to the remote
276 from the {\eclipse} session, and are attached to it via the Tcl/Tk remote
295 remote tools active)}
299 Once attached to an {\eclipse} session, the remote development tools have
309 to each other via the remote Tcl/Tk interface. The interactions of the two
315 can only interact with the remote tools window when execution in the
316 {\eclipse} session is suspended. The toplevel window of the remote tools
319 the remote tools to {\eclipse}. This can either be
322 to {\eclipse} via the ``Resume ECLiPSe'' button on the remote tools window.
327 To use the remote tools, the user must first load the right library
329 start the remote tools by
343 {\eclipse} prints the host and port address it expects the remote tools to
344 attach to, and execution is now suspended waiting for the remote tools to
358 remote tools are ran on the same machine as the {\eclipse}
367 success, the remote tools window (see Figure~\ref{remotetools}) will be
370 The user is not able to immediately interact directly with the remote
380 be handed over to the remote tools. This can be done by calling the
382 When the remote tools have control, the user can
386 of the remote development tools:
390 \item[tools\indextt{tools/0}] Explicitly hands over control to the remote
393 {\eclipse} session is suspended until the remote tools allows {\eclipse} to
398 	Checks if the remote development tools have been attached to this
406 Once attached, the remote development tools should be connected until the
413 It is possible to attach the remote development tools to any {\eclipse}