Chapter 5: Building the APP

Create the first Web page of your Web-based University Application for Administrators (which you will be enhancing throughout the rest of this book) with the following instructions:

1.
Create an HTML file with the name Splash.htm.

2.
Create an appropriate heading (title) for your application.

3.
Be sure to provide a title to appear in the browser window when this page is displayed.

4.
Add some introductory text explaining that this page is the introductory page to the rest of the University Application for Administrators Web site.

5.
Feel free to experiment with different font sizes, colors, faces, and emphasis (boldfacing and italicizing).

6.
Experiment with adding inline images and BODY tag attributes.

7.
Experiment with any of the other tags introduced in this lab (like annotating this page with comments).

Create your top navigational bar by following these directions:

1.
Create an HTML file called Top_Nav.htm.

2.
Display the heading “University Maintenance Application for Administrators”.

Create 3 hypertext links (inside a table so that they will be spaced horizontally evenly) called “Students”, “Instructors”, and “Classes”. For now, the HREF attributes for all 3 links will hold no value.

After you FTP these files to a Web server, everyone who has a frames-capable browser should be able to invoke your Main_Frame.htm file by typing its URL in a browser. When they do so, they should be able to see that your Top_Nav.htm file is loaded into the top navigational bar, while your Splash.htm file is loaded into the lower half (the main portion) of the screen. However, the way this page is currently coded, anyone using a browser that does not support frames will be greeted with an empty page.

To account for this possibility you can include the NOFRAMES tag. This tag and everything that follows it is read by browsers that cannot interpret frames, and ignored by those that can. For an example of how the NOFRAMES tag is used, include the following code in your Main_Frame.htm document:

<HTML> 
<HEAD> 
<TITLE>Main Frameset for the University Maintenance Web
site for Administrators</TITLE> 
</HEAD> 
<FRAMESET ROWS="25%, 75%"> 
<FRAME SRC="Top_Nav.htm" NAME="top"> 
<FRAME SRC="Splash.htm" NAME="main"> 
</FRAMESET> 
<NOFRAMES>
							<BODY><H2>
							Sorry.  This document uses frames.  But your
							browser does not support them.
							</H2></BODY>
							</NOFRAMES> 
</HTML>

Note that while the FRAMESET tag does not include a BODY tag, the NOFRAMES tag does.

In the preceding example, people using frames-savvy browsers will see your intended page, and those who cannot see frames will instead see the message written in the NOFRAMES section. Though the user will receive a message (better than nothing at all), it is actually better to create a page that delivers the same content, if not the same functionality, for non-frames viewers. This means you’ll have to put some thought into delivering another solution. Without frames, you might have to be a little more creative; you might have to work out a solution using tables, for instance.

After you’ve created your Top_Nav.htm file and Main_Frame.htm file, load your Main_Frame.htm file into your browser to ensure that your Top_Nav.htm and Splash.htm files are being loaded properly into the page painted by Main_Frame.htm. An example of what you should be working towards can be seen in the companion Web site for this book, located at http://www.phptr.com/boardman. Visit the Web site periodically to share and discuss your answers with other readers.


..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.221.140.111