On Thu, Dec 10, 2015 at 9:05 PM, Carsten Haitzler <[email protected]> wrote: > On Thu, 10 Dec 2015 09:49:00 -0200 Felipe Magno de Almeida > <[email protected]> said:
[snip] >> The idea of allowing using libv8 directly is that the user could use EFL >> binding embedded in an application. And then themselves would actually >> interpret and run the JavaScript code and register the EFL runtime directly, >> by initializing >> it through the register_* functions. > > isn't that kind of hard given v8 changes abi a lot? unless app itself provides > v8 - then we have the same node issue? The application would have to be willing to deal with v8 problems, yes. >> This allows great flexibility on how to run JavaScript code with EFL. >> However, >> it requires the user to deal with libv8 directly and write C++ code to make >> use of this. >> >> The EFL could itself create a libv8 interpreter and register manually, >> for example, >> to allow JavaScript code in edje without node.js but with access to the whole >> binding. This could be how Bob would begin. > > tho bob was ... lua :) It could be both :). Regards, -- Felipe Magno de Almeida ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
