Hello, So in the coming month, we are going to work very hard on getting the Eo API stable and part of that is what we call the EFL interface with this new API. This API is going to be used by all binding that will be autogenerated. Basically you can think of it as EFL 2.0 base (Legacy staying around on top of it).
For today I would like to point at the new animator API based on an Eo event triggered on Evas canvas and all Evas_Object. You can give a look at how it work in Efl: https://git.enlightenment.org/core/efl.git/commit/?id=e405afb2f94a5c72a4cd120b2e1391571c4e310f https://git.enlightenment.org/core/efl.git/commit/?id=62030c1003111985922cdb25d56d448601584606 https://git.enlightenment.org/core/efl.git/commit/?id=e8134e868a4369a89e2bb1d65e8ea8dfd72684ad And how to use it: https://git.enlightenment.org/core/elementary.git/commit/?id=403843500119ae05445907808a049220dfe455f6 I just realized that this example could have been simpler as the callback will be destroyed during the object destruction and there is no need to unregister the animator in the destructor anymore. Let me know if you have any comment or things that needs to be clarified. -- Cedric BAIL ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
