CISC 370 Lecture Notes for Class No. 19 April 18, 2000

STILL UNDER CONSTRUCTION

Assignment

Reading:

Horstmann & Cornell,

Exercises:

Today's Lecture Topics

1. Term projects
   • Term project mile posts

     • Mile Post 1: Due Thursday, April 27:

       At this mile post you must have completed a significant portion of the initial design. This can be demonstrated either by turning in a definition of all the classes to be included in the final project that includes the data description and prototypes for all the significant methods or by turning in a complete initial implementation of some important piece of the overall design with a paragraph or two to explain its purpose and what additional is to be done.

     • Mile Post 2, Thursday, May 11:

       Full initial implementation due. Does not have to be debugged or running. Main purpose is to show that entire project has been planned along with an initial implementation.

     • May 25 & 26: Term projects due.

       A completed term project consists of all code plus relevant documentation that clearly identifies what you have done, what code/ideas you have borrowed from other sources with a complete reference to each source (i.e., an bibliography). Documentation must also clarify design and coding for the grader (BFC). The documentation should point out features of your design and code that you think are noteworthy. This should include positive as well as negative attributes (I will count off less for negatives that you point out and are aware of).

       I will schedule 20-30 minute periods for each project to be demoed and explained on April 25 and 26. April 26 is the normal final exam day for this course. Send me email no later than Tuesday, May 4 that tells me when you have scheduling conflicts on these two days plus any preferred times for your demo/presentation. The available demo/presentation times can be viewed on the presentation schedule web page.

       Grades for your term project will depend primarily on the finished project and the demo/presentation, but the material handed in at each milepost will influence the final grade.

2. See lecture 18 for important information on setting up use of (1) a Java 2 enabled browser for displaying web pages with applets that contain JApplets, and (2) the HTML converter that converts HTML code for use with the SUN Java 2 plug-in.

3. Applet HTML tags

   1. APPLET tag. This is the basic tag for invoking an applet from an HTML tag. In the future, when all browsers recognize the OBJECT tag, it should be used instead of APPLET. We will only use the APPLET tag in this course. For more information on the OBJECT tag see Horstmann & Cornell, pp. 551-3 or any good book on HTML 4.0.

   2. In addition to the APPLET tag, there are APPLET attributes that can be used with the APPLET tag. The most important ones for this course are
      • CODE - gives the name of the file that contains the compiled Java code for the applet. For example, TL_Applet.class. This file name is taken relative to the local directory/folder from which the currently display HTML file was found. You cannot use an absolute path name.
      • CODEBASE
      • WIDTH
      • HEIGHT
      • ALIGN
      • ARCHIVE - This attribute is important for minimizing the time required to load an applet and any associated Java classes.
      • NAME - This attribute is important for HTML pages that use frames. It also has other uses; see H&C, p. 552.

5. Passing information to applets A bar chart applet. You must have a Java 2 compliant browser to view this applet.

8. -->

Back to the CISC 370 homepage.

This page has been accessed times since 18 April 2000.

Corrections, suggestions and comments to Bob Caviness

Copyright 2000 B. F. Caviness