Lines Matching defs:with
6 % in compliance with the License. You may obtain a copy of the License
51 interfacing {\eclipse} with Java, Sun's popular object-oriented
54 program or to interface {\eclipse} with a commercial application
58 libraries) and a basic knowledge of how to interact with {\eclipse}
218 interfaces which contain the methods used when interacting with {\eclipse}.
229 \subsubsection*{Interact with {\eclipse} using methods in the {\it EclipseConnection} or {\it EclipseEngine} interface}
231 We interact with the {\eclipse} engine by invoking methods on the object
238 \subsubsection*{Terminate interaction with the {\eclipse}}
240 with {\eclipse}, the interaction should be terminated. Like
442 executed. How to construct this parameter is dealt with in Section
444 how to deal with the results returned by {\tt rpc}\index{rpc() method}. Finally, some more
455 the {\eclipse} command line. Just like with the {\eclipse} command line,
501 CompoundTerm}. This object is the Java representation of the goal term, with
510 with their instantiations. Hence even if the variable was named in the
559 rpc}\index{rpc() method} is invoked with a {\it CompoundTerm} parameter. When used in an
561 variable. Using {\it CompoundTerm} you cannot represent a goal with
633 directions. However, the programmer need not be concerned with low-level
661 reference, we supply the method with a string which will equal to the
673 {\it ToEclipseQueue} objects, and will also open streams with the
675 exist with the specified name. If a stream exists which has this name
707 reading from and otherwise interacting with streams. Any of these may
737 Rather than dealing with low-level data I/O instructions such as reading
741 used\index{EXDR}. This allows {\eclipse} to communicate with other
790 FromEclipseQueue}, with the following lines:
845 updates, and have Java react with some appropriate graphical action
856 automatically to {\eclipse}'s interaction with the queue.
880 There is an example Java program {\tt QueueExample2.java} with an
901 relevant incoming stream, write it out in EXDR format with an
918 Starting with release 5.9, the {\it OutOfProcessEclipse}
959 reference, we supply the method with a string which will equal to the
970 object, and will also open a stream with the
972 exist with the specified name. If a stream exists which has this name
1003 reading from and otherwise interacting with streams. Any of these may
1063 used to provide interaction with {\eclipse}. These are {\it
1070 interface for interaction with Java, based around the concept of a
1086 interfacing with Java, there is a unified technique in {\eclipse} for
1091 different machine. When {\eclipse} is communicating with one or more
1209 \item The {\eclipse} engine shares memory and other resources with Java.
1241 and terminated, subsequent invocations of {\tt getEclipse} with an
1302 and our association with it. Once the {\tt destroy} method has been
1325 before the connection with Java is initialised or end after the
1326 connection with Java is terminated. Furthermore, it may also be useful
1404 constructors with a password parameter. This either blocks
1417 {\eclipse}. Another possibility is to call the goal with this argument
1430 sequences, control initially rests with the Java side. Therefore the
1457 used with care. An invocation of {\tt resume()} should be paired with
1471 % \subsubsection{Using {\it ToEclipseQueue} objects with a {\it RemoteEclipse}}
1557 you would expect during a ``session'' with {\eclipse}. The {\it
1595 {\eclipse} is in a separate process \ohtml{(with separate memory heap/stack)} & -- & $\bullet$ & $\bullet$ \\
1596 \olatex{(with separate memory heap/stack) & & &\\}