Show/Hide <span> elements - starting over

[gbeacock]

Let’s try this again. For X-mas, I'm creating an HTML version of a Family Tree complete with biography information, photo galleries, and anything else I can squeeze in. I am producing as complete a biography of everyone as possible. Each section is written over top of each other and menu buttons are used to toggle the elements between 'visible' and 'hidden'.

I know one problem I have. I’m not sure where the semi-colon(;) is required. It seems to be needed in some places but not others.

I've put a skeleton set of the pages up at:

http://ca.geocities.com/gbea****/FamilyTree/Bea****/WilliamK/index.html

There are three elements at present, all shown upon loading. (I'll change that later so that only the basic data can be seen) Clicking on a button should set everything as hidden, then show the page called. I really don't see why this doesn't work.

The page is written with a lot of JS, because the available information for each person will be different for everyone. This is even more so since I am trying to include as much biographic information as possible


There are many files interconnected.

- index.js uses this file to build the page. It is the same file for everybody.
- data.js contains all their info and file names for biographic text sections (soon).
These work in conjunction with many common files to reduce downloading.
- styles.css contains all the styles being used, or in many cases, not used.
- scripts.js has all the functions used
- scripts2.js is a temporary file holding new functions
- Menu.js is not my own script but borrowed from:
http://developer.netscape.com/views...smith_menu.html


Any other info that would help. I can put it all into a .zip file if that would be of any use.

[gbeacock]

Thank-you

I am stupid. I am very stupid. I cannot spell. I hated spelling in school. I like word processors with spell checkers. I'm a bad bad boy. I fixed 'visable', but not 'visability'. I should be spanked :eek:

Seriously, I'd like to thank everybody and appologize for wasting your time. I'll probably be back with another stupid problem as this project develops.

All the writeln() is needed to make the code adaptable to different situations. innerHTML is not covered in my reference books, which were written for version 4 browsers. I'll check into that someday when I can afford to.

I understand this would be easier in XML and I'll look into that some day.

Again