-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathTODO
59 lines (57 loc) · 2.56 KB
/
TODO
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
49
50
51
52
53
54
55
56
57
58
59
TODO
---
- fix glyph server hack
- fix window title hack
- get cloning to work
- positioning is wrong
- get rotation to work (alt click)
- rotates wildly, some calculation is wrong
- get to run again on the n800
- SVG ellipse is not elliptic enough at large sizes. The
radius should be factored into the bezier calculation
(which is trivial to so)
- change gezira real streams contructors to take varargs instead of an array
- create getters for gezira streams attributes (e.g., rotation.angle)
- make shift key work (for events), and change the shift state from
a parameter to a function call on the sdl object
- Fix getTransformToElement
- need to rewrite setAttributeNS to reuse the attr node, not
create a whole new one each time
- I should look at the "fill-opacity" attribute to grab
alpha of fill color.
- fix "copy" inheritance problem (see dom/events.js) by using
true JS inheritance just for the Node clone family? This might also
fix the fragile ordering of loaded files/packages
- make all gezira parents (groups, too?) point to a default
gezira (blank) object upon creation? This "null" node could be
used in several places (instead of just a gezira.Node with no children)
- ideally I'd have a object mapping to and from dom and gezira objects.
This would get rid of the domObject._graphics stuff, and allow for the
hit testing to work. Expose a hash table object? Or a special purpose
function?
- Fix memory leaks of gezira objects. Must install a finalizer gezira
JS objects.
- expose a window.height window.width getters (and setters?)
- an element may be added to the dom render queue multiple times because
multiple attributes of that element are changed in a given phase. Should
we do a uniq() on that queue then? How much of a win does this get
me? Can either == or === get me a fast object id-like comparison?
- write glue code for other JS engines, window/events libraries and
graphics renderers
- v8
- nitro
- rhino
- plug in an (X)HTML parser (see OMeta/JS)
- To make our (X)HTML output the same as FF, we need to:
- support doctype
- the script tags, plus the "1" child text node in each
- don't emit </endtags> for elements that don't (can't?) have
children (e.g., <stop />)
- don't emit implied args for transforms (e.g., translate(0 0))
- don't output default implied values (or keep track if they have been
changed (specified))
- no newlines for text nodes
- spaces/commas for lists
- same order of the attributes
- network functionality. Bindings to libcurl (or something like it)
- CSS