On Tue, May 3, 2016 at 9:34 AM, Tom Hacohen <[email protected]> wrote: > On 03/05/16 17:22, Cedric BAIL wrote: >> On May 3, 2016 1:53 AM, "Tom Hacohen" <[email protected]> wrote: >>> You broke expedite and probably other apps that rely on it. Could you >>> please update expedite to use the legacy APIs? >> >> No, this is done on purpose. We're lacking a text interface so far and >> expedite is the only application we have to validate it's usability and >> speed to some extend. If you need to tests the legacy API, there is a >> branch for 1.7 that provide just that. >> >> Current master should reflect current usability of efl interface. Of course >> this will be fixed before we release of efl 1.18 as we obviously can't >> release it without text support ! >> > > Ah, so it's on purpose that I can't benchmark my changes to the EFL? Gotcha.
As I have said, there is a 1.7 branch that will fullfill that requirement. > It's like when you (was it you?) used #warning to keep your todo. > Breaking the build is not the proper todo list... Write it down > somewhere else and fix what's broken. :( Sorry I don't have an infinite amount of time. Writting code that I will revert in the next month is very low on my priority list, especially when there is a way to get things working, see above. If you have ample time to do it, you are welcome to do the patch and revert it once the text interface has landed. -- Cedric BAIL ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
