2 [title ClickSlide Demo]
4 [footer Clickslide Demo]
8 a Compiler for Browser based Slideshows
12 [li Why would I write another Slideshow system]
13 [li What's wrong with JavaScript?]
14 [li How do you simplify HTML?]
18 [h2 Why Write another Slideshow System?]
20 [li WYSIWYG Slideshow applications are annoying [ul
21 [li too much fiddling, not straight to point]
23 [li [em LaTeX] is not exactly casual]
24 [li Existing Browser Slideshows are [ul
25 [li based on JavaScript (see next slide)]
26 [li Either verbous HTML, or unflexible markup]
31 [h2 Why avoid JavaScript]
33 [li Nothing wrong with JS as a programming language, [strong but...]]
34 [li Freedom to [em Use], [em Study], [em Share], and [em Improve] can in practice not be applied to code served from another Computer (regardless of the license this code is under)]
35 [li Impossible to get Browser security straight for Turing complete programs [ul
36 [li → Massive security problems, which are fundamentally unresolvable]
37 [li HTML and CSS are not Turing complete (CSS is a [em regular] language)]
39 [li Performance killer in practice]
42 [slide [h2 Simplifying HTML]
43 Maintain the flexibility of plain HTML. Decrease verbosity of the code. [br]
44 [pre style="display: inline-block; width: 46%; background-image: url(exb0_light.jpg);"
47 \<title\>Demo\</title\>
49 \<body id="frontpage"\>
50 \<h1 class="top"\>Headline\</h1\>
54 [pre style="display: inline-block; width: 46%; background-image: url(exb3_light.jpg);"
65 [slide [h1 This is a \<h1\>]
66 [pre \[h1 This is a \\\<h1\\\>\]]
71 \[h2 This is a \\\<h2\\\>\]
74 \[li ... gets uncovered ...\]
75 \[li ... item by item\]
81 [li ... gets uncovered ...]