|Page 398 of 800||Search internet|
'Loading' a Logiweb page is a process which takes a Logiweb 'reference' as input and produces a Logiweb 'cache' as output.
After loading a page it is possible to 'render' it. At present, loading and rendering is done by the lgc compiler.
Rendering results in a number of interlinked html-, pdf-, and other files. When viewed in an ordinary web browser, the interlinked html-, pdf-, and other files allow to navigate within and among Logiweb pages. A genuine Logiweb browser would allow the same kind of navigation as is possible with an ordinary web browser plus the interlinked html-, pdf-, and other files. Hence, an ordinary web browser plus the interlinked files effectively implement a Logiweb browser. We refer to that browser as the 'Logiweb cross browser' because it is a Logiweb browser that is hosted by an ordinary web browser.
Rendering of a Logiweb page typically results in a number of html- and pdf-files. But the rendering engine of Logiweb is not restricted to any particular format. Rendering of a Logiweb page may also result in .c files, .h files, makefiles, and any other kind of file that can be expressed as a sequence of bytes. It is the author of a Logiweb page who decides which and how many files rendering results in.
In particular, rendering of a Logiweb page may result in 'Logiweb scripts' which are executable files. Such scripts are executed using the Logiweb Abstract Machine (lgwam) as script interpreter
Loading a page consists of fetching, unpacking, codifying, and verifying the page which is described in the following.
|Page 398 of 800||Search logiweb.eu|