aboutsummaryrefslogtreecommitdiff
path: root/doc/ref/javascript.texi
blob: bbe1cb2548c7353aa21949c288549381939467fa (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
@node Javascript
@chapter Javascript

@c web components
@defindex wc

@c done
@node General Stuff
@section General stuff
The frontend code has its entry-point in @code{script.ts}

All elements are initialized in elements.ts

@include javascript/clock.texi
@include javascript/lib.texi
@include javascript/eventCreator.texi
@include javascript/types.texi
@include javascript/vevent.texi
@include javascript/globals.texi
@include javascript/server_connect.texi
@include javascript/formatters.texi
@include javascript/user-additions.texi

@node General Components
@section General Components
@include javascript/components/date_time_input.texi
@include javascript/components/input_list.texi

@node VEvent Components
@section VEvent Components
@include javascript/components/vevent.texi
@include javascript/components/changelog.texi
@include javascript/components/edit_rrule.texi
@include javascript/components/popup_element.texi
@include javascript/components/tab_group_element.texi
@include javascript/components/vevent_block.texi
@include javascript/components/vevent_description.texi
@include javascript/components/vevent_dl.texi
@include javascript/components/vevent_edit.texi

@section About our buildsystem
Currently (almost) everything is written in Typescript, and bundled
through browserify. Ideally we would, for debug builds, export the
single transplied Javascript files, but Chromium Chromium lacks
support for modules on XHTML documents
@url{https://bugs.chromium.org/p/chromium/issues/detail?id=717643}.
However, seeing as the issue still gets frequent updates as of 2021 I
believe that this might one day get resolved.