Look at also other topic groups, which I have done!
You can return to this topic group by using this menu and the link Table of topic groups in the top of the page.
Both frame and table systems have difficulties to build navigation system to big page groups. What could be the best system?
I have used complex frame system in order to get short link paths. My principle is "if you in any page, you can get to any other page with one to three clicks!" I don't however regard my system in every respect the best available. The ideal solution in my mind is to separate navigation and information partially from each others like CSS and the HTML file.
This system does have however some problems:
<A href="../Seurakunta/vasen_alue.html" target="_blank" value="top:30;left:30; width:630; height:400">
<A href="../Seurakunta/vasen_alue.html" target="left" value="top:30; left:30; width:630; height:400;" href="../Seurakunta/Virheet.html" target="center">. At this system the user could exchange the content of several frames at the same time, but he would not need to exchange the whole frameset neither use block level frame systems like I have designed.
idattribute), if it is not a frame-document. A frame document has a name or a fragment identifier, for example
<FRAME name ="textpage" id="textpage" ...>). But if the HTML would have the possibility to give the
idattribute to all documents and there could be the possibility of multi linking the system could work better. Lets make an example so that the idea become more obvious:
<html id="navipage" ... >.
<A href="navipage.html" target="navipage"; a href="something.html" target="textpage">;. They are opened at the same time and there is no need to open other documents. These two documents would work like a frame-document, but they would be independent. Both documents could be put into the bookmarks lists. I hope, that in future the root element could have core attributes and the
idattribute could" communicate" with each other and both could change the content of the other document.
target="mainWindow". At that way only two windows are needed and any window doesn't need to close.
XML has XLink. It might solve some navigation problems, but it doesn't necessary do, what I mean (I have not read thoroughly the documentation).
If my suggestion could be somehow automated, it does have following advances:
For personal use it is easy today make this kind of system with Opera! Opera can save as name the whole window system and user can open these saved files (Preferences > Save Window Settings - File > Open). If other browsers could do the same, instead of frame set files, browsers could use window saving files. The page designer gives the downloadable starting set, but the user could exchange it and save it with an another combination. The whole window is in use and what bigger screen, the more powerful system - with small devices is impossible to reach this efficiency. This system is ideal for scientist, which needs to compare materials with each others.