On Thu, Mar 18, 2010 at 3:16 PM, Peter Johnson <[email protected]> wrote:
> On Thu, Mar 18, 2010 at 06:13:43PM +0100, Cedric BAIL wrote:
>> On Thu, Mar 18, 2010 at 6:04 PM, Dave Andreoli <[email protected]>
>> wrote:
>> > 2010/3/18 Enlightenment SVN <[email protected]>
>> >
>> >> Log:
>> >> evas: mega documentation improving commit.
>> >>
>> >> This commit moves Evas.h contents a lot, but it should not change code
>> >> (some conts were added, some function attributes were changed).
>> >>
>> >> The purpose of such is to define the order that doxygen show modules
>> >> in its documentation.
>> >>
>> >> I also splitted documentation a bit more, and added a src/examples to
>> >> list useful example code. Right now it is just a pure-evas
>> >> draw-and-save using buffer engine.
>> >
>> > I have created the same folder (examples) in edje, but under the doc
>> > folder.
>> > It's better to keep stuff consistent and change edje or evas to keep
>> > examples
>> > in the same dir (should I have to move edje/doc/examples to
>> > edje/src/examples ?)
>>
>> I would prefer all codes to go in the src subdirectorie. Does it make
>> sense to provide example in eina too ? As we already provide a lot of
>> sample inside the doxygen doc itself.
>
> Speaking as someone who uses EFL but does not develop them, I would prefer
> examples as independent source files that can be compiled and run (like
> edje_test), ideally surrounded by the autotools nonsense. I know it's more
> work, but it would be far more instructive to me.
that's my understanding as well, that's why the evas example is just
like that, you have the following options to tune build and install of
examples:
--enable-build-examples to actually compile the binaries
--enable-install-examples to install source and binary (if
compiled) under $(datadir)/evas/examples
--
Gustavo Sverzut Barbieri
http://profusion.mobi embedded systems
--------------------------------------
MSN: [email protected]
Skype: gsbarbieri
Mobile: +55 (19) 9225-2202
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
