On Fri, Feb 17, 2012 at 7:47 PM, Youness Alaoui <kakar...@kakaroto.homelinux.net> wrote: > Good stuff! :) > > Any chance this will cover internals too (maybe as a secondary objective) ? > While the public API is generally well documented, internal APIs aren't. > I'm referring anyways to the difficulty to understand how to write a new > evas engine for example.
No. At least not in this project, here we're focusing on the people that are coming to EFL due Tizen and they are not writing such things. Note it *looks like* we have well documented API. Just rephrasing the API name without "_" is not enough (ie: elm_win_title_set() -> Sets the title of the window). We needs to document relations (even the most subtle!), side effects, pre and post conditions (when there are such). Last but not least, need examples of real world use cases as not everyone can deduce what to do :-) -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
