Base Web Files
Welcome. This is meant to describe some of the base files that this site is probably likely to reference on pages from multiple distinct sections of the web page.
Below a description of the various components, some sample HTML for these base technologies is available.
Expanding an ancestor element doesn't result in the browser losing track of which descendents were previously visible before any earlier collapse of the ancestor.
The example sub-lists have been commented out of this page. Later sections of this page, such as the example code, service as a real-life example of deeply nested definition lists and so they can be used for testing. (The example code was, in fact, needlessly broken up into multiple sections for the clear purpose of being more deeply nested so it could serve as an example of a deeply nested definition list.)
This was made to be intentionally easy. Basically, the requirements on the webmaster are the fewest possible that perform the technical necessities:
The following loads DTTag and LinkNav. (Please respect licensing information, and customize the page references such as properly identifying the Copyright page.)
Having web pages run the initialization script can be a bit distracting if content, which the user is trying to view, collapses out of view (even if only temporarily before it is re-expanded) or is scrolled out of view due to other content that is collapsing.
Different web browsers may process the definition lists at different speeds. Therefore, testing the experience in one web browser (like Firefox 2) may make things seem much better than how the content ends up getting displayed in another web browser (such as MS IE 7). Having large definition lists (with dozens and dozens of items) may take well over ten and perhaps even thirty seconds even if the HTML file is loaded quickly. Any use of the hideem() function can therefore be quite distracting.
It is possible that some of this may be improved with different code, such as if initem() becomes enhanced to try to be more graceful with a BODY that isn't yet done loading. However, this does describe some potential experience with the current state of things.
After calling changeem(), do not expect that the function is compete until isChangeEmDone() indicates that it is complete. For example, calling changeem() multiple times could cause an earlier, more elaborate changeem() process (perhaps one affecting more list elements) to complete after a later, simpler call. The end result of what is showing and what is not showing may be something other than desired.
For now, all parents must be expanded in order for a child to be visibly expanded when the page begins. The code could be modified to automatically expand any ancenstors whenever a child is expanded. However, unless that was made into an option, that would limit possibilities. For example, on this page, expanding the “Example code” will cause some sections, like the Overview, to be expanded while the larger section of code remains collapsed. This may or may not have really good uses, but as this page shows, the capability for such hidden sub-expansions does exist.
A wrapper function expnamed() has been made. See example of partexp() in this HTML file for an example of how to use expnamed().
Although manually naming DT elements is not necessary just to implement basic expandability, manually naming DT elements is highly recommended as an easy to way reference what gets expanded and what doesn't. If the tags are not manually named, they can be expanded partially if they are properly referenced, but referencing the tags may be more difficult if they aren't given manually-assigned names.
Redistribution is permitted according to the license specified in the files.
[#lnknavfx]: The lnknavfx.js adds support for browsers that don't support :hover (such as MS IE 5.5) and shows how one can remove a reference to the linknav download site (which is done not to resist giving credit to the site, but rather just to make the widget smaller). No changes are needed to be made to the linknav.js or linknav.css file: just include this file as well. This LnkNavFx (LinkNav Fix) code is licensed for distribution with the same permissions granted by the LinkNav's license. (This is a simple script, and ideally the license would be this simple three word license: “No rights reserved.” However, LinkNav's license's “Share Alike” clause is more restrictive.)
Possible additions/changes that may be made: Add/document support for creating a custom footer, supporting title elements of LINK tags (as used by FGA: Providing "split horizon" DNS service as an example).
Coming... I wouldn't say coming soon, because these might take some time before it is launched.
Controls over embedded files, notably multimedia files such as music and movies, is something that TOOGAM is very likely to include on this site at some point in time.
Such supporting code does exist: some code had been developed to support multiple plug-ins (such as QuickTime and Windows Media Player) and browsers (including Microsoft Internet Explorer and Netscape Navigator), although the code was developed before Firefox. Making sure the code works okay with newer browsers is likely to be done before public release. Also, testing with mozplugger and Timidity is likely to be done as well.
The code used cookies to save preferences, so users could save whether they preferred one codec over another. (There may be various reasons for this: speed issues, cosmetics, or even how the output is played, which can be dramatically different quality with MIDI files.) There were plans (although this might not have been implemented yet) to allow the user to pick a task, such as picking a background music, and having it play uninterrupted as the user went from one web page to another. (This was done with an additional window, such as a legitimate and useful and non-intrusive use of a pop-under that would politely close when the main web page was left. This might not commonly work as well now that browsers have become more aggresive against less user-favorable usage of pop-up technologies.)
Another cool feature that was working was SAPI: having web pages speak to users. This began to work less well as unsigned ActiveX controls became less runnable, but there may be some potential in having this be released yet.
This is not included here for the intentions of recommending that others use it (in its current state). Instead, the reason this file is being mentioned is simply so that another file, that is used by this web page, is being publicly documented and made available.
This may be updated quite a bit before being recommended for widespread use. Counting on its contents is currently not a recommended practice.
This was initially named the “CSS for Operating System Installer Guide”. This was named after a guide that TOOGAM started working on. However, that guide has since evolved into a website called Cyber Pillar.
Start with something like this:
Be sure to also have a matching
Customize as desired:
<DL>tags are on a single page. Otherwise, the act of creating bars on the left (which is called "tabularizing", a term made by the creator of the code that does that) might be rather slow. By the end of the year 2016, that was still typically true. (Presumably that will eventually be sped up with newer hardware and/or software.) This can be seen on many pages on the Cyberpillar.com website. To rectify this, Cyberpillar.com would not "tabularize" a page that has more than a certain number of tags (or certain tags). However, Cyberpillar.com would show a “Tabularize” hyperlink in the right frame, so users could choose to Tabularize on their own.