comparison docs/lyx/ede.lyx~ @ 42:792da050d8c4 tip

more dox

 EDE Use Cases
 \end_layout
 
 \begin_layout Standard
 EDE is highly modular.
- Each it's components, with the exception of the UI, is written as a stand
- alone programs and works independently.
+ Each of it's components, with the exception of the UI, is written as a
+ stand alone programs and works independently.
  Because of this design strategy EDE can be used in a number of different
  ways.
  This section details the use cases experimented with so far.
 \end_layout
 

 \end_layout
 
 \begin_layout Standard
 Using the tool chain in this manner is analogous to programming and run-time
  debugging a real-world micro-controller.
- Source code is assembled and the written into the emulator's memory, the
- user can then use the debug prompt to step through program and probe the
- emulator internals.
+ Source code is assembled and written into the emulator's memory.
+ The user can then use the debug prompt to step through program and probe
+ the emulator internals.
 \end_layout
 
 \begin_layout Standard
 \begin_inset ERT
 status open

 
 
 \end_layout
 
 \begin_layout Standard
+\begin_inset Newpage pagebreak
+\end_inset
+
+
+\end_layout
+
+\begin_layout Subsection
+Interpreter Mode
+\end_layout
+
+\begin_layout Standard
+Source code does not have to be pre-assembled.
+ Since the command-line interface, the assembler and the debugger are all
+ written in python, the assembler's functions can be imported into the interface
+ code.
+ This has been done to create a mode where the user enters assembly code
+ at a prompt, and then that code is immediately assembled and executed on
+ an instance of the emulator.
+\end_layout
+
+\begin_layout Standard
 \begin_inset ERT
 status open
 
 \begin_layout Plain Layout
 

 \end_inset
 
 
 \end_layout
 
+\begin_layout Standard
+\begin_inset Graphics
+	filename /home/jmz/qm/ede/docs/img/ede/interpreter.svg
+	display false
+
+\end_inset
+
+
+\end_layout
+
 \end_body
 \end_document