Sophie: xconq-7.5.0-1.20050612.5mdv2009.1 i586

xconq-7.5.0-1.20050612.5mdv2009.1.i586.rpm

<HTML>
<HEAD>
<!-- This HTML file has been created by texi2html 1.39
     from ./hacking.texi on 12 June 2005 -->

<TITLE>Hacking Xconq - Startup Options</TITLE>
</HEAD>
<BODY>
Go to the <A HREF="hacking_1.html">first</A>, <A HREF="hacking_12.html">previous</A>, <A HREF="hacking_14.html">next</A>, <A HREF="hacking_35.html">last</A> section, <A HREF="hacking_toc.html">table of contents</A>.
<HR>


<H2><A NAME="SEC13" HREF="hacking_toc.html#SEC13">Startup Options</A></H2>

<P>
Although there are many different ways to get a game started, you have
three main categories of functionality to support: 1) selection of the
game to play, 2) setting of variants, and 3) selection of players.  For
command-line-using programs, the file <CODE>cmdline.c</CODE> need only be
linked in to provide all of this functionality.  For graphical
interfaces, you will need to design appropriate dialogs.  This can be a
lot of work, exacerbated by the fact that these dialogs will be the
first things that new <I>Xconq</I> players see, and will therefore shape
their opinions about the quality of the interface and of the game.

</P>
<P>
[more detail about what has to be in dialogs?]

</P>
<P>
Interface code should check all player specs, not proceed with
initialization until these are all valid.

</P>
<P>
Both standard and nonstandard variants should vanish from or be grayed
out in dialog boxes if irrelevant to a selected game.

</P>

<HR>
Go to the <A HREF="hacking_1.html">first</A>, <A HREF="hacking_12.html">previous</A>, <A HREF="hacking_14.html">next</A>, <A HREF="hacking_35.html">last</A> section, <A HREF="hacking_toc.html">table of contents</A>.
</BODY>
</HTML>