aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLaurent Ghigonis <laurent@p1sec.com>2012-11-04 20:12:12 +0100
committerLaurent Ghigonis <laurent@p1sec.com>2012-11-04 20:12:12 +0100
commit979c7879a307d136c50863735267a18e4f179e10 (patch)
tree4ae7372dae06aeab5db1f81fc769a11d4eb9b024
parentadd "Elife slows down my e17" section (diff)
downloadglouglou-979c7879a307d136c50863735267a18e4f179e10.tar.xz
glouglou-979c7879a307d136c50863735267a18e4f179e10.zip
add Future section
-rw-r--r--README9
1 files changed, 9 insertions, 0 deletions
diff --git a/README b/README
index fa879a3..1ce413a 100644
--- a/README
+++ b/README
@@ -31,3 +31,12 @@ to OpenGL in Composite > Rendering pannel
* Reduce the size of the elife grid by modifying the source code, in
src/elife_evas_smart.c at the definitions of NCELL_X and NCELL_Y
+
+Future
+======
+
+20:08 < loran> for the moment each cell is an evas_object. having the whole grid as one evas object and filling polygons manually (i'll take a look at seed
+ algorithm) might be faster, not sure
+20:10 < loran> but if i can have opengl rendering for the background with composite module for example, then i will improve other parts of elife, like having cell
+ created on external events like new processes, packets blocked by firewall, ...
+20:10 < loran> :p