@@ -80,7 +80,7 @@ main = run 3708 $ do
80 appendChild newParagraph text
80 appendChild newParagraph text
81 appendChild body (Just newParagraph)
81 appendChild body (Just newParagraph)
84 -- Make an exit button
84 -- Make an exit button
85 exitMVar <- liftIO newEmptyMVar
85 exitMVar <- liftIO newEmptyMVar
86 Just exit <- createElement doc (Just "span")
86 Just exit <- createElement doc (Just "span")
@@ -111,8 +111,8 @@ There are a number of different JSaddle runners to choose from
111* [jsaddle-clib](https://hackage.haskell.org/package/jsaddle-clib) - C interface used to run JSaddle on Android using JNI.
111* [jsaddle-clib](https://hackage.haskell.org/package/jsaddle-clib) - C interface used to run JSaddle on Android using JNI.
113In all of these cases a web control or browser of some sort is used. An
113In all of these cases a web control or browser of some sort is used. An
114−[HTML file](https://github.com/ghcjs/jsaddle/blob/master/data/index.html)
114+[HTML file](./jsaddle/src/Language/Javascript/JSaddle/Run/Files.hs#L24)
115−and a [small JavaScript command interpreter](https://github.com/ghcjs/jsaddle/blob/master/data/jsaddle.js)
115+and a [small JavaScript command interpreter](./jsaddle/src/Language/Javascript/JSaddle/Run/Files.hs#L340)
116are loaded into it. Then the native GHC compiled JSaddle code runs. In order to interact with the browser
116are loaded into it. Then the native GHC compiled JSaddle code runs. In order to interact with the browser
117it sends commands to the JavaScript command interpreter. The mechanism for sending the commands differs
117it sends commands to the JavaScript command interpreter. The mechanism for sending the commands differs
118for the different runners, but they are always combined into batches and encoded in JSON.
118for the different runners, but they are always combined into batches and encoded in JSON.