|
The first page was created in Macromedia Dreamweaver and uses Hide and Show layers behaviors in a timeline. The images themselves don't move. A single image is repeated in all the layers and for the later layers it's oversized using the width and height attributes of the image tag.
At the end of the sequence, the browser model is checked, again using code written by Dreamweaver. Netscape viewers go to a page that tells them some of the subsequent windows will be less lively in Netscape than in Internet Explorer. All visitors are then transferred to a plain black page (amazing1).
This page holds the JavaScript code that launches the progressive empty window. The code is public freeware. When the window fills the screen, it loads itself with an HTML page (amazing2). At this stage there are two windows open.
Amazing2 now launches its own new window (amazing3) which is the blue window, making three windows open in total. It also pre loads a picture (amazingtrans.gif) without showing it. Dreamweaver code is used in both cases.
The blue window (amazing3) contains hand-coded JavaScript that moves it across the screen. In IE it eventually leaves the screen almost completely. This window also contains JavaScript code to close itself when the movement has finished.
Meanwhile amazing2 shows the picture amazingtrans.gif, which is solid black with the letters Amazing HTML written in the middle as a transparent section. A flame picture is loaded behind this image and moved up in a repeating loop, giving the impression of continuous movement. It's hard work on the graphics side for your computer processor, so it can be jerky.
Eventually, amazing2 also self-closes. If the timing is right (and it isn't always), the window hidden in the background, amazing1, moves to a new URL just before this happens.
Now only the original window is open, at the page that finishes the sequence.
See the sequence again
Back to the finish page
|
