Sophie

Sophie

distrib > Mandriva > 2010.0 > i586 > media > contrib-release > by-pkgid > bd5c3d824c3db63ffd9226c15941e6ad > files > 2382

mozart-1.4.0-1mdv2010.0.i586.rpm

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>2.3 Implementation</TITLE><LINK href="ozdoc.css" rel="stylesheet" type="text/css"></HEAD><BODY><TABLE align="center" border="0" cellpadding="6" cellspacing="6" class="nav"><TR bgcolor="#DDDDDD"><TD><A href="node4.html#section.started.architecture">&lt;&lt; Prev</A></TD><TD><A href="node2.html">- Up -</A></TD></TR></TABLE><DIV id="section.started.implementation"><H2><A name="section.started.implementation">2.3 Implementation</A></H2><P> The implementation idea of the window interface is quite simple. The graphics engine is executed by a separate operating system process (it runs in fact a modified <KBD>wish</KBD>). Any communication with the graphics engine is done via strings. The interface maps tickles and tickle messages to strings (this is done in a fairly efficient way). In the reverse direction, strings can be mapped back to Oz data types like integers, atoms, lists of integers or lists of atoms. </P><P> To get an impression of the efficiency of the implementation, try some examples, as well as the <A href="../demo/index.html">demos</A> and the <A href="../tools/index.html">tools</A> that come with Mozart. They are all built on top of the Tk window programming interface. </P></DIV><TABLE align="center" border="0" cellpadding="6" cellspacing="6" class="nav"><TR bgcolor="#DDDDDD"><TD><A href="node4.html#section.started.architecture">&lt;&lt; Prev</A></TD><TD><A href="node2.html">- Up -</A></TD></TR></TABLE><HR><ADDRESS><A href="http://www.ps.uni-sb.de/~schulte/">Christian&nbsp;Schulte</A><BR><SPAN class="version">Version 1.4.0 (20090610)</SPAN></ADDRESS></BODY></HTML>