> -------- Original Message -------- > Subject: Re: [E-devel] [Efl-technical-documentation] Site statistics > Local Time: December 18, 2017 10:05 PM > UTC Time: December 19, 2017 6:05 AM > From: pie...@couderc.eu > To: enlightenment-devel@lists.sourceforge.net > > On 12/18/2017 05:28 PM, Stephen Houston wrote: > >> "If we are to de-prioritise the new API at the cost of further development >> of legacy APIs then we are prolonging the period of time in which we >> request developers to use an API which we are intending to discontinue." >> I don't disagree. But if we de-prioritize the old API at the cost of >> furthering the development of new API then we are encouraging the >> development of unstable apis that are not complete and won't have a stable >> release for X amount of time. Which isn't exactly ideal either. I don't >> think either option sounds great and it's going to get to a point of "Don't >> use that api, it will be discontinued, but don't use that api either >> because it is unstable, incomplete, and will change". New developers will >> look at that say... uh... okay so what do I use? Something other than EFL. > > I am glad to have developed my first application under efl (eegrep = > multidimensional grep). > With legacy API. > Should I regret not having used Gnome ?
My personnal take on where we are heading with all of this, is that legacy API will still be part of EFL and be still maintained for the next 5 years at least. As the new unified API can be used in a legacy application allowing for a smooth transition out of legacy. It does seems to me that the unified API does allow for new features that were not easy to do in the legacy API (animator as an event on the object for example) which is why I expect going forward new feature to come on the unified API first and maybe only. The open question will be for bindings, especially the one that have already an existing user base. I would love to see the python bindings allow for the same smooth transition as for the C API, for the same reason as we already have a developers base that we shouldn't screw up. For other bindings, they will be 100% around the new unified API. I hope this idea is shared with most of the developers here and that we move forward with this in mind. Cedric ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
