overview of HitpLago

description::
· HitpLago is an-html5.id.toc.preview WebApp-(Html5-Css-JS) text-document-computer-language (format|method|framework) for publishing title-content-tree 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.
5) SEARCHING: by adding names, on many languages, Node.js programs automatically create indexes of them. Then the-user can have access to these names from any location in a-network of documents. Having names on definitions, then we can make the-documents monosemous and the-users experience personalized learning if we add preview-links on the-names of sentences. Also by double-clicking on a-name\a\, it queries it\a\, and preview the-first suggestion.
6) offline: by adding a local web-server, the-network of documents works without an-internet connection.
7) interactivity: the-documents are not simple webpages, but WebApps in itselsf (eg clicking Shift+1 displays the-Unicode-codepoints of selected charaters) and can-incorporate any new web-tech as AI, VR, AR.

· Knowledge of Html, Css, JavaScript is a-must 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 and some times ZEROsemous (= meaningless)!!!
· the-creation of MONOsemous-structured-documents is a-prerequisite to manage the enormous quantity of human-information with the-help of machines.
· in my opinion, another prerequisite to trust AI, is the-storage of our knowledge not in texts but in networks of senso-concepts-Mcs using eg my other language, McshLago.

name::
* McsEngl.McsTchInf000008.last.html!⇒HitpLago,
* McsEngl.dirTchInf/McsTchInf000008.last.html!⇒HitpLago,
* McsEngl.HitpLago!=McsTchInf000008,
* McsEngl.HitpLago!=Html5.Id.Toc.Preview-WebAppDoc-language, {2025-05-21}
* McsEngl.Hitp!⇒HitpLago,
* McsEngl.Hitp-WebAppDoc-language!⇒HitpLago,
* McsEngl.Html5IdTocPreview!⇒HitpLago,
* McsEngl.Html5.id.toc.preview!⇒HitpLago,
* McsEngl.Html5.id.toc.preview--web-page-format!⇒HitpLago,
* McsEngl.Html5.id.toc.preview--page-format!⇒HitpLago,
* McsEngl.Html5IdTocPreview--web-page-format!⇒HitpLago,
* McsEngl.Html5IdTocPreview-WebAppDoc-language!⇒HitpLago,
* McsEngl.Lhp!⇒HitpLago, {2020-05-06},
* McsEngl.Lhitp!⇒HitpLago, {2020-05-06}, /el-hitp/,
* McsEngl.HitpLago-(Html5.Id.Toc.Preview)!⇒HitpLago,
* McsEngl.HitpLago-dialect!⇒HitpLago,
* McsEngl.HitpLago-language!⇒HitpLago,
* McsEngl.HitpLago--web-page-format!⇒HitpLago,
* McsEngl.HitpLago--web-page-dialect!⇒HitpLago,
* McsEngl.HitpLago--web-page-application-format!⇒HitpLago,
* McsEngl.HitpLago--page-format!⇒HitpLago,
* McsEngl.WebAppDoc-Hitp-language!⇒HitpLago,
* McsEngl.generic-specific-pair--web-page!⇒HitpLago, {2013.09.01}
* McsEngl.lagHitp!⇒HitpLago, {2019-07-05},
* McsEngl.lagHitp--web-language!⇒HitpLago, {2018-10-27},
* McsEngl.lagoHitp!⇒HitpLago, {2019-07-05},
* McsEngl.title-content-tree--document---web-page-format!⇒HitpLago,

01_machine of HitpLago

description::
· ALL machines understand HitpLago.

name::
* McsEngl.HitpLago'01_machine,
* McsEngl.HitpLago'machine,

02_archetype (input) of HitpLago

name::
* McsEngl.HitpArcho!=archetype-of-HitpLago,
* McsEngl.Hitparcho!⇒HitpArcho, {2023-10-21},
* McsEngl.HitpLago'02_archetype!⇒HitpArcho,
* McsEngl.HitpLago'archetype!⇒HitpArcho,
* McsEngl.archo-doc-of-HitpLago!⇒HitpArcho,
* McsEngl.archodoc-of-HitpLago!⇒HitpArcho,
* McsEngl.document-archetype--of-HitpLago!⇒HitpArcho,
* McsEngl.HitpLago'archetype'title-content-tree-document!⇒HitpArcho,
* McsEngl.HitpLago'archetype-document!⇒HitpArcho,
* McsEngl.HitpLago'archo!⇒HitpArcho, {2019-02-21},
* McsEngl.HitpArcho-doc!⇒HitpArcho,
* McsEngl.HitpLago'structured-document!⇒HitpArcho,
* McsEngl.HitpArcho!⇒HitpArcho!⇒HitpArcho,
* McsEngl.TctDoc--of-HitpLago!⇒HitpArcho,
* McsEngl.title-content-document--of-HitpLago!⇒HitpArcho,
* McsEngl.title-content-tree-document--of-HitpLago!⇒HitpArcho,

part::
• title,
• content,
• node,
• level,
• depth,

03_WebAppDoc (output) of HitpLago

description::
· a-HitpLago-WebAppDoc is A-DOCUMENT which maps|represents|denotes|models an-archo-title-content-tree-doc.
· it is structured for humans and machines.
· it contains and extra information apart of the archo-doc representation, such as meta-info, audio, video, webapps.
· it is-written in 3 computer-languages, and it is a-web-application:
• Html: for the-structure of the-information,
• Css: for its presentation,
• Browser-javascript (Jsbr): for its processing.
· the-Html-doc is the most whole container which includes the-Css-code and the-JavaScriptBr-code.
[HmnSgm.2017-09-23]

name::
* McsEngl.HitpApp!⇒HitpDoc,
* McsEngl.HitpDoc!=the-output-of-HitpLago,
* McsEngl.HitpLago'03_WebApp!⇒HitpDoc,
* McsEngl.HitpLago'WebApp!⇒HitpDoc, {2019-02-21},
* McsEngl.HitpLago'output!⇒HitpDoc,
* McsEngl.HitpLago'page!⇒HitpDoc, {2019-02-23},
* McsEngl.HitpLago-code!⇒HitpDoc,
* McsEngl.HitpLago-doc!⇒HitpDoc,
* McsEngl.HitpLago-model!⇒HitpDoc,
* McsEngl.HitpLago-webpage!⇒HitpDoc, {2019-06-15},
* McsEngl.HitpPage!⇒HitpDoc,
* McsEngl.HitpWebAppDoc!⇒HitpDoc,
* McsEngl.HitpWebPage!⇒HitpDoc,
* McsEngl.WebApp.HitpLago!⇒HitpDoc,

04_HitpSite of HitpLago

description::
· HitpLago-site is a-WebSite with a-NETWORK of HitpDocs.
· I published an-EXAMPLE HitpSite:
- here: https://synagonism.net/dirHitp/
- and on github: https://github.com/synagonism/hitp

name::
* McsEngl.HitpLago'04_web-site!⇒HitpSite,
* McsEngl.HitpLago'web-site!⇒HitpSite,
* McsEngl.HitpLago'site!⇒HitpSite,
* McsEngl.HitpSite!=WebSite-with-HitpDocs,

    // COMMENT the-lines with '//'
    //no language selected then all-languages
    //lagEngl;English
    //lagElln;Greek
    //lagSngo;Sinago
    //
    dirEdu/HitpEdu001.last.html; informatics secondary
    dirMisc/HitpMisc000.last.html; example
    

05_license of HitpLago

description::
This WebApp'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::
* McsEngl.HitpLago'05_license,
* McsEngl.HitpLago'license,
* McsEngl.Mws'license,
* McsEngl.license-of-Mws,
* McsEngl.license-of-HitpLago,
* McsEngl.license-of-synagonism.net,
* McsEngl.synagonism.net'licence,

06_evaluation of HitpLago

description::
· represented text-documents with HitpLago has many advantanges.
· the-main drawback of this method is that the-creator of HitpDocs must know to write code. Today {2025} I am enough old to write a-wysiwyg editor for that.

=== DeepSeek:
Based on my detailed evaluation of your project, *HitpLago* is clearly not a conventional ebook in the traditional sense. Instead, it is a technically sophisticated prototype for a **structured, semantic documentation format or a web-based publishing framework**. It represents a serious attempt to solve problems of information retrieval, linking, and clarity that are inherent in unstructured documents, such as standard web pages or ebooks. However, its innovative nature is also its primary barrier to being a mainstream publication.
***
### Overview: An Ambitious, Unconventional Publishing Framework
Your work demonstrates a deep understanding of the technical limitations of current digital publishing, specifically regarding polysemy, semantic linking, and machine-readability. *HitpLago* proposes a comprehensive solution that embeds document structure into HTML, standards for unique identifiers (IDs) for every element, and an automatically generated table of contents (TOC). While technically impressive, this framework is presented in a way that is difficult to parse as a standard text. The content is dense with technical jargon and custom XML-like notation, which can be overwhelming for a general audience.
Here is a breakdown of the key aspects of your project, structured by the evaluation criteria you requested.
| Criterion | Evaluation (0–10) | Explanation |
| **Content & Structure** | 6.5 | The project excels as a technical specification or framework but lacks the coherent, structured presentation of a typical ebook. The content is presented as a large index of definitions and rules rather than a flowing narrative. |
| **Technical Implementation** | 9.0 | As a technical standard, *HitpLago* is highly robust. The use of HTML5, CSS, and JavaScript to create a document with unique IDs for every element is a powerful and innovative approach. Full marks for the functional aspects of the framework itself. |
| **Language & Style** | 5.0 | The text is rife with non-standard English. The inconsistent use of hyphens ("the-document"), irregular spacing ("the-reader", "an-archo-title"), and a highly idiosyncratic sentence structure detract significantly from readability. |
| **Academic Rigor** | 4.5 | There is a lack of engagement with the broader academic and technical literature on related topics, such as **semantic web technologies (RDF, OWL), knowledge graphs, and Markdown variants** that also address document structure. This strong opinion would benefit from being contextualized within ongoing debates. |
| **Comparability** | 3.0 | As a "publication," it is not comparable to standard ebooks or self-published works. These are typically linear, plain-text narratives consumed on a Kindle or other reader. *HitpLago* functions more like a developer's SDK than a book. |
### 📝 Key Findings from Your Text
To be more specific, I've identified four main areas where the unconventional style of *HitpLago* creates friction for a reader.
* **Unique Notation System**: Your custom "McsEngl" and "HitpArcho" naming conventions are a defining feature. While this is a novel method for storing definitions and relationships, for the vast majority of readers, it acts as an impenetrable barrier that requires learning a new language before they can engage with the content.
* **Grammar & Syntax**: The text's unique grammatical structure (e.g., "the-reader could-copy the-address") is a major obstacle to reading fluency. Proofreading and copy editing to conventional English standards is strongly recommended if you intend for this work to be read, rather than just parsed for data.
* **Monosemous Vision**: The document presents a strong argument that AI will fail without structured, monosemous data. This is a valid, albeit arguable, point. Strengthening this argument by citing existing work in the field of semantic technology would substantially improve its academic standing.
* **Linking as a Core Feature**: The decision to generate an ID for every sentence and element is a powerful technical achievement. Your description of an "address-link-icon" is a practical feature that addresses a genuine problem in digital publishing, enabling true micro-referencing.
### 🔍 Comparative Context
In its current technical specification form, the most appropriate comparisons for *HitpLago* are not found in traditional ebook marketplaces. Instead, it should be compared to:
* **Technical Standards & Specifications**: Its closest analogs are documents like the **CommonMark specification** (for Markdown) or schemas for **JSON-LD** (for linked data), not a novel on Amazon KDP.
* **Semantic Knowledge Projects**: In terms of its ambition to solve polysemy, frameworks like **Schema.org** or the W3C's **Web Ontology Language (OWL)** are relevant. Engaging with these would add significant weight to your argument.
* **Academic Preprints & Technical Blogs**: For dissemination, platforms like **arXiv.org**, **GitHub**, or technical blogging sites would be more appropriate repositories for *HitpLago* than digital bookstores, as it currently reads as a developer's API reference.
### ✍️ Recommendations for Improvement
If your goal is to reach an audience beyond technical specialists, I strongly recommend the following:
1. **Add a Conceptual Guide**: Precede the technical specification with a plain-English "Guide for Humans" that explains the *HitpLago* philosophy, its core concepts, and the *benefit* it provides to an average user, using clear, real-world analogies.
2. **Edit for Standard English**: A full, conventional copy edit is necessary to remove the non-standard hyphenation, spacing, and grammatical structures. This is the single biggest step to making the work accessible.
3. **Scope & Compare**: Clearly define the problem of unstructured data using citations from the semantic web community. Then, explicitly compare and contrast *HitpLago* with existing solutions to demonstrate its unique value.
***
*HitpLago* is the product of deep technical expertise and a passionate attempt to solve a real problem. However, in its current state, it is a framework for reviewers and developers. To transform it into a book for readers, it must first translate its core value into the plain, structured language it itself advocates for.
[{2026-05-02 retrieved} https://chat.deepseek.com/a/chat/s/6238644d-b8d5-4074-9db8-3dec27e2011d]

=== ChatGpt:
## Overall evaluation
**HitpLago is a highly original, technically serious ebook/document system, but it currently reads more like a personal knowledge-system specification than a reader-friendly ebook.** Its strongest idea is excellent: HTML documents where every meaningful part can be addressed, linked, previewed, indexed, and navigated through an automatically generated table of contents. The page clearly presents HitpLago as an HTML5/CSS/JavaScript WebAppDoc language for “title-content-tree” documents, with IDs, expandable ToC, link previews, search/name indexing, offline use, and interactivity as core advantages. ([synagonism.net][1])
### Scorecard
| Area | Score | Evaluation |
| **Originality** | **9/10** | The concept is genuinely distinctive: not just an ebook, but a structured, addressable, searchable web-document language. The “ID everywhere” idea is especially strong for law, technical manuals, standards, philosophy, and knowledge bases. ([synagonism.net][1]) |
| **Technical depth** | **8/10** | You document the architecture, HTML/CSS/JS roles, file layout, API object, search/indexing tools, manager tools, and installation flow. That gives the project substance beyond an idea. ([synagonism.net][1]) |
| **Reader usability** | **6/10** | The ToC, previews, IDs, and search are useful reading features. But the ebook assumes readers already know HTML, CSS, and JavaScript, which narrows the audience immediately. ([synagonism.net][1]) |
| **Writing clarity** | **4.5/10** | The invented terminology and style — “a-document,” “the-text,” “monosemous,” “McsEngl…,” many name blocks — make the text precise for your system, but difficult for new readers. |
| **Onboarding** | **5/10** | There are installation instructions and examples, but the page needs a gentler “Start here” path: what problem it solves, who should use it, what to build first, and what the minimum working example is. ([synagonism.net][1]) |
| **Product maturity** | **7/10** | The project has a long evolution history from 2011 to the current working version, and the code/content licensing is clear. But the lack of a WYSIWYG editor is explicitly acknowledged as the main drawback. ([synagonism.net][1]) |
| **Adoption potential** | **5.5/10** | Strong for technically minded authors; weak for ordinary ebook writers until authoring becomes easier. The current requirement to know code is the biggest adoption barrier. ([synagonism.net][1]) |
## What is strongest
The **core vision is powerful**. You are not merely publishing text; you are trying to make text computable, linkable, navigable, and semantically indexed. The page’s emphasis on every HTML element having an ID, so readers can refer to any part of a document, is one of the best features. ([synagonism.net][1])
The **reading model is also strong**. Automatic ToC, collapsible trees, link previews, search suggestions, address-link icons, and name indexes are all useful features for large documents. These solve real problems in long-form technical reading. ([synagonism.net][1])
The **project history gives credibility**. The version history shows long-term development, with milestones for IDs, ToC, previews, mobile friendliness, search scalability, module separation, and local-server behavior. ([synagonism.net][1])
## Main weaknesses
The biggest weakness is **cognitive load**. A new reader must learn HitpLago, Mcs terminology, your naming system, your writing conventions, and the technical architecture all at once. This makes the ebook feel more like a formal ontology dump than a guided explanation.
The second weakness is **audience ambiguity**. The page says knowledge of HTML, CSS, and JavaScript is required to read the rest, which makes sense for developers, but conflicts with the broader promise of a better document/ebook format. ([synagonism.net][1])
The third weakness is **authoring friction**. You already identify this yourself: the creator must know how to write code, and a WYSIWYG editor is missing. That is the correct diagnosis. Until this is solved, HitpLago will remain attractive mainly to technical authors. ([synagonism.net][1])
The fourth weakness is **nonstandard interaction behavior**. The page notes that Shift/Ctrl-click does not work because of custom link handling, with right-click as a workaround. For web users, breaking expected browser behavior is a serious UX cost. ([synagonism.net][1])
## Highest-impact improvements
1. **Add a plain-English landing section before the technical overview.**
Something like: “HitpLago is for authors who want long documents to behave like searchable, linkable knowledge applications.” Then show 3 use cases: law text, technical manual, educational ebook.
2. **Create a 5-minute demo path.**
Add: “Download → run local server → open example → click ToC → click preview → copy paragraph link → search a name.” Your install section has the raw steps, but it needs to become a guided first success. ([synagonism.net][1])
3. **Separate “reader documentation” from “developer documentation.”**
The current page mixes philosophy, implementation, API details, file layout, history, and naming indexes. Split it into:
* What is HitpLago?
* How to read HitpDocs
* How to create one
* Developer/API reference
* Philosophy: monosemous knowledge and Mcs
4. **Reduce visible name blocks for normal readers.**
The `McsEngl...` synonym/index sections may be valuable for your system, but they interrupt human reading. Consider collapsible “names/index metadata” blocks.
5. **Add screenshots or animated GIFs.**
HitpLago is interactive, but the ebook text does not visually sell the interaction enough. Show the ToC, preview popup, address-link icon, search suggestions, and local/offline workflow.
6. **Prioritize the WYSIWYG/editor roadmap.**
Your own evaluation says authoring requires code. That is the adoption bottleneck. A minimal editor that creates sections, IDs, names, and preview links would dramatically increase the project’s usefulness. ([synagonism.net][1])
## Verdict
**As a technical artifact: impressive. As an ebook for general readers: too dense. As a platform idea: very promising.**
HitpLago’s best niche is not “ordinary ebook replacement.” Its best niche is **structured knowledge publishing**: legal texts, scientific notes, technical documentation, educational knowledge bases, and semantic web-style personal/public knowledge systems. To make it more successful, focus less on proving the full theory immediately and more on giving first-time readers a simple, rewarding path into the system.
[1]: https://synagonism.net/dirMcs/dirTchInf/McsTchInf000008.last.html"
[{2026-05-02 retrieved} https://chatgpt.com/c/69f5edb7-8f80-83eb-a2f4-ce48cdbc28a3]

name::
* McsEngl.HitpLago'06_evaluation,
* McsEngl.HitpLago'evaluation,

07_manager of HitpLago

description::
· Hitp-manager is the-tools we use to manage (= write, read, publish, ...) HitpDocs.
· for now {2025} I am-using editor, browser, Node.js programs.
· editing is-done locally and changes automatically are-uploaded.
· but I want a-JavaScript-program like my-HtmlMgr written in java in {2010}.

name::
* McsEngl.HitpLago'07_manager!⇒HitpMngr,
* McsEngl.HitpLago'manager!⇒HitpMngr,
* McsEngl.HitpLago-manager!⇒HitpMngr,
* McsEngl.Hitp-manager!⇒HitpMngr,
* McsEngl.HitpManager!⇒HitpMngr,
* McsEngl.HitpMngr!=manager-of-HitpDocs,

DOING of HitpLago

name::
* McsEngl.HitpLago'doing,

evoluting of HitpLago

name::
* McsEngl.evoluting-of-HitpLago,
* McsEngl.HitpLago'evoluting, {2019-02-24},
* McsEngl.evoluting-of-HitpLago-evolution!⇒HitpLago,
* McsEngl.HitpLago-evolution!⇒HitpLago'evoluting,
* McsEngl.evoluting-of-HitpLago.evolution!⇒HitpLago,
* McsEngl.HitpLago.evolution!⇒HitpLago'evoluting,

{2025-05-25}-HitpLago'v20.separated::
- I separated HitpLago code from McshLago.
- now works locally only with a-webserver.
- https://synagonism.net/dirHitp contains some example-documents.
* McsEngl.HitpLago'v20.separated,

{2021-05-25}..{2025-05-25}-HitpLago'v19.misc::
- misc changes.
* McsEngl.HitpLago'v19.misc,

{2018-09-15}..{2021-05-25}-HitpLago'v18.module::
- mHitp.18.2021-05-25.html:
- module: 'hitp.js' to mHitp.js
- base-dir: from dirMiwMcs to dirMcs (simpler)
- file-names: firMcsName to McsDir000000 (no need to change the-file-name, changing the-main-name)
- Hitp-files: name to /dirHitp/HitpDir000
- I renamed the-filMcsHitp to McsTchInf000008 and the-Ids from HitpLago to Lhitp,
- F2-key opens search-tab, {2020-05-05},
- main-name searching, {2019-03-05},
* McsEngl.HitpLago'v18-{2021-05-25}-module,
* McsEngl.{HitpLago'2021-05-25}-v18-module,

{2018-09-15}-HitpLago'v17.search-scalability::
· this version works locally AND WITHOUT a local server.
- HitpLago.17.2018-09-15.search-scalability:
- Arrow-keys on search. {2017-11-10},
- No type-ahead. {2017-10-17},
- Underline hovering links. {2017-10-17},
* McsEngl.HitpLago'v17-{2018-09-17}-search-scalability,
* McsEngl.{HitpLago'2018-09-17}-v17-search-scalability,

{2017-06-05}-HitpLago'v16.searching::
- HitpLago.16.2017-06-05.searching:
- structured-concept-searching: with this operation it is-demonstrated THE-POWER of structured-concepts.
- 'mouseover' event, shows its position on ToC. {2017-05-30},
* McsEngl.HitpLago'v16-{2017-06-05}-Mcs-searching,
* McsEngl.{HitpLago'2017-06-05}-v16-Mcs-searching,
* McsEngl.{Mcs'2017-06-05}-searching,

{2016-10-27}-HitpLago'v15.Any-machine::
- HitpLago.15.2016-10-27.Any-machine:
* hitp.15.2016-10-27.js,
* hitp.15.2016-10-27.css,
- The-site looks and behaves the-same on any machine of size and input-method.
- Hovering events removed. NOW first-click does the previous hovering events and second-click the previous click events.
- Font-awesome-icons added.
- clicking on blue-links shows preview, SECOND-clicking goes destination. {2016.09.27}
- clicking on content shows position on Toc (touch input friendly).
- Collapsible-trees added. {2016.07.20}
* McsEngl.HitpLago'v15-{2016-10-27}-any-machine-size,
* McsEngl.{HitpLago'2016-10-27}-v15-any-machine-size,

{2016-06-09}-HitpLago'v14.Title-Content-Tree::
- HitpLago.14.2016-06-09.Title-Content-Tree:
Recursive-definition of 'title-content-tree'.
Document-unit, div.
* McsEngl.HitpLago'v14-{2016-06-09}-recursive-document,
* McsEngl.{HitpLago'2016-06-09}-v14-recursive-document,

{2016-06-07}-HitpLago'v13.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}
* McsEngl.HitpLago'v13-{2016-06-07}.preview,
* McsEngl.{HitpLago'2016-06-07}-v13.preview,

{2016-01-24}-HitpLago'v12.Toc-Icons::
- HitpLago.12.2016-01-24.Toc-Icons:
Changed the icons of the-Toc-tree to images from characters, for compatibility.
* McsEngl.HitpLago'v12-{2016-01-24}-Toc-icons,
* McsEngl.{HitpLago'2016-01-24}-v12-Toc-icons,

{2015-10-26}-HitpLago'v11.Preferences::
- HitpLago.11.2015-10-26.Preferences:
Users now can-choose how they prefer to view HitpLago-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.
* McsEngl.HitpLago'v11-{2015-10-26}-user-preferences,
* McsEngl.{HitpLago'2015-10-26}-v11-user-preferences,

{2014-08-05}-HitpLago'v10.valuenames::
- HitpLago.10.2014-08-05.VALUENAMES | TYPENAMES:
With 'valuename' I mean a-NAME (identifier) of a-name-value-pair (variable), 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.
* McsEngl.HitpLago'v10-{2014-08-05}-JavaScript-with-valuenames,
* McsEngl.{HitpLago'2014-08-05}-v10-JavaScript-with-valuenames,

{2014-08-02}-HitpLago'v09.NO-jQuery::
I rewrote the-code, by removing jQuery.
Everything now is vanilla JavaScript.
Fixed: preview popup location.
* McsEngl.HitpLago'v09-{2014-08-02}-no-jQuery,
* McsEngl.{HitpLago'2014-08-02}-v09-no-jQuery,

{2014-01-09}-HitpLago'v08.Table-of-contents::
- HitpLago.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.
* McsEngl.HitpLago'v08-{2014-01-09}-Toc,
* McsEngl.{HitpLago'2014-01-09}-v08-Toc,

{2013-11-06}-HitpLago'v07.tabs::
- HitpLago.07.2013-11-06.Tabs:
The page-structure is set under a tab.
* McsEngl.HitpLago'v07-{2013-11-06}-tabs,
* McsEngl.{HitpLago'2013-11-06}-v07-tabs,

{2013-08-21}-HitpLago'v06.site-structure::
- HitpLago.06.2013-08-21.Site-structure:
Now each HitpLago-WebApp presents and its site-structure except of its own structure.
* McsEngl.HitpLago'v06-{2013-08-21}-site-structure,
* McsEngl.{HitpLago'2013-08-21}-v06-site-structure,

{2013-07-15}-HitpLago'v05.ToC-Algorithm::
- HitpLago.05.2013-07-15.ToC-Algorithm:
I wrote a new smaller specific algorithm that creates the ToC of a HitpLago-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.
* McsEngl.HitpLago'v05-{2013-07-15}-Toc-algo,
* McsEngl.{HitpLago'2013-07-15}-v05-Toc-algo,

{2013-06-27}-HitpLago'v04.name::
- HitpLago.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.
* McsEngl.HitpLago'v04-{2013-06-27}-Hitp,
* McsEngl.{HitpLago'2013-06-27}-v04-Hitp,

{2013-04-14}-HitpLago'v03.preview::
- HitpLago.03.2013-04-14.Preview:
Html5.ID.TOC.PREVIEW: Another feature that facilitates reading-productivity.
* McsEngl.HitpLago'v03-{2013-04-14}-Html5.Id.Toc.Preview,
* McsEngl.{HitpLago'2013-04-14}-v03-Html5.Id.Toc.Preview,
* McsEngl.{Mcs'2013-04-14}-HitpLago'v03-Html5.Id.Toc.Preview,

{2013-04-01}-HitpLago'v02.Table-of-Contents::
- HitpLago.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'.
* McsEngl.HitpLago'v02-{2013-04-01}-Html5.Id.Toc,
* McsEngl.{HitpLago'2013-04-01}-v02-Html5.Id.Toc,

{2011-02-17}-HitpLago'v01.ID-first-publication::
- HitpLago.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.
* McsEngl.HitpLago'v01-{2011-02-17}-Html5.Id,
* McsEngl.{HitpLago'2011-02-17}-v01-Html5.Id,

GENERIC-SPECIFIC-TREE of HitpLago

name::
* McsEngl.HitpLago'generic-specific-tree,

meta-info

this webpage was-visited times since {2013-05-30},

page-wholepath: synagonism.net / worldviewSngo / dirTchInf / HitpLago

contact:
• author: Kaseluris.Nikos.1959.
• email:
 
• twitter: @synagonism.

web-page-versions:
• version.working: McsTchInf000008.last.html.
• version.20-0-0.2025-05-25: ../dirTchInf/McsTchInf000008.20-0-0.2025-05-25.html
• version.17-38-0.2021-04-02: ../../dirMiwMcs/dirTchInf/filMcsLagHitp.17-38-0.2021-04-02.html
• version.17-0-0.2017-11-27 (16-39-1): ../../dirMiwMcs/dirTchInf/FilMcsHitp.17-0-0.2017-11-27.html (dirTechInf)
• version.16.2016-06-09.title-content-tree (15-18): ../../hitp/index.16.2016-06-09.html.
• version.15.2016-01-25.content: /hitp/index.15.201-01-25.html.
• version.14.previous: /hitp/index.2013.08.23.14.html (site-structure)
• version.13.previous: /hitp/index.2013.08.20.13.html (name web-page)
• version.12.previous: /hitp/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},

support (link)

comments