multi-page Specification

The multi-page format describes structure and names convention for files, used for presenting two-dimensional data (2D-info Space) in HTML and JavaScript.
Name of multi-page is the name of its main folder.
Structure
multi-page.html - starting file.

Sub-directories:

Content - actual content of the multi-page.
Browser - a program for 2D-info navigating.


Content

info-program.js - main content file.
Function Content describes data fragments for each available Instance and Level. They are variables with names in the fInstance[Level] format. For example, f001[3] begins definition of a fragment at first Instance and third Level.
The actual content is a string inclosed in double quotes.
Use no line breaks or double quotes in the string!
If your text includes double quotes, you will need to use " instead of them. The line breaks must be replaced with \n.
The fragment can include plain text or HTML code. In the latter case, it must exclude the following HTML tags:

  
<html> ... <body>, </body>, </html>

.
(Otherwise, the multi-page Browser will not be able to navigate between fragments: We have only one html document, containing a subset of fragments).

Folder Content/files is reserved for user's supporting files. For example, you can find there view.css stylesheet, background image, as well as Images and Sounds directories.
Parent folder for locating images is Content/files/Images.
For example, you can refer to
<img src="../../Content/files/Images/picture.gif"> .

For redirecting a specific fragment to another URL location, setting background sound or video, you can insert some JavaScript code. The code should refer to the following variables: NewURL, BgSound, and Video.

see examples

In addition, there are definitions for default Entry Level, Highest Level, and number of Instances. Also, variable Encoding may specify used character set.

There must be reserved at least ten empty arrays
for Instances (f001-f010), as current versions of
multi-page Browsers use that number as a constant.

Tip:
You can simply insert your data into existing multi-page framework, e.g., with help of WordPad. However, using special 2D-infoPad is a much better way for developing and supporting multi-pages effectively. All HTML tags, quotes, paths, and line breaks will be adjusted automatically. Besides, using "native" tools from author of multi-page format gurantees you are dealing with the most recent updates in multi-page technology.

meta.js - META information about the multi-page's content.
It includes definition of Title, Version, Date, Author, Copyright, and Synopsis. All these variables must be defined (use "" if they are empty or not used).

There must exist at least one non-empty fragment, -
at Instance one and entry Level!
The scale 1×1 (Instances×Levels) means a "flat", one-dimensional info space,
e.g., a conventional html or text document.


Browser

The multi-page Browser consists of two parts:

InfoEngine
Design

processor.js - main code for 2D-info navigation.
It's located in InfoEngine .

The Design forms visual appearance of the multi-page Browser. You may replace this folder with another version, or develop your own design.
Used files:

browser.js - general layout for Browser.
control.html - main control panel.
screen.html - main content display.
menu.html - reserved for user's needs
meta.html - support for displaying meta.
copyright.html - Browser's copyright message.
help.html - Browser's help page.

You can view your Content with different versions of Browser, - just assemble multi-page from required components!

check Download section for ready-to-use examples

If you want us to customize multi-page format to suit your specific needs (e.g., if you need a unique courseware shell), please contact here:
developer@2d-infospace.net

To view multi-pages written in international character encodings, make sure your Web browser is configured properly. For example, in Netscape 4.75 you need to select a required value in View--CharacterSet menu (with clicking SetDefaultCharacterSet). In MS Internet Explorer 6.0, use View--Encoding menu.