Play with this set of frames .. use the example provided and click on
Go!
The source document will end up in this frame, the analysis in the
frame on the right. Using your mouse you can
shift the frame boundary that
separates this document from the analysis section.
Big brother is holding both your hands
If you try and type in a URL outside our domain (anaesthetist.com) then
the analysis will fail miserably! No, don't blame us, blame the paranoid
androids who wrote JavaScript. 'For security reasons' they've crippled
JavaScript so that two frames containing documents from different domains
cannot talk to one another. Period. You yourself can read the source of
a document, but you cannot use JavaScript to view the image of this source
on your computer. If you want to use our page to examine your own
pages, save the frame components to disk, and then use them locally on
your machine!
How did we do it?
It's probably best to view the source of the frames and each
individual document. The only substantial part is the HTML document
f_base, that makes up the top frame. (To view the source, right click
on the top frame). We write the properties
of the page you specified using the
for .. in
construct (discussed in part six) to step through all the properties of the page.
The wrinkle is that we make each property a link, and the link
allows you to invoke another function we've defined within f_base
called Deeper. Deeper allows us to either display properties
of the item (if it's a string or number) or open up another
window, with the 'sub-properties' of the object selected. And so on..
By the way..
We note that in the Ecma specification for 'EcmaScript' there are
ways of hiding components from for .. in. Does this surprise you?
An irritation
Some time or another we'll get around to fixing the following
problem - when you open multiple nested windows and then close
the topmost one (after viewing a datum) you'll find that the
other windows are hidden behind the main window, so they tend
to become lost. A pain.