Hello. On 07/05/16 00:42, Cedric BAIL wrote: > cedric pushed a commit to branch master. > > http://git.enlightenment.org/core/efl.git/commit/?id=45d17f100e927ee90ea782a387893add0e7f3fbd > > commit 45d17f100e927ee90ea782a387893add0e7f3fbd > Author: Cedric BAIL <[email protected]> > Date: Fri May 6 15:32:32 2016 -0700 > > ecore: update documentation of Efl.Timer. > > I am wondering how this is going to affect our legacy API documentation > which has indeed a different lifecycle.
You mean how an documentation update in the EO file would effect the published docs? They would not be part of any current/legacy docs. It will be part of the new doc system we are working on based on the EO files though. What we currently have is manually updated from time to time here: https://devs.enlightenment.org/~stefan/dokuwiki/doku.php?id=efl:reference#efl_reference This is nothing official yet but just to help Daniel and me to verify our changes. regards Stefan Schmidt ------------------------------------------------------------------------------ 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
