cpt.hitp-webpage-language-set
cpt.html5.id.toc.preview-webpage-language-set
with Html5, Ids, Table-of-contents, link-Preview

hitp'Description

Description:
HITP (html5.id.toc.preview) is a-LANGUAGE-SET (format|method) for publishing WEBPAGES of title-content-tree structured-documents with these advantages:
1) Html5: no need for special programs to read them, as all machines have the needed browser (= html reader). Also html5-elements structure the-text for humans and machines.
2) Id: anyone can-refer to ANY PART of them, because all their html-elements have IDs.
3) Toc: automatically created expandable table-of-contents makes reading easy.
4) Preview: same domain link-preview makes reading fast.

With these attributes and by connecting the-names of the-sentences with their definitions using preview-links, we can-create our electronic-documents subjectively MONOSEMOUS, easily readable by humans and machines.
Knowledge of HTML, CSS, Browser-JavaScript is a-prerequisite to read the-rest of this page.

Artificial-intelligence will never succeed to understand today's polysemous unstructured-info[1] (only a portion of it will manage), for the simple fact it[1] is polysemous!!!
The creation of monosemous-structured-documents is a-prerequisite to manage the enormous quantity of human-information with the-help of machines.

hitp'Name

Name:
• cpt.Html5IdTocPreview,
• cpt.html5.id.toc.preview,
• cpt.generic-specific-pair--webpage, {2013.09.01}
• cpt.html5.id.toc.preview--webpage-format,
• cpt.html5.id.toc.preview--page-format,
• cpt.html5IdTocPreview--webpage-format,
• cpt.hitp--webpage-format,
• cpt.hitp--webpage-application-format,
• cpt.hitp--web-page-format,
• cpt.hitp--page-format,
• cpt.title-content-tree--webpage-format,
=== Abbreviation:
• cpt.hitp,

hitp'Archetype (the-doc)

Description:
Archetype is the-entity we want to model with a-format, or a-language.
A-hitp-archetype or a-TITLE-CONTENT-TREE-DOCUMENT, is a-document (= recorded information) with a title-content-tree structure.

Name:
• cpt.hitp'archetype,
• cpt.hitp'archetype-document,
• cpt.hitp'archetype-tree,
• cpt.hitp'archetype-whole-part-tree,
• cpt.hitp'archo-doc,
• cpt.hitp'archo-root-tree,
• cpt.hitp'doc,
• cpt.hitp'document,
• cpt.hitp'root-tree,
• cpt.hitp'structured-document,
• cpt.hitp'title-content-tree-document,
• cpt.document,
• cpt.doc,
• cpt.title-content-document,
• cpt.tcd,
• cpt.title-content-tree-document,
• cpt.tctd,

hitparcho'Title-content-tree

Definition.Recursive:
START-CONDITION:
A-title-content-tree is a-whole-part-tree of 1) INFO-TITLE: the-parent-node and 2) INFO-CONTENT: an order-set of info-doc-units and part title-content-trees (subtrees), the-children-nodes.
END-CONDITION:
Leaf-subtrees consist of 1) a-title and 2) an order-set of info-doc-units.

Name:
• cpt.hitp'info-title-content-tree,
• cpt.hitp'archo-tree,
• cpt.title-content-tree,
• cpt.tct,

Part:
title,
content,
node,
level,
depth,

Specific:
bottom-tree,
leaf-tree,
root-tree,
subtree,

hitparcho'tree.BOTTOM

Definition.Specific:
Bottom-tree is a-tree whose content contains bottom-nodes.

Name:
• cpt.hitp'archo-tree.bottom,
• cpt.hitp'archo-bottom-tree,
• cpt.title-content-tree.bottom,

hitparcho'tree.LEAF

Definition.Specific:
Leaf-tree is a-tree whose content contains only doc-units.

Name:
• cpt.hitp'archo-tree.leaf,
• cpt.hitp'archo-leaf-tree,
• cpt.title-content-tree.leaf,

hitparcho'tree.ROOT

Definition.Specific:
Root-tree is the outermost tree in a-title-content-tree-document.
Its title, the-root-title, has no parent.

Name:
• cpt.hitp'archo-tree.root,
• cpt.hitp'archo-root-tree,
• cpt.title-content-tree.root,

hitparcho'tree.SUBTREE

Definition.Specific:
Subtree is a-tree which is part of the-content of another tree.

Name:
• cpt.hitp'archo-tree.subtree,
• cpt.hitp'archo-subtree,
• cpt.title-content-tree.subtree,

hitparcho'Title

Description:
An-archo-title is text (a-name or a-phrase) that describes an-archo-content.
Sometimes, a-title is generic-information and a-content specific.

Name:
• cpt.hitp'archetype--info-title,
• cpt.hitp'archetype-title,
• cpt.hitp'archo-title,
• cpt.title-content-tree'title,

hitparcho'title.Root

Description:
Root-title is-called the outermost title-node in the-archetype-tree.

Name:
• cpt.hitp'archetype--root-title,
• cpt.hitp'archetype--root-node,
• cpt.title-content-tree'title.root

hitparcho'Content

Description:
Archo-content[1] is the-children of an-archo-title.
It[1] is an order-set of info-doc-units and info-title-content-trees.

Name:
• cpt.hitp'archetype--info-content,
• cpt.hitp'archo-content,
• cpt.title-content-tree'content,

hitparcho'Doc-unit

Description:
Archo-doc-unit is
- a-paragraph-with-sentences: an order-set of sentences, or
- a-paragraph-with-subparagraphs: an order-set of group of sentences separated with empty lines, or
- a paragraph-with-nonsentences: a-paragraph plus images, audios, videos, lists, tables, trees.

Name:
• cpt.hitp'archetype--info-doc-unit,
• cpt.hitp'archo-doc-unit,
• cpt.title-content-tree'doc-unit,

hitparcho'Table-of-contents

Description:
Archetype-table-of-contents is a-whole-part-tree with nodes the-titles of the-archo-doc.

Name:
• cpt.hitp'archetype-table-of-contents,
• cpt.hitp'archetype-toc,
• cpt.hitp'archo-toc,
• cpt.title-content-tree'toc,

hitparcho'Node-of-tree

Description:
The-nodes of the-archo-tree are of two types: archo-doc-units or archo-titles.

Name:
• cpt.hitp'archetype-node-of-tree,
• cpt.hitp'archetype-node,
• cpt.hitp'archo-node,
• cpt.title-content-tree'node,

Specific:
• ancestor-node,
bottom-node,
• child-node,
• descendant-node,
leaf-node,
• parent-node,
root-node,
• sibling-node,
top-node,

hitparcho'node'number

Description:
Every node has 2 numbers that denote its distance from the-top (root) and the-bottom of the-tree.

Name:
• cpt.hitp'archetype-number-of-node,
• cpt.hitp'archo-node-number,
• cpt.hitp'depth-number-of-archo-node,
• cpt.hitp'number-of-archo-node,
• cpt.title-content-tree'node-number,

Specific:
root-number-of-node,
bottom-number-of-node,

hitparcho'node'number.ΒΟΤΤΟΜ

Description:
Bottom-number of a-node is its distance from the-bottom.
The-bottom-node has 0 bottom-number.
The-root-node has the-highest bottom-number.

Name:
• cpt.hitp'archetype-bottom-number-of-node,
• cpt.hitp'archo-node-bottom-number,
• cpt.hitp'height-number-of-archo-node,
• cpt.hitp'bottom-number-of-archo-node,
• cpt.title-content-tree'node-number.bottom,

hitparcho'node'number.ROOT

Description:
Root-number of a-node is its distance from the-top (root).
The-root has 0 root-number.
A-bottom-node has the-highest root-number.

Name:
• cpt.hitp'archetype-root-number-of-node,
• cpt.hitp'archo-node-root-number,
• cpt.hitp'depth-number-of-archo-node,
• cpt.hitp'root-number-of-archo-node,
• cpt.title-content-tree'none-number.root,

hitparcho'node.BOTTOM

Description:
Bottom-node is a-node with the-highest root-number.

Name:
• cpt.hitp'archetype-bottom-node,
• cpt.hitp'archo-node.bottom,
• cpt.title-content-tree'node.bottom,

hitparcho'node.LEAF

Description:
Leaf-node is a-node without children.

Name:
• cpt.hitp'archetype-leaf-node,
• cpt.hitp'archo-node.leaf,
• cpt.title-content-tree'node.leaf,

hitparcho'Level-of-tree

Description:
Level-of-tree is the-set of nodes with the-same number.

Name:
• cpt.hitp'archetype-level-of-tree,
• cpt.hitp'archetype-level,
• cpt.hitp'archo-level,
• cpt.title-content-tree'level,

hitparcho'Depth-of-tree

Description:
Depth-of-tree is the-number of its levels.

Name:
• cpt.hitp'archetype-depth-of-tree,
• cpt.hitp'archetype-depth,
• cpt.hitp'archo-depth,
• cpt.hitp'archetype-height-of-tree,
• cpt.hitp'archetype-height,
• cpt.hitp'archo-height,
• cpt.title-content-tree'depth,

hitp'Model (the-webpage)

Description:
A-hitp-webpage is a special webpage which contains the-hitp-doc[1] which[1] maps|represents|denotes|models a-title-content-tree-doc.
Its information is structured for humans and machines.
The-webpage contains and extra information apart of the-doc, such as meta-info and site-info.
It is-written in 3 computer-languages, because it is a-web-application:
HTML: for the-structure of the-information,
CSS: for its presentation,
Browser-JavaScript: for its processing.

Name:
• cpt.hitp'code,
• cpt.hitp-code,
• cpt.hitpcode,
• cpt.hitp'model,
• cpt.hitp-model,
• cpt.hitppage,
• cpt.hitp'page,
• cpt.hitp-page,
• cpt.hitp'webpage,
• cpt.hitp-webpage,
• cpt.hitpwpg,

hitpwpg'Browser-compatibility

Description:
• Hitp is-tested on modern {2016} browsers on win10: Chrome, Firefox, Safari, Edge, IE11.

Name:
• cpt.hitp'browser-compatibility,
• cpt.hitp'browser-support,

hitpwpg'Download

Name:
• cpt.hitp'download,

GitHub-site:
Since version.10.2014-08-05.valuenames I published the-code on GitHub.
https://github.com/synagonism/hitp/.

To use the online files, use the-latest-files on the-project-page on GitHub.
http://synagonism.github.io/hitp/hitp.html.
http://synagonism.github.io/hitp/hitp.css.
http://synagonism.github.io/hitp/hitp.js.

Synagonism-site:
hitp.14.2016-06-09.title-content-tree,
v.12.2016-01-24.toc-icons,
v.11.2015-10-26.preferences,
v.10.2014-08-05.valuenames,
v.08.2014-01-09.toc,
v.07.2013-11-06.tabs,
v.05.2013-07-15.toc-algo,
v.04.2013-06-27.html5.id.toc.preview,
v.03.2013-04-14.preview,
v.02.2013-04-01.toc,
v.01.2011-02-17.html5.id,

hitpwpg'Components

Every hitp-webpage is comprised of:
• one html-file with the main content,
• one css-file,
• one js-file,
• one optional directory with all other needed files such as pictures, audio, video, css, etc.
The-name of the-directory is the-same with the-name of the-html-file plus the '.files' extension.

Name:
• cpt.hitp'components,

hitpwpg'Directory

Description:
This directory contains all the extra files needed for the-hitp-file.
Its name is the-name of the-hitp-file plus '.files'.

Name:
• cpt.hitp'dir,

hitp'webpage'HTML

Description:
Html defines the-structure of a-hitp-webpage and stores the-archo-doc.

Name:
• cpt.hitphml,
• cpt.hitp'html,
• cpt.hitp'code'html,
• cpt.hitpcode'html,

hitphml'HTML5

Description:
We use the HTML5-elements section, header, footer to create the-parts of a-hitp-page that map a-title-content-tree-doc.

Name:
• cpt.hitp'html5,

hitphml'Title-content-tree

Description:
A-hitp-title-content-tree maps an-archo-title-content-tree.
We use the section, header, footer and p elements to create hitp-trees.

Name:
• cpt.hitp'title-content-tree,
• cpt.hitp-title-content-tree,
• cpt.hitp'webpage-tree,
• cpt.hitp'tree,
• cpt.hitp-tree,
• cpt.hitptree,
• cpt.hitptct,

Part:
title-of-hitp-tree,
content-of-hitp-tree,
doc-unit-of-hitp-tree,

Specific:
footer-tree,
header-tree,
meta-tree,
p-tree,
root-tree,
section-tree,

hitptree.ROOT

Description:
A-hitp-root-tree (a-hitp-doc) maps|represents an-archo-root-tree (a-title-content-tree-doc).
We use a-header and an-h1 elements to create the-title, and an-ordered-set of h1-trees with last a-footer-tree to create the-content of the-root-tree.
The-header-element is the first child of the-body-element.
<header id="idHeader">
  <h1 id="idHeaderH1">Title
  </h1>
</header>

<section id="idName">
  <h1 id="idNameH1">Title
    </h1>
  content
</section>

<footer id="idFooter">
  <p id="idFooterP1">Title:
    doc-units
    </p>
</footer>

Name:
• cpt.hitp'tree.header,
• cpt.hitp'header-tree,
• cpt.hitp'tree.root,
• cpt.hitp'root-tree,
• cpt.hitp-root-tree,
• cpt.hitp-document,
• cpt.hitp-doc,

Depth:
The biggest depth of a-hitp-doc is 6+1.
This is because the-heading-elements h1 ... h6 are 6 and thus a-section-tree can have only 5 subtrees.
The extra depth we get from p-trees.

PROPOSAL: Because many documents use deeper depth than 7 (even-though I do-not-think it is a good practice) I proposed on {2010.10.24} in public-html-comments@w3.org list to use all the single-digit numbers 0-9 as html-headings.

hitptree.SECTION

Description:
A-section-tree is a-tree in which we use the-section-element as a-container, a-heading-element for its title and for its content, doc-units or other section-trees.
The-subtrees of a-section-tree have ordered titles in the form h1, h2, h3, h4, h5, and h6.
<section id="idName2">
<h2 id="idName2H2">Title2
  </h2>
<p>Sentence1.
  Sentence2.
  </p>
  
<section id="idName3">
<h3 id="idName3H3">Title3
  </h3>
<p>Sentence1.
  Sentence2.
  </p>
</section>
</section>

Name:
• cpt.hitp'tree.section,
• cpt.hitp'section-tree,
• cpt.hitp-section-tree,

Specific:
• h1-section-tree (has h1-element as title),
• h2-section-tree (has h2-element as title),
• h3-section-tree (has h3-element as title),
• h4-section-tree (has h4-element as title),
• h5-section-tree (has h5-element as title),
• h6-section-tree (has h6-element as title),

hitptree.FOOTER

Description:
A-hitp-footer-tree is an optional special tree, last child of the-root-tree.
It is-created with the-footer-element, with no title, and content document-units with text that ends the-text of the-doc.
<footer id="idFooter">
  <p id="idFooterP1">Title:
    doc-units
    </p>
</footer>

Name:
• cpt.hitp'tree.footer,
• cpt.hitp'footer-tree,
• cpt.hitp-footer-tree,

hitptree.P

Description:
A-hitp-p-tree is always a-leaf-tree we create with the-p-element.
Its-title is the first line which ends with ':'.
Its-content contains only doc-units.
<p id="idName">Title:
  sentences or subparagraphs
  </p>
//or
<div id="idName">
<p>Title:
  Sentence1.
  Sentence2.
  </p>
  <table>
  ...
  </table>
</div>

Name:
• cpt.hitp'tree.p,
• cpt.hitp'p-tree,
• cpt.hitp-p-tree,

hitptree.Meta

Description:
A-webpage-meta-tree is a special section-tree, which is NOT PART of the-root-tree.
It contains meta-info about the-doc such as versions, comments, support etc.
<section id="idMeta">
<h1 id="idMetaH1">Meta-Info
  </h1>
  content.meta
  <p id="idMetaWebpage_path"><span class="clsB clsColorGreen">Page-path</span>:
    hitp-webpage
    ∈ synagonism.net
  </p>
</section>

Name:
• cpt.hitp'tree.meta,
• cpt.hitp'meta-tree,
• cpt.hitp-meta-tree,

hitphml'Title

Description:
A-hitp-title maps an-archo-title[1].
We use the-heading-elements (h1, h2, ... h6) to implement it[1]:
<h1 id="idName">title</h1>
or the first line of a-p-element ending with ':'
<p id="idName">title:
  doc-unit
  </p>

Name:
• cpt.hitp'title,
• cpt.hitp-title,
• cpt.hitp'webpage-title,

hitphml'Content

Description:
A-hitp-content maps an-archo-content.
It contains hitp-doc-units and other hitp-trees.

Name:
• cpt.hitp'content,
• cpt.hitp-content,
• cpt.hitp'content-of-tree,

hitphml'Doc-unit

Description:
A-hitp-doc-unit maps an-archo-doc-unit.
It is-created with p-elements and inline elements, or we use a-div-element as a-container if and extra block elements like ol, ul, table create the-doc-unit.

Name:
• cpt.hitp'doc-unit,
• cpt.hitp-doc-unit,
• cpt.hitp'document-unit,

Specific:
paragraph-with-sentences-doc-unit,
paragraph-with-subparagraphs-doc-unit,
paragraph-with-nonsentences-doc-unit,

hitpunit.Paragraph-with-sentences

Description:
For readability, we put every sentence in a new line.
<p id="idName">Sentence1.
  Sentence2.
  SentenceLast.
  </p>

Name:
• cpt.hitp'doc-unit.paragraph-with-sentences,
• cpt.hitp'doc-unit.sentences,
• cpt.hitp'sentences-doc-unit,

hitpunit.Paragraph-with-subparagraphs

Description:
<p id="idName">Sentence1.
  Sentence2.
  
  Sentence3.
  SentenceLast.
  </p>

Name:
• cpt.hitp'doc-unit.paragraph-with-subparagraphs,
• cpt.hitp'doc-unit.sentences,
• cpt.hitp'sentences-doc-unit,

hitpunit.Paragraph-with-nonsentences

Description:
<div id="idName">
<p>Sentence1.
  Sentence2.
  </p>
  <table>
  ...
  </table>
</div>

Name:
• cpt.hitp'doc-unit.paragraph-with-nonsentences,
• cpt.hitp'doc-unit.nonsentences,
• cpt.hitp'nonsentences-doc-unit,

hitphml'File

Description:
The-html-file is the main file of the-webpage.
See the-example-file on github.

Name:
• cpt.hitp'html-file,
• cpt.hitp'file,
• cpt.hitp-file,

hitphml'IDs

Description:
The core concept (and first motive) of our-proposal is the-addition of ID-attributes on all elements of a-hitp-page.
For example:
<h1 id="idXxxx">...
<p id="idYyyy">...

Now we can-refer to any part of the-document!!!

Name:
• cpt.hitp'id,
• cpt.hitp-id,

The-IDs must-be unique:
You can-use as ID whatever you want.
We sugest to begin with "id" in-order to be-distinguished from other words in the-text and do-not-contain spaces.
For example:
id, idHeader, idHitpidx-income, ...

The-IDs must-be visible to the-reader:
The-reader, in-order to REFER to any part of the-document, must-know the-ID of this part of the-file.
This can-be-done by adding a hidden element in this part of the-file that will-be-visible when the-mouse is over this text.
But if this hidden-element is and a-link-element, then the-reader could-copy the-address of this part of the-file from the-address-bar of his browser.
Here is an-example of the simple code we have to add to reach our goal.
<p id="idYyyy">...
  <a class="clsHide" href="#idYyyy"></a></p>

With this code, when the-reader has the-mouse over an-HTML-element (a part text), at the-end appears the-id-link-symbol .
Clicking on this symbol, s|he can-see the-ID of this text and s|he can-copy from the-address-bar the-address of this particular part of the-text.
The-paragraph you are-reading now has the-feature we are-talking about and you can-experiment with it.
We can-set IDs, if we need them, on every SENTENCE in a-paragraph.

ID-Patterns:
If the-author of a-doc uses patterns to write the-IDs of a-text-file, it helps the-reader to quickly identify the-parts of the-file.
Examples:
- idA4 (article)
- idA4P2 (paragraph)
- idP2 (Part)
- idP2C2 (Chapter)

NOTATION: the-ID of a-heading-element is the-ID of its section-element plus H1, H2, etc.
This way we can-link and preview the-part of the-doc with this heading.

hitphml'Links

Description:
By setting IDs in all elements of a-text, we can-refer to any part of a-document.
Then we can-use links in all places in a-text we refer to another place inside a-document or outside of it.
Law-texts are full of references.
Find the-references it is difficult and sometimes impossible.
If the-references are "one click away", then reading law will become easier.

Name:
• cpt.hitp'link,

hitphml'Math-formulas

Name:
• cpt.hitp'math,

Description:
Using MathJax we can-have "beautiful math in all browsers". For example: x = b ± b 2 4 a c 2 a
HOW:
1. we need to add the following code inside the-head-element:
<script src="http://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML"></script> and
2. create the-math-code. An easy method is from the online site ShareMath.

hitp'webpage'CSS

Description:
CSSs separate content from presentation.
We use a-css-file for harmonization in the-appearance of documents and for the-toc creation.
You need the following code to use it:
<link href="http://synagonism.github.io/hitp/hitp.css" rel="stylesheet" type="text/css" />
You can-store the-hitp.css-file AND in your server.
Also you can modify the-appearance

Name:
• cpt.hitpcss,
• cpt.hitp'css,
• cpt.hitp'code.css,

hitpcss'class

Description:
Like the-IDs, the-name of all css-classes begin with 'cls'.
Below is the-code of the-classes I am-using.

Name:
• cpt.hitp'css'class
• cpt.hitp'cls,
• cpt.hitpcls,

hitpclsCenter {
  text-align: center;
}

hitpclsCenterBlock {
  display: block;
  margin-left: auto;
  margin-right: auto;
}

hitpclsCenterInline {
  display: block;
  text-align: center;
}

hitpclsBtn {
  border-radius: 5px;
  font-size: 12px;
  margin: 2px 0 5px 12px;
}

hitpclsBtn:hover {
  background: #e0f2f7;
  color: red;
}

hitpclsColorBlue {
  color: #0000ff;
}

hitpclsColorGreen {
  color: #008000;
}

hitpclsColorGreenBg {
  background-color: #008000;
}

hitpclsColorRed {
  color: #ff0000;
}

hitpclsColorYellow {
  color: #FFFF00;
}

hitpclsColorYellowBg {
  background-color: #FFFF00;
}

hitpclsEditor {
  background: transparent;
  color: #999999;
}

hitpclsFontGrExt {
  font-family: "Palatino Linotype";
}

hitpclsFontGrMg {
  font-family: MgPolNewTimes;
  font-size: 16px;
}

hitpclsFontSerif {
  font-family: Serif, "Times New Roman", Georgia;
}

hitpclsFontSansserif {
  font-family: SansSerif, "Microsoft Sans Serif", Arial, Dialog, Tahoma;
}

hitpclsFontMonospaced {
  font-family: Monospaced, "Courier New", Courier;
}

hitpclsFontScript {
  font-family: Script "Monotype Corsiva";
}

hitpclsFontDecorative {
  font-family: Wingdings;
}

hitpclsPagePb {
  display: block;
  text-align: right;
  color: green;
}

hitpclsHide {
  //misc attributes that hide id-link and expose it by hovering.
}

hitpclsSizeSmall {
  font-size: small;
}

hitpclsSizeSmallX {
  font-size: x-small;
}

hitpclsSizeMedium {
  font-size: large;
}

hitpclsSizeLarge {
  font-size: large;
  font-weight: bold;
}

hitpclsSizeLargeX {
  font-size: x-large;
  font-weight: bold;
}

hitpclsB {
  font-weight: bold;
}

hitpclsBU {
  font-weight: bold;
  text-decoration: underline;
}

hitpclsU {
  text-decoration: underline;
}

hitpcss'File

Description:
You can-download this file, or use the online one.

Name:
• cpt.hitp'css-file,
• cpt.hitp'file.css,

hitp'webpage'Browser-JavaScript

Description:
Browser-JavaScript does the-information processing on the-page.
- creates the-toc and inserts into the-page.
- makes the-width of toc-container dynamic.
- adds preferences on the-page.
- adds the-site-structure.
- adds the-page-path.
- ...

Name:
• cpt.hitpljb,
• cpt.hitp'browser-JavaScript,
• cpt.hitp'JavaScript,
• cpt.hitp'js,
• cpt.hitp'language.JavaScript.browser,
• cpt.hitp'ljb,
• cpt.hitp'code.browser-JavaScript,
• cpt.hitp'code.JavaScript,
• cpt.hitp'code.js,

hitpljb'File

Description:
'hitp.js' is the-JavaScript-code you need to create a-hitp-webpage.
You can-download this file, or use the online one.
So, hitp.html, hitp.css and hitp.js is the-code needed to create hitp-pages, and it is free (MIT license).

Name:
• cpt.hitp'js-file,
• cpt.hitp'file.js,

hitpljb'Table-of-Contents

Description:
When you are-reading text on a-computer-screen you are-losing your reading-position.
Hitp-webpages automatically create the-table-of-contents-tree (toc) of the-doc of the-page and show your reading-position.
HOW: you need to add the following code at the-end of the-body-element:
<script src="http://synagonism.github.io/hitp/hitp.js"></script>

The-attributes of hitp-toc are:
* It is expandable.
* There is two-way communication between the-toc and the-content.
- By clicking on the-toc, goes to that heading in the-content.
- By clicking|hovering on content, this content position is highlited in the-toc and its parents are only expanded, giving to the-reader the big picture of the-position s|he is-reading.
Thus the-toc improves the-readability of big documents.
* If the-user needs more space for the-content, the-splitbar has a-button that closes|opens the-toc with one click.
* The-splitter changes width.

My previous approach was the-creation of a-Chrome-extension, my Table-of-contents-crx which creates a-toc on any page with headings only in Chrome.

Name:
• cpt.hitp'toc,
• cpt.hitp-toc,
• cpt.hitp'toc-tree,

hitpljb'Link-preview

Description:
Another functionality that facilitates reading is the-addition of previews (pop-ups) on internal (same-origin) links with destination relatively small chunks of text.
This is especially useful for footnotes, abbreviations, definitions, index items, paragraphs etc.

HOW: you only have to add the-class 'clsPreview' on the-links you want to trigger popups when the-reader is hovering over them.
<a class="clsPreview" href="#idPreview">link-preview</a>

Name:
• cpt.hitp'link-preview,
• cpt.hitp'popup,
• cpt.hitp'preview,

hitpljb'Tree-info

Description:
Our information is full of generic-specific and whole-part trees.
Now hitp support collapsible trees, easily readable.

HOW:
You create the-tree as an-html-unordered-list (UL).
Then you add the-class 'clsTreeUl' on the first element.
That's it, the-rest is done by the javascript code of the-page.

  • Tree-root
    • Node1
      • Node1.1
        • Node1.1.1
        • Node1.1.2
      • Node1.2
        • Node1.2.1
        • Node1.2.2
    • Node2
      • Node2.1
      • Node2.2
      • Node2.3

Name:
• cpt.hitp'tree,
• cpt.hitp'tree,
• cpt.hitp'tree-info,
• cpt.hitp'info-tree,

hitp'webpage'Meta-info

Description:
A-hitp-webpage contains and extra info other than a-doc.
Most of this info is-stored in the-meta-title-content-tree.

Name:
• cpt.hitp'meta-info,
• cpt.hitp-meta-info,

hitpmeta'Page-path

Description:
By setting a-p-element[1] with id "idMetaWebpage_path", the-program sets its content as the first paragraph in the left toc-container, showing where the-page fits in the-site's-structure.
NOTE: If the-document does-not-contain this paragraph, the-program sets the-title-element as page-path.
I put this[1] element as the last paragraph of the-meta-title-content-tree.

Name:
• cpt.hitp'pagepath,
• cpt.hitp'page-path,

hitpmeta'Site-structure

Description:
Every hitp-page, except of presenting its own structure, presents and its site-structure in a pull-down menu.

HOW: You have to add ONCE in the-root-directory of the-site the-file 'hitpmenu.html' with the-site-structure in the-form of an-unordered-html-list.
Of cource, modifying this file, all the-hitp-pages will-present the-changes.

Name:
• cpt.hitp'site-structure,

hitp'webpage'Writing-style

Name:
• cpt.hitp'writing-style,

Description:
Today, our information has MANY interpretations/meanings (= polysemous).
Hitp-pages can-reduce it, by accepting the-following writing-style.

Names:
We use the-name-notation-of-this-site.
No spaces inside names.

Definition-links:
The-names of the-sentences are-connected with preview-links with their definitions.

Sentences:
Every sentence begins in a new line, which improves readability.

Time:
{1959} denotes time.

hitp'webpage'Index

Description:
Html5.id.toc.preview-pages improve the-functionality of the-indexes of documents because we have the-capability to refer|link, from the-index, to any part of the-text (because we use IDs) and preview these parts.

Name:
• cpt.hitp'index,

Concept-Index

Description:
Every text describes CONCEPTS.
The-concepts have NAMES.
Every SENTENCE in a-text is composed of names.
IF we create the-concept-index of a-text, with every concept-entry to hold its names and its definition, THEN we will-have ONE interpretation of the-meaning of a-text (= monosemous-text).
IF we set preview-linking on the-names of sentences with the-concept-index, THEN the-understanding of a-text will-become FAST.

Name:
• cpt.hitp'concept-index,
• cpt.hitp'index.concept,

Concept-Model

Description:
Every text describes concepts and relations of concepts, which form a subjective MODEL (modelConcept) of reality.
More important than the-concept-index is the-modelConcept of the-text.
In a-model-concept a-concept-entry contains, except its names and its definition and ALL its attributes|characteristics.
A crude example of a-modelConcept contains my hitp-page of the Keynes book 'The General Theory of Employment, Interest, and Money'.
A better example is my Javascript-programming-language-concept.

Name:
• cpt.hitp'concept-model,
• cpt.hitp'modelConcept,

Name-Index

Description:
Βy setting as ID on each name|term-entry the pattern "idHitpidx-term", the-reader will-have very quick access to the-entries.
un.sna.2008.html is an-example with a-name-index.

Name:
• cpt.hitp'name-index,
• cpt.hitp'index.name,

Word-Index

Name:
• cpt.hitp'index.word,
• cpt.hitp'word-index,

Description:
The majority of programs today search a-text for words and NOT names.
By pressing Ctrl+F or F3 you can-search for words.

hitp'License

Description:
This webpage's work is FREE under the-creative-commons Attribution-3.0-Unported-(CC-BY-3.0)-license.
The-computer-code is under the-MIT-license, you can-find it on GitHub.

Name:
• cpt.hitp'license,

hitp'Problem (issue)

Name:
• cpt.hitp'issue,
• cpt.hitp'problem,

overflow-x:visible, overflow-y:auto {2013.08.23}:
I needed this combination to display the-site-menu, but I found that it does not work even in the new flexbox layout.
WORKAROUND: hovering on the-menu, it displays only the left navigation container.

:after psudo-element {2013.08.23}:
Inherits properties from its dependent element, like 'underline' which we cannot change.
WORKAROUND: I hide it when I hover the main element, but have other problems.

Firefox

location.href {2013.08.16}:
FIXED
In contrast to Chrome, Firefox loses selected-text after setting value on 'location.href'.
WORKAROUND: first click to go to that location and then select-text from this location.

Back-Forward {2013.08.16}:
FIXED.
Clicking on buttons 'back', 'forward' shows the visited locations but does not go to that location.
WORKAROUND: click on the-address-bar and hit enter.

hitp.SPECIFIC

Name:
• cpt.hitp'example,
• cpt.hitp.specific,

SPECIFIC:
This site presents many examples with our proposal.
Actually I'm writing the-site with this proposal.
Reading the-code of these examples and seeing its behavior, is the best way to understand what really we are-proposing.
ebook-examples.
law-examples.
standard-examples.
empty-page to edit on GitHub-project-page.

hitp.EVOLUTION of proposal

Name:
• cpt.hitp'evolution,
• cpt.hitp.evolution,

{version.minor}:
- Collapsible-trees added. {2016.07.20}

{version.14.2016-06-09}: Title-Content-Tree:
Recursive-definition of 'title-content-tree'.
Document-unit, div.

{version.13.2016-06-07}: Preview:
Preview-links have more darkblue-color than non-preview-links. {2016.05.01}
Added a-time-delay on preview-links. {2016.04.30}
Changed id-link from ¶ to a background link image. {2016.02.23}

{version.12.2016-01-24}: Toc-Icons:
Changed the icons of the-toc-tree to images from characters, for compatibility.

{version.11.2015-10-26}: Preferences:
Users now can-choose how they prefer to view hitp-pages:
- they can-have or not the link-preview characteristic,
- they can-see on the table-of-contents the position of the content they are reading by hovering or clicking on that content.

{version.10.2014-08-05}: TYPENAMES | VALUENAMES:
With 'valuename' I mean a NAME (identifier) of a VARIABLE (= a name-value pair), that denotes the VALUE (type) with which it is associated.
Now ALL the custom names of my code are valuenames, with its FIRST-CHARACTER to denote its value|type:
- aName denotes array.
- bName denotes boolean.
- fName denotes function.
- nName denotes number.
- oName denotes object.
- rName denotes regular-expression.
- sName denotes string.
- xName denotes mixed-values.
This method is a SIMPLE method to make JavaScript a type language!!!
This way we increase the readability of the source code.
I published my new code, with the MIT license (= do whatever you want, only mention my work), on GitHub at https://github.com/synagonism/hitp.

{version.09.2014-08-02: NO jQuery:
I rewrote the-code, by removing jQuery.
Everything now is vanilla JavaScript.
Fixed: preview popup location.

{version.08.2014-01-09}: Table-of-contents:
Hovering a piece of text, you see its position on ToC.
To see the-address of the-text you click on ¶.
With the previous functionality, you had to click on text to see its position.

{version.07.2013-11-06}: Tabs:
The page-structure is set under a tab.

{version.06.2013-08-21}: Site-structure:
Now each hitp-webpage presents and its site-structure except of its own structure.

{version.05.2013-07-15}: ToC Algorithm:
I wrote a new smaller specific algorithm that creates the ToC of a hitp-page.
The previous was the one of html5-outliner-chrome-extension.
Also I enclosed the-code in one literal object, the 'HITP'.
I allow gaps in headings like: h1, h2, h4 because existing docs use this pattern.

{version.04.2013-06-27}: Name:
I change the-name of the proposal from html5.id.toc to html5.id.toc.preview (= html5IdTocPreview)
in-order to include all its main attributes.
Abbreviation: ebkHitp, hitp.

{version.03.2013-04-14}: Link Preview:
HTML5.ID.TOC.PREVIEW: Another feature that facilitates reading-productivity.

{version.02.2013-04-01}: Table of Contents:
HTML5.ID.ToC: Adding a few lines of javascript code the static-pages are becoming dynamic ('applications!') but this facilitates reading.
This way the 'electronic-text' begins to have more advantantages than 'printed-text'.
Other forms of 'electronic-text' which merely digitize printed-text are inferior to 'printed-text'.

{version.01.2011-02-17}: first publication:
HTML5.ID: the goal of my first try was to show a simple method of a-text-format we can-read in a ubiquitous web-browser that anyone can-REFER to any part of it.
The main types of texts I had in my mind were law-texts.

hitp'Versioning

Description:
We can-have a simple versioning paradigm on hitp-pages by setting the-date on its file-name plus one or more numbers indicating how many times changes have-occured, ie 'index.16.2016-06-09.html' (= version 16 of index.html on {2016-06-09}).
Having and a-file with only the-file-name but with the LAST-MINOR-DYNAMIC version we can always have access to the last version with minor changes we do-not-think important to hold records on them.
From internal links we can-have access to previous dated versions.
As example look this file you are-reading.
Evolution is a continuous entity.
Every author SUBJECTIVELY desides when to call a-page 'version'.

Name:
• cpt.hitp'versioning,

hitp'Todo

Description:
* Make it mobile friendly. {2016.08.08}

Name:
• cpt.hitp'todo,

Meta Info

VERSIONS:
• version.16-14.2016-08-09.last.minor: index.html (DYNAMIC-VERSION)
• version.16.2016-06-09.last.minorNo (15-18): index.16.2016-06-09.html (title-content-tree)
• version.15.201-01-25: index.15.201-01-25.html (content)
• version.14.previous: index.2013.08.23.14.html (site-structure)
• version.13.previous: index.2013.08.20.13.html (name webpage)
• version.12.previous: index.2013.06.29.12.html (new-dir-hitp)
• version.11.previous: /hit/index.2013.06.26.html (new-name)
• version.10.previous: /hit/index.2013.06.18.html (no-doc.ready)
• version.9.previous: /hit/index.2013.06.01.html (synagonism.net)
• version.8.previous: /gym-eleous.ioa.sch.gr/textid/index.2013.05.29.html (concept-index)
• version.7.previous: /gym-eleous.ioa.sch.gr/textid/index.2013.05.15.html (math)
• version.6.previous: /gym-eleous.ioa.sch.gr/textid/index.2013.04.14.html (link-preview)
• version.5.previous: /gym-eleous.ioa.sch.gr/textid/index.2013.04.01.html (toc)
• version.4.previous: /gym-eleous.ioa.sch.gr/textid/index.2013.03.31.html (counter)
• version.3.previous: /gym-eleous.ioa.sch.gr/textid/index.2013.03.28.html (¶ right)
• version.2.previous: /gym-eleous.ioa.sch.gr/textid/index.2013.01.16.html
• version.1.published: /gym-eleous.ioa.sch.gr/textid/index.2011.02.17.html
• Created: 2011.02.15

This page was visited times since 2013.05.30.

Page-path: hitp-wpglag ∈ synagonism.net

Support

Comments

comments powered by Disqus