aboutsummaryrefslogtreecommitdiffstats
path: root/doc/TODO.txt
blob: 47e08d708f88c2fb4d45a35c6d43b317dac62e26 (plain) (blame)
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
TODO
====

* zoom

* BUG: show nodes labels does not show old nodes labels
reproduce: do not show labels, add edges, show label, add edges

* BUG: sometimes when you add nodes during layouting, the graph is broken
a new edge attaches to the wrong new vertice
it seems to be always the same node numbers that gets this wrong edge

* BUG: vertices / vertices text fight for being on top. use evas layers ?
add 500 edges to reproduce, and watch the nodes

* speed: evas_object_rectangles
04:40 <@raster> they add clipoouts
04:41 <@raster> make them just a bit translucent
04:41 <@raster> and it'll be faster

* find a better storage type for vertices
quick access O(1) -> table
possibility to foreach and remove at the same time

* possible future API: no edges no vertices for the user

struct Egraph_Vertice {
  const char *name;
  int vertice_id;
  Evas_Object *o;
  void *data;
}
egraph_vertice_add(Egraph *eg, const char *name, void *data);
egraph_edge_add(Egraph *eg,
                const char *a, const char *b, void *data);

* speed: draw directly to a surface and map to evas via invisible polygons
see elementary/src/bin/test_gesture_layer3.c
04:45 < glouglou> i would like to draw directly in a surface and then give it to evas, but i want in the future to have user interaction with the nodes of my 
                  graph, like click click reaction, so i guess i cannot escape from creating one evas object for each node and edge
04:46 <@raster> trick:
04:47 <@raster> u can just create invisible rects
04:47 < glouglou> (i can imagine crazy mapping of the clicks on my surface that triggers evas callbacks, but i'm not that crazy)
04:47 <@raster> and overlay them on your image
04:47 <@raster> use them for event stuff
04:47 < glouglou> lol
04:47 <@raster> or polygons tyoo
04:47 <@raster> thats about the only use of polygons
04:47 <@raster> as u can do exact inside/outside poly checks for events
04:48 < glouglou> i think you are talking about the crazy things i don't want to do :p
04:48 <@raster> one of the elm demos does this
04:48 <@raster> for soming/rotating with little photos
04:48 <@raster> multitouch test stuff

* speed: from Thanatermesis :
the Core library (https://github.com/acaudwell/Core)
renders to OpenGL directly
used by :
http://code.google.com/p/logstalgia/
https://github.com/acaudwell/Gource (http://code.google.com/p/gource/)