Move JS documentation into the JS-code.

Texinfo was a bad match for how TypeScript is structured. This also
allows generation of jsdoc pages, which can be nice.

Another large win is that this opens up for the texinfo pages to replace
the Guile heading with different subheadings, including
- external library
- internal library
- C library
- ...

1 files changed, 0 insertions, 48 deletions

diff --git a/doc/ref/javascript.texi b/doc/ref/javascript.texi
deleted file mode 100644
index bbe1cb25..00000000
--- a/doc/ref/javascript.texi
+++ /dev/null
@@ -1,48 +0,0 @@
-@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.