documentation more consistent
This commit is contained in:
@@ -23,12 +23,12 @@
|
||||
@(define version (webview-version-string))
|
||||
|
||||
|
||||
@title{Racket Webview - v@version - Introduction}
|
||||
@title[#:tag "racket-webview-intro"]{Racket Webview - v@version - Introduction}
|
||||
@author[@author+email["Hans Dijkema" "hans@dijkewijk.nl"]]
|
||||
|
||||
@defmodule{racket-webview}
|
||||
|
||||
@section{Overview}
|
||||
@section[#:tag "racket-webview-intro-overview"]{Overview}
|
||||
|
||||
This documentation is provided for version @bold{@version} of racket webview.
|
||||
|
||||
@@ -41,7 +41,7 @@ On top of that, @racketmodname[racket-webview/racket-webview] provides a
|
||||
functional API. The class-oriented API described in this manual is built from
|
||||
smaller modules on top of that layer.
|
||||
|
||||
@section{Core Concepts}
|
||||
@section[#:tag "racket-webview-intro-core-concepts"]{Core Concepts}
|
||||
|
||||
The library is structured around two main concepts:
|
||||
|
||||
@@ -52,7 +52,7 @@ The library is structured around two main concepts:
|
||||
A context manages local file serving, certificates, and settings. A window loads
|
||||
content, handles events, and provides access to DOM elements.
|
||||
|
||||
@section{Modules}
|
||||
@section[#:tag "racket-webview-intro-modules"]{Modules}
|
||||
|
||||
The public API is divided into the following modules:
|
||||
|
||||
@@ -66,7 +66,7 @@ The public API is divided into the following modules:
|
||||
@item{@racketmodname[racket-webview/rgba] — RGBA color values}
|
||||
@item{@racketmodname[racket-mimetypes] — MIME type lookup}]
|
||||
|
||||
@section{Typical Usage}
|
||||
@section[#:tag "racket-webview-intro-typical-usage"]{Typical Usage}
|
||||
|
||||
A typical application creates a @racket[wv-context%] object and then creates one
|
||||
or more @racket[wv-window%] objects within that context. DOM elements are
|
||||
|
||||
Reference in New Issue
Block a user