Designed for attendees who are well into creating their own Web pages and want to make the interface more intelligent/responsive, want to include visualization and simulation, are getting ready to incorporate Java applets and/or Java Beans into their sites. Participants will learn the principles of Document Object Model and Dynamic HTML; create interactive page interfaces with scripting tools like Dreamweaver or Visual JScript; consider the pedagogical importance of visualizations and simulations; and explore how to combine relevant pre-made Java controls and applets together in a sound user interface. The workshop puts more emphasis on the reasons for incorporating particular interactivities into your pages, since the mechanics of scripting are handled largely by the tool. Developing Courses: Web Publishing, Developing Courses: Web Page Design, or equivalent experience is strongly recommended.
1. The Importance of Overall Course and Web Page Development Planning
How much work do you want to do?
Show source code for animation on Web Snapshot CD.
Open same file in Netscape 4.0
To fully incorporate HTML 4.0 specs for all browsers would require the following:
You can even resort to creating two or more entirely separate sites, one containing pages designed for IE 4.0, one for Navigator 4.0 and others for older browsers (see sidebar, "Getting Help"). Besides a lot of work, this approach requires a special, top-level redirector Web page that determines a user's browser and then automatically navigates the user to the root of the appropriate site.
With a bit of extra work and some compromises, it's also possible to create HTML tags and browser-aware scripts that display correctly under both Internet Explorer 4.0 and Navigator 4.0, and degrade gracefully under older browsers. If not, you can still resort to creating an alternate Web page for fossil browsers.
If your Web server supports Active Server Pages (ASP) or CGI, you can also write a server-side ASP script or CGI program to run a browser detect and generate a browser-specific page on the fly. This approach works with all browsers, since the scripts and programs run on the server, not in the user's browser.
Pictorius iNet Developer claims to be the first to solve this problem. Essentially, page information is stored in an internal database-type file and is served based on the incoming browser type. iNet recognizes the browser type and version and handles the request appropriately.
Of course, less than 50% of Web surfers use 4.0 browsers.
How Much Advanced Planning Should I
Do?
What Should Be Included in On-line
Syllabi?
How Are Web Lectures and
Presentations Different From Classroom Ones?
Why Build an Index for a Course
Web Site?
How Does On-line Testing and
Student Evaluation Work?
Go to Topic 2