This repository has been archived by the owner on Feb 14, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5
/
TODO
80 lines (61 loc) · 2.39 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
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
// Legend
* = URGENT
+ = SHORT TERM
- = LONG TERM
? = unsure
O = OK, done
// General
* Priorities for the next minor release:
* Make the widget more robust (font management)
+ make DPI a configurable parameter
? make pangolayout pangolinelayout areas configurable (glyph area?)
? have callback functions to notify progress while building/formatting/etc?
these should not depend on the backend
- use step area to implement linebreaking in mrows
- add possibility of disabling shaping of certain characters for shapers. Eg:
<section name="disable-shaping">
<key name="char">03BB</key>
<section name="range">
<key name="from">A0</key>
<key name="to">B0</key>
</section>
</section>
// AbiWord
* commit default shaper in abimathview
// MathML
BUGS
? when index == length in a glyph area the caret is drawn
at the right end of the focus' bounding box. It would be
more appropriate to draw it just after the glyph, especially
for mo elements. Is this really better?
? selecting the root <math> element does not show selection
ARCH IMPROVEMENTS
* MathMLNormalizingContainerElement::format can be removed
? make default value of attributes configurable
? make GlyphStringArea a leaf-like area?
- change the clone method for areas so that it checks if the
content is unchanged, and possibly implement the replace this
way
- implement auxiliary methods for searching into the area model
- It may be feasible to generalize searching functions
over areas by implementing a visitor
O it seems like the choice of having that the first child of a
vertical area is the bottommost is a bit weird. Think of the cursor:
intuitively at increasing indices the cursor should go forward (that
is right or down depending on the container). No, it is consistent
with the coordinate system used by areas where the origin is at the
bottom
PERFORMANCE IMPROVEMENTS
- in TemplateBuilder do not use the hash map for retrieving old
elements, but use accessor methods instead. Much faster
MISSING
? make setSelected virtual in Gtk_WrapperArea and implement
an open Wrapper area that selects all its children. Use the
open wrapper for groups
- runtime selection of backend
// GTK Backend
ARCH IMPROVEMENTS
+ define selection as a pluggable feature (much like decorators)
instead of a built-in feature. For some operations it may be desirable
not to have selection implemented this way
+ same with click