idk_parser_beta_win64.exe
..idk
extension to test the markup.CTRL+C
.NOTE: IDK documents with status
set to draft
inside a context, will not be converted to HTML.
The IDK parser tool is able to check for errors in your .idk
files, convert them as W3C compliant HTML files, check the HTTP URI and file path present in them.
The HTML produce does not need to have javascript enable when viewed, simple interactions on click are present (id est in context elements).
When you download the idk_parser_beta_win64.zip, you will have inside the program with the .exe
extension and a folder name local
.
This folder contains the shared resources for HTML conversion (head, menu and footer) you can modify in order to make it at your personal taste. The html
folder location is used to save all HTML files. You must not delete the assets
folder inside it but can delete anything else.
This is the complete build used for this website, that way you are able to see how IDK markup works on a deeper level.
targ_p
: the folder path where all IDK files are located (with extension .idk
).root_p
: the path where all related file are located (images, css, html ...).check_urls
(optional): will check every http(s) urls of all idk documents.Set them as broken if unresolvable.js
(optional): build related data for js interaction (highlited, selected ids and more).no_file_path_check
(optional): disable the check on file path inside mentioned inside idk document making it unable to have broken links.None dependency is present in the software, but it makes extensive use of the Digital Grove project.
idk_parser_beta.exe targ_p="./local/idk_files/" root_p="./local" deploy
idk_parser_beta.exe targ_p="./local/idk_files/" root_p="./local" check_urls
idk_parser_beta.exe targ_p="./local/idk_files/" root_p="./local" check_file_paths
In several ways we emphasize ease of use.
We permit to select every text chunks:
When the intend of the writer is obvious, we want the markup correct it without failing or uninteded behaviour:
.
.