On Wed, 25 May 2011, Carsten Haitzler (The Rasterman) wrote:
> On Tue, 24 May 2011 22:43:33 +0900 Daniel Juyung Seo <[email protected]> > said: > >>>> I personally dislike the fact that our >>>> header are growing that much and much prefer eina's header, where each >>>> of the functionnality have it's own header >> >> I already raised the same suggestion but raster disliked header separation. >> http://www.mail-archive.com/[email protected]/msg32229.html >> We had no agreement at that time. >> >> Daniel Juyung Seo (SeoZ) > > i still don't likes itssssssss. :) one possible advantage of having several header files is that if you change one of these header files, and if the source files include only the necessary header files, then the compilation is faster. Maybe on linux, it's not that important, but, on Windows, it is (eet compiles in more than 1 mn, and to compile the EFL up to edje, + elementary, it takes more than 1 hour, so for me (and only for me, i think), increasing the compilation speed is very important) Vincent > >> On Tue, May 24, 2011 at 9:39 PM, Cedric BAIL <[email protected]> wrote: >>> On Tue, May 24, 2011 at 1:59 PM, Vincent Torri <[email protected]> wrote: >>>> On Tue, 24 May 2011, Daniel Juyung Seo wrote: >>>>> It's already done in other libs such as evas, edje, eina, ... >>>>> >>>>> And ecore has missing documentations on the website due to this. >>>>> http://docs.enlightenment.org/auto/ecore/ >>>>> Compare this with Evas documentation. >>>>> http://docs.enlightenment.org/auto/evas/ >>>> >>>> i would like to do the contrary for all the libraries : having a .dox file >>>> in doc/. One of the reason is to update the version number automatically >>>> with configure. See line 13 of the current Ecore.h. The other solution >>>> would be to have an Ecore.h modified by configure, and I don't like this. >>>> >>>> The other reason is to not pollute the main header with such doc and to >>>> actually give a documentation of all the components of an EFL in a single >>>> or several dox files >>> >>> I don't know much about your plan, idea, but one of the good point of >>> moving doc to header, is that we could generate doc with just the >>> header (so any distribution that provide a dev package, can be the >>> source of a local doxygen doc). I personally dislike the fact that our >>> header are growing that much and much prefer eina's header, where each >>> of the functionnality have it's own header... But that's another >>> discussion, so just forget my last grumbl :-) >>> -- >>> Cedric BAIL >>> >> >> ------------------------------------------------------------------------------ >> vRanger cuts backup time in half-while increasing security. >> With the market-leading solution for virtual backup and recovery, >> you get blazing-fast, flexible, and affordable data protection. >> Download your free trial now. >> http://p.sf.net/sfu/quest-d2dcopy1 >> _______________________________________________ >> enlightenment-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >> > > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > The Rasterman (Carsten Haitzler) [email protected] > > > ------------------------------------------------------------------------------ > vRanger cuts backup time in half-while increasing security. > With the market-leading solution for virtual backup and recovery, > you get blazing-fast, flexible, and affordable data protection. > Download your free trial now. > http://p.sf.net/sfu/quest-d2dcopy1 > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
