On Mon, 6 Jun 2011, Gustavo Sverzut Barbieri wrote:

> Hi all,
>
> ProFUSION is proud to be back to work on EFL, thanks Samsung ;-)
>
> Our current work is to improve documentation of core EFL so we can
> match competitors like Android and iPhone, it should not just improve
> parts of API, but lots of examples, diagrams and things that lead
> third party application developers to use our libraries properly.
>
> Rasterman requested us to cover few goals:
>   - examples should be external files that can be compiled and
> checked, avoiding bogus examples ;-)
>   - all doc should be in doxygen

may i add that all the new exported functions must have @since 1.1 ?

>   - example files should be installable
>   - all examples/docs in the package itself (see below for some shortcomings)
>   - big picture should be provided to introduce users to concepts and
> ways of doing things, with diagrams and screenshots whenever possible.
> Screenshots should be auto-generated to match theme changes with ease.

discomfitor showed me that doc:

http://pugixml.googlecode.com/svn/tags/latest/docs/manual.html

I find the front page very good. Maybe you could look at it and use some 
ideas. What would be nice would be to have the same layout of the front 
page for all the EFL

Vincent

> Shortcomings: EFL is well split into independent modules, Evas does
> not depend on Ecore, for instance. But to make actual useful examples,
> we rather focus on the important bits and instead of creating our own
> implementation to keep modules independent, we'll depend on these
> external libraries FOR THE EXAMPLES.
>    That means that if you --enable-build-examples it will pull in
> ecore-evas so we have ecore_evas_new() and ecore_main_loop_begin().
> This will require examples to have 2 phase builds.
>    An alternative we could do is to create a new "sub project" inside
> examples/, with it's own "autogen.sh", "configure.ac" and
> "Makefile.am" that can even be installed into
> /usr/share/$PACKAGE/examples/.  We can link the main project to have
> "make examples" to enter examples and run the build on it.   I like
> this idea more, but let's see what others think.
>
> We're currently starting with Eina, Eet, Evas and Elementary. Please
> try to avoid endless commits changing whitespaces, okay? (/me looks at
> Seoz and Hermet).
>
> -- 
> Gustavo Sverzut Barbieri
> http://profusion.mobi embedded systems
> --------------------------------------
> MSN: barbi...@gmail.com
> Skype: gsbarbieri
> Mobile: +55 (19) 9225-2202
>
> ------------------------------------------------------------------------------
> Simplify data backup and recovery for your virtual environment with vRanger.
> Installation's a snap, and flexible recovery options mean your data is safe,
> secure and there when you need it. Discover what all the cheering's about.
> Get your free trial download today.
> http://p.sf.net/sfu/quest-dev2dev2
> _______________________________________________
> enlightenment-devel mailing list
> enlightenment-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
>
>

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to