Cogito said:
Using as an example some code that I saw in a web site I managed to
create code that builds a hex to decimal table (which is incidental to
my questions).
I find it amazing how in such a small javascript program I can
generate such a sophisticated table including the generation of the
HTML code that builds the table. I'm sure that to the experts amongst
you this is old stuff.
After coding it I still have three questions:
1. In the sample code the whole thing works when invoked in the <BODY>
line:
<BODY leftMargin=0 onload=hextable() topMargin=0>
When I remove the 0 onload=hextable() from this line and place it as
hextable();
Do you mean like
<body hextable() ...>
If so then this is invalid. hextable() is being treated as an (invalid)
attribute of the <body> tag.
If you mean like
<body>
hextable()
....
then hextable() is merely content.
Perhaps you mean
<body>
....
<script type="text/javascript">
hextable();
</script>
In this case, however, the javascript must appear after (in your HTML) the
element whose id is sign.
Any suggestion how I can activate it from within the html part of the
code?
Er, see above.
2. Despite the fact that the code seems to generate the entire table
it still requires a table definition at the bottom part of the code
(it does not work when I remove it). What is the explanation for this?
No, it does not. All it needs is an element whose id is "sign". You have
provided this in your td element. What you really have is a nested table.
Turn on table borders (for both tables) and you will see what is hapenning.
Methinks what you really want is
<div id="sign"></div>
<script type="text/javascript">
hextable();
</script>
where the div is a catch all block level element avaible for use when no
other element fits the bill.
3. What is the meaning of the line:
sign.innerHTML=area
Area is a var where you have dumped a lot of text into. This text is,
incidentally, sort of valid HTML.
There is an element on the page whose id is sign.
sign.innerHTML=area plonks the content of your area var into the element, as
HTML, just as if you had hand coded it within that element when you wrote
the page.
Look up the specs on innerText. This plonks *content* into an element.
innerHTML plonks html code into the element. Yes, the browser reparses the
document object model and re-lays out the page. You may also like to explore
sign.innerText=area;
Of course innerHTML is a microsoft invention and as such will not work on
non-IE browsers.
Cheers
Richard.
