image file names

Author: davidfarmer

source/a-command-line-interface.ptx

@@ -10,7 +10,7 @@
     </p>
     <figure xml:id="fig-command-line">
       <caption>A command-line user interface.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="cmdline.eps"/>
     </figure>
     <p>
       The command-line approach might also be called
@@ -23,7 +23,7 @@
     </p>
     <figure xml:id="fig-console">
       <caption>The Java console window.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="console.eps"/>
     </figure>
     <p>
       In Chapter<nbsp/>3 we described how to use the <c>System.out.print()</c> and
@@ -43,7 +43,7 @@
     </p>
     <figure xml:id="fig-streams">
       <caption>Input and output streams.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="streams.eps"/>
     </figure>
     <p>
       Each Java program has three standard streams available to it at startup: <c>System.in</c>, <c>System.out</c>, and <c>System.err</c>.
@@ -71,7 +71,7 @@
     </p>
     <figure xml:id="fig-buffrdr">
       <caption>The <c>BufferedReader</c> class.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="buffrdr.eps"/>
     </figure>
     <p>
       <xref ref="fig-buffrdr">Figure</xref>
@@ -190,7 +190,7 @@ System.out.println("Your average pace was " +
     </p>
     <figure xml:id="fig-keybrdrdr">
       <caption>Design of the <c>KeyboardReader</c> class.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="keybrdrdr.eps"/>
     </figure>
     <p>
       <xref ref="fig-keybrdrdr">Figure</xref>
@@ -391,7 +391,7 @@ Hi, please input your name here > Kim
     </p>
     <figure xml:id="fig-greeter">
       <caption>Using <c>KeyboardReader</c> as the user interface.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="greeter.eps"/>
     </figure>
     <p>
       The full implementation of the <c>GreeterApp</c> class is shown in <xref ref="fig-greeterapp">Figure</xref>.

source/a-graphical-user-interface-gui.ptx

@@ -68,7 +68,7 @@
     <figure xml:id="fig-guiscreen">
       <caption>Various GUI components from the <c>javax.swing</c> package. <term>[Artwork: We
       need to label the components.]</term></caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="guicapture.eps"/>
     </figure>
     <p>
       The Swing classes are generally considered to be superior to their AWT \marginpar{Model-view-controller (MVC) architecture} counterparts.
@@ -137,7 +137,7 @@ public class GreeterApp extends Object { ... }
     <figure xml:id="fig-swing1">
       <caption>Top-level Swing and AWT classes. [NOTE: REDRAW JWindow
       is a subclass of Window.]</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="swing1.eps"/>
     </figure>
     <p>
       A <term>top-level container</term>
@@ -184,7 +184,7 @@ public class JFrame extends Frame { ... }
     </p>
     <figure xml:id="fig-framecapture">
       <caption>A simple window.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="framecapture.eps"/>
     </figure>
     <p>
       <xref ref="fig-framecapture">Figure</xref>
@@ -244,7 +244,7 @@ public class SimpleGUI extends JFrame
     </p>
     <figure xml:id="fig-framesubclass">
       <caption><c>SimpleGUI</c> is a subclass of <c>JFrame</c>.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="framesubclass.eps"/>
     </figure>
     <p>
       The constructor method illustrates how to use some of the methods inherited from <c>JFrame</c>. <xref ref="fig-framesubclass">Figure</xref>
@@ -276,7 +276,7 @@ public class SimpleGUI extends JFrame
     </p>
     <figure xml:id="fig-swing2">
       <caption>Swing components.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="swing2.eps"/>
     </figure>
     <p>
       Let's begin by creating a simple user interface,
@@ -317,7 +317,7 @@ public class SimpleGUI extends JFrame
     </p>
     <figure xml:id="fig-constructors">
       <caption>Public methods and constructors for basic Swing components.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="swingmeth.eps"/>
     </figure>
     <p>
       <xref ref="fig-constructors">Figure</xref>
@@ -382,7 +382,7 @@ add(String region, Component comp) add comp at region
     </p>
     <figure xml:id="fig-borderlayout">
       <caption>Arrangement of components in a border layout.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="border.eps"/>
     </figure>
     <p>
       Components are added to a border layout by using the <c>add(String
@@ -441,7 +441,7 @@ contentPane.add("South", inputPanel); // Add to JFrame
     </p>
     <figure xml:id="fig-eventmodel">
       <caption>Java's event model.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="eventmodel.eps"/>
     </figure>
     <p>
       In an event-driven programming model,
@@ -471,7 +471,7 @@ Repeat forever or until the program is stopped
     </p>
     <figure xml:id="fig-eventhier">
       <caption>Java's event hierarchy.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="eventhier.eps"/>
     </figure>
     <p>
       When the user clicks the <c>JButton</c>, Java will create an <c>ActionEvent</c> object.

source/abstract-classes-interfacesand-polymorphism.ptx

@@ -61,7 +61,7 @@
       That is, the method definition contains just the method's signature,
       not its body.
       Any class that contains an abstract method,
-      must itself be <image width="73%" source="chptr08"/> declared abstract.
+      must itself be <image width="73%" source="animals.eps"/> declared abstract.
       Here is the definition of the <c>Animal</c> class:
     </p>
 <pre>

source/adding-text-network-resourcesforan-application.ptx

@@ -164,7 +164,7 @@ while (line != null) {
     <figure xml:id="fig-realestategui">
       <caption>User interface design for the real
       estate application.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="15f11.eps"/>
     </figure>
     <p>
       The interface for this application is very important.
@@ -190,7 +190,7 @@ while (line != null) {
       borders, respectively.
       <xref ref="fig-realestategui">Figure</xref>
       illustrates these various design decisions.
-      <image width="73%" source="chptr15"/>
+      <image width="73%" source="p838f1.eps"/>
     </p>
   </subsection>
   <subsection>
@@ -261,7 +261,7 @@ http://java.trincoll.edu/&#126;jjjava/homes/
     <title>The <c>ImagePanel</c>Class</title>
     <p>
       We'll use a second class,
-      the <c>ImagePanel</c>, to handle displaying the image (Figs.<nbsp/>15.18 <image width="73%" source="chptr15"/> and <xref ref="fig-imagepanel"></xref>).
+      the <c>ImagePanel</c>, to handle displaying the image (Figs.<nbsp/>15.18 <image width="73%" source="p839f1.eps"/> and <xref ref="fig-imagepanel"></xref>).
       The reason we use a separate class for this task is that we want the image to appear in its own panel
       (which appears on the West border of the main window).
       In addition to its constructor,
@@ -447,7 +447,7 @@ private void showCurrentSelection() {
     <figure xml:id="fig-realestatescreen">
       <caption>The <c>RealEstate- Viewer</c> program
       downloads images and documents over the Web.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="15f14.eps"/>
     </figure>
     <figure xml:id="fig-realestateclass">
       <caption>The <c>RealEstateViewer</c> class, Part I.</caption>

source/agui-based-game-optional-graphics.ptx

@@ -39,7 +39,7 @@
     </p>
     <figure xml:id="fig-capture">
       <caption>The Sliding Tile Puzzle.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="captureGUI.eps"/>
     </figure>
   </introduction>
   <subsection xml:id="fig-GUIplayable">
@@ -74,7 +74,7 @@
       the GUI should pass this information to the game.
       The game should then decide whether or not that is a legal move and communicate this back to the GUI. Assuming it is a legal move,
       the game should also update its representation of the game's state to reflect that the tile array has changed.
-      And it should somehow make communicate the game's state to the GUI. <image width="73%" source="chptr09"/>
+      And it should somehow make communicate the game's state to the GUI. <image width="73%" source="GUIplayable.eps"/>
     </p>
     <p>
       Because it is impossible to know in advance just what form of data a game's moves might take,
@@ -120,7 +120,7 @@ private char puzzle[] = {'R','R','R',' ','L','L','L'};
  private int blankAt = 3;
 </pre>
     <p>
-      <image width="73%" source="chptr09"/> Note how we initialize the <c>puzzle</c> array with the initial configuration of seven characters.
+      <image width="73%" source="slidingtilepuzzle.eps"/> Note how we initialize the <c>puzzle</c> array with the initial configuration of seven characters.
       Taken together, these statements initialize the puzzle's state.
     </p>
     <p>
@@ -252,7 +252,7 @@ public class SlidingTilePuzzle extends ComputerGame
     </p>
     <p>
       Figure<nbsp/>9.39 provides a summary of the design.
-      As an implementor of the <image width="73%" source="chptr09"/> <c>ActionListener</c> interface, <c>SlidingGUI</c> implements the <c>actionPerformed()</c> method,
+      As an implementor of the <image width="73%" source="slidingGUI.eps"/> <c>ActionListener</c> interface, <c>SlidingGUI</c> implements the <c>actionPerformed()</c> method,
       which is where the code that controls the puzzle is located.
       The main data structure is an array of seven <c>JButton</c> s, representing the seven tiles in the puzzles.
       The buttons' labels will reflect the state of the puzzle.

source/an-overviewof-networks.ptx

@@ -33,7 +33,7 @@
     </p>
     <figure xml:id="fig-topology1">
       <caption>Star, bus, and ring topologies.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="15f1.eps"/>
     </figure>
     <p>
       In a star network (Fig.
@@ -70,7 +70,7 @@
     </p>
     <figure xml:id="fig-topology2">
       <caption>Tree and fully connected mesh topologies.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="15f2.eps"/>
     </figure>
   </subsection>
   <subsection xml:id="self-study-exercisesA36">
@@ -97,7 +97,7 @@
     <figure xml:id="fig-internet">
       <caption>An internet is a collection of distinct
       networks joined together by routers.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="15f3.eps"/>
     </figure>
     <p>
       The United Nations is an apt analogy for the <term>Internet</term>
@@ -233,7 +233,7 @@ [email protected]
       and one performed by the <term>server</term>
           <idx><h>server</h></idx>
       (Fig.<nbsp/>15.4).
-      <image width="73%" source="chptr15"/> For example, in the HTTP case,
+      <image width="73%" source="15f4.eps"/> For example, in the HTTP case,
       the Web browser plays the role of a client by requesting a Web page from a Web (HTTP) server.
       A Web server is just a computer that runs HTTP software<mdash/>a program that implements the HTTP protocol.
       For e-mail, the program you use to read your e-mail<mdash/>Eudora, Pine,
@@ -303,7 +303,7 @@ Server: Accept a request from a client and provide the service.
       Modern computer networks, such as the Internet,
       are organized into a number of levels of software and hardware.
       Each level has its own collection of protocols (Fig.<nbsp/>15.5).
-      <image width="73%" source="chptr15"/> The application level,
+      <image width="73%" source="15f5.eps"/> The application level,
       which contains the HTTP, FTP, SMTP, and DNS protocols,
       is the highest level.
       Underlying the application-level protocols are various
@@ -358,7 +358,7 @@ Server: Accept a request from a client and provide the service.
     <figure xml:id="fig-ipprotocol">
       <caption>Routers between individual networks use the
       IP protocol to translate one network protocol to another.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="15f6.eps"/>
     </figure>
     <p>
       As we have seen,
@@ -379,7 +379,7 @@ Server: Accept a request from a client and provide the service.
     </p>
     <figure xml:id="fig-nethier">
       <caption>The <c>java.net</c> package.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="p825f1.eps"/>
     </figure>
     <p>
       The <c>java.net.URL</c> class provides a representation of the \marginpar{java.net.*} Internet's Uniform Resource Locator that we described earlier.
@@ -396,7 +396,7 @@ Server: Accept a request from a client and provide the service.
       based on Internet packets.
     </p>
     <p>
-      <image width="73%" source="chptr15"/>
+      <image width="73%" source="15f8.eps"/>
     </p>
   </subsection>
 </section>

source/array-algorithms-searching.ptx

@@ -36,7 +36,7 @@
       If it is not found, then <m>-1</m> is returned to indicate failure.
     </p>
     <p>
-      <image width="73%" source="chptr09"/>
+      <image width="73%" source="p430f1.eps"/>
     </p>
     <p>
       The <c>Search</c> class (Figs.<nbsp/>9.15 and <xref ref="fig-search"></xref>) provides the Java implementation of the <c>sequentialSearch()</c> method.
@@ -201,7 +201,7 @@ Key  Iteration  Low   High    Mid
       So the search will terminate.
     </p>
     <p>
-      <image width="73%" source="chptr09"/>
+      <image width="73%" source="p432f1.eps"/>
     </p>
     <p>
       The <c>TestSearch</c> class (Figs.<nbsp/>9.17 and <xref ref="fig-testsearch"></xref>) provides a program that can be used to test two search methods.

source/case-study-a-two-player-game-hierarchy.ptx

@@ -65,7 +65,7 @@
       One way to answer this question is to generalize our current version of <c>OneRowNim</c> by moving any variables and methods that apply to all two-player games up to the <c>TwoPlayerGame</c> class.
       All subclasses of <c>TwoPlayerGame</c><mdash/>which includes the <c>OneRowNim</c> class<mdash/>would inherit these elements.
       <xref ref="fig-onerownim">Figure</xref>
-      shows the current design of <c>OneRowNim</c>. <image width="73%" source="chptr08"/>
+      shows the current design of <c>OneRowNim</c>. <image width="73%" source="onerownim.eps"/>
     </p>
     <p>
       What variables and methods should we move up to the <c>TwoPlayerGame</c> class?
@@ -112,7 +112,7 @@
     <figure xml:id="fig-twoplayergame">
       <caption><c>TwoPlayerGame</c> is the
       superclass for <c>OneRowNim</c> and other two player games.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="twoplayergame.eps"/>
     </figure>
     <p>
       To begin with,
@@ -691,7 +691,7 @@ public interface IPlayer {
       (We will leave the task of defining
 <c>NimPlayer</c>, a good player,
       as an exercise.)
-      <image width="73%" source="chptr08"/>
+      <image width="73%" source="nimplayer.eps"/>
     </p>
     <p>
       As an implementer of the <c>IPlayer</c> interface, <c>NimPlayerBad</c> will implement the <c>makeAMove()</c> method.
@@ -955,7 +955,7 @@ Sticks left: 0 Game over! Winner is Player 2 Nice game.
     <figure xml:id="fig-wordguessuml">
       <caption>Design of the <c>WordGuess</c>
       class as part of <c>TwoPlayerGame</c> hierarchy.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="wordguess.eps"/>
     </figure>
     <p>
       Let's call the game class <c>WordGuess</c>. Following the design of

source/case-study-an-n-player-computer-game.ptx

@@ -19,7 +19,7 @@
     <title>The <c>ComputerGame</c>Hierarchy</title>
     <figure xml:id="fig-game">
       <caption>Overview of the <c>ComputerGame</c> class hierarchy.</caption>
-      <image width="73%" source=".."/>
+      <image width="73%" source="nplayerwordguess.eps"/>
     </figure>
     <p>
       <xref ref="fig-game">Figure</xref>
@@ -76,7 +76,7 @@
       they remain hidden from all other classes.
     </p>
     <p>
-      <image width="73%" source="chptr09"/> The <c>ComputerGame(int)</c> constructor allows the number of players to be set when the game is constructed.
+      <image width="73%" source="computergame.eps"/> The <c>ComputerGame(int)</c> constructor allows the number of players to be set when the game is constructed.
       The default constructor sets the number of players to one.
       The constructors create an array of length <c>nPlayers</c>:
     </p>
@@ -313,7 +313,7 @@ Current word ???????? Previous guesses GLE
       players 0 and 1 are computers and player 2 is a human.
     </p>
     <p>
-      <image width="73%" source="chptr09"/>
+      <image width="73%" source="wordguesser.eps"/>
     </p>
     <p>
       In our new design,

source/case-study-the-one-row-nim-game.ptx

@@ -19,7 +19,7 @@
 <c>OneRowNim</c>, and a user interface object,
       for which we will use either a <c>KeyboardReader</c> or a <c>OneRowNimGUI</c>. One goal of our design was to develop the <c>OneRowNim</c> class so that it can be used,
       without changes,
-      with either a command-line interface or a GUI. <image width="73%" source="chptr04"/>
+      with either a command-line interface or a GUI. <image width="73%" source="ornuml.eps"/>
     </p>
     <p>
       Recall that we designed the <c>OneRowNim</c> class to maintain the state of the game and to provide methods that enforce the rules of the game.