| > trying to avoid this pushes everyone into the loweest common denominator design which basically means "assume X11, a window and draw commands and you call a 'draw me' function, then have more functions to push in events etc."..... No you don't need to abstract the X11 calls. What you should expose is an fd+pollmask (or collection of them) for the program to poll (+ timeout if you need it), and a function to call to make progress. The latter you already have in C in ecore: `ecore_main_loop_iterate` The former is a bit trickier with EFL, I guess you could create something with `ecore_main_loop_select_func_set`, but the API inside out: you really want to be able do the replacement select from outside of `ecore_main_loop_iterate`. I haven't read into the implementation to see if this is already possible. > that's not of much if any concern to us as we provide a runtime already. I don't want your runtime, I just want your GUI functions.
I need you to integrate with my existing runtime. > If your source and resources are packed into a single file then the executor needs to be able to read from that file and unpack stuff from it FIRST before a single line of any lua code is run. it has nothing to do with mainloop etc. - it has to do with features existing before any lua code is run. Why? the lua code itself can do the unpacking if it wants to.
There are tools around to do this. But I don't think we need to continue this subthread. |