It's just like eina header files. See eina/src/include. On Thu, Dec 22, 2011 at 3:38 PM, Sanjeev <[email protected]> wrote: > Isn't this going to be a burden for app developers? > # including a separate header for every widget was painful for me. (I tried > this with android apps in eclipse with suggestions and HATED it.) >
You will include Elementary.h only. > Is Elementary.h going to be a series of #includes of all widgets ? Yes. > Is documentation going to be split across headers too? I find the one header Yes. > to be convenient since I can reference across api in a single vim. Yes. > > For app developers the documentation is well presented via doxygen and gives > the categorization (which can be changed). > > Apart from modularity / 'each widget to its own', are there any other > benefits? > > Sorry, but I am not for splitting a 'joint family' of widgets :). > > -----Original Message----- > From: Michael Blumenkrantz [mailto:[email protected]] > Sent: Thursday, December 22, 2011 2:57 PM > To: Enlightenment developer list > Subject: Re: [E-devel] elementary.h split? > > On Thu, 22 Dec 2011 14:53:39 +0900 > Daniel Juyung Seo <[email protected]> wrote: > >> Yay! You changed your mind? >> >> We already had some discussion before about the header separation and >> putting documentation into header. >> > http://www.mail-archive.com/[email protected]/msg317 > 64.html >> > http://www.mail-archive.com/[email protected]/msg338 > 40.html >> > http://www.mail-archive.com/[email protected]/msg340 > 66.html >> >> But still we need to discuss how? >> 1. Separate headers by widget: list, genlist, gengrid, actionslider, >> ctxpopup, ... >> 2. Separate headers by widget groups: simple, list, map, ... >> 3. Leave one big header as is: Elementary.h >> >> It looks like you agreed to separate the header. So number 3 is out. >> 1. Separate headers by widget: list, genlist, gengrid, actionslider, >> ctxpopup, ... >> 2. Separate headers by widget groups: simple, list, map, ... >> >> Any suggestions or comments from anybody? >> >> Daniel Juyung Seo (SeoZ) >> >> On Thu, Dec 22, 2011 at 2:42 PM, Carsten Haitzler <[email protected]> >> wrote: >> > ok guys - yes. it's probably time to split elementary.h - daniel - i >> > remember you were vehement about chaning this - go for it. split it up > :) >> > >> > -- >> > ------------- Codito, ergo sum - "I code, therefore I am" -------------- >> > The Rasterman (Carsten Haitzler) [email protected] >> > >> > > has to be #1. > > > > ---------------------------------------------------------------------------- > -- > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app development. Create > new or port existing apps to sell to consumers worldwide. Explore the > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > http://p.sf.net/sfu/intel-appdev > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------------ > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app development. Create > new or port existing apps to sell to consumers worldwide. Explore the > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > http://p.sf.net/sfu/intel-appdev > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
