-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathReference
49 lines (43 loc) · 1.79 KB
/
Reference
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
===========================================================
eXe2eLML - Reference
-----------------------------------------------------------
This document contains informations I found when writing
the script and details about technical choices.
Why use the "One page HTML export" of eXeLearning ?
------------------------------------------------------
1) The internal data format for an eXe document was not clear to me.
It is a zip of a ".data" file and I was not able to understand it.
2) The "One page HTML export" is a XHTML file which was very adapted
to a XSLT transformation.
3) Badfully it does not preserve the tree structure of the (exe) Idevices
(they are all put at the same level)
Structure of the "One page HTML export" of eXeLearning
------------------------------------------------------
html
head
body
div id=content
div id=header // the document title
div id=main
div class=node // each section
div id=nodeDecoration
p id=nodeTitle // section title
div class=***Idevice // each Idevice
The structure of an Idevice vary but with a common basis.
div class=***Idevice
div class=iDevice // + emphasis1 (or 0? not clear to me)
img // Idevice's icon
span class=iDeviceTitle // Idevice's title
div class=iDevice_inner // Idevice's content
Issues
------
- Paragraphs
A <p> tag is converted into a <paragraph> tag. But it seems that eLML
merge two consecutives paragraphs (is it documented ?)
I added a <newLine space="long"/> at the end of each <paragraph> which
is followed by another parapgraph.
- Fill in the Blanks
In the eXe output, answers are coded so I insert a default answer
Todo : investigate the javascript that decode the answer and use
it during the conversion.
===========================================================