On Fri, 24 Feb 2012 10:44:24 +0900 Elevate Efl <eflel...@gmail.com> said:
i see camelcase... and i just go... "ewwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww c-plus-plus conventions!". > This complaint was raised already, thought about and rejected, because > elev8 was in prototype phase and we wanted to follow EFL style to be > consistent with the rest of the code base. > > For the advanced use cases, I do see your point. Users of elev8 'API' might > end up having a mix of their style and EFL style in their code. But isn't > that the case with using any third party library? > > (FYI : DART follows camel case as well, but with some variations) > http://www.dartlang.org/articles/style-guide/#names > > But camel case, seems like an agreed upon style for C++ across many > projects. > Since elev8 is quite small in code size, now would be a good time to change > the style. I can see prospective users complaining about readability of the > code. > > > > On Fri, Feb 24, 2012 at 5:16 AM, Leandro Pereira > <lean...@profusion.mobi>wrote: > > > Hi. > > > > I'd like to propose we move the naming scheme of Elev8's API to > > CamelCase, so that it is more consistent with other things our target > > developers might be using. > > > > JavaScript itself, Node.js, jQuery, and even Tizen APIs (at least the > > ones I've looked into -- WebRuntime stuff to be more precise) uses this > > scheme. > > > > I'm proposing this because we're working on a JavaScript framework to > > develop applications in EFL using Elev8 as a base. > > > > And although the idea is to completely hide what's below (where naming > > wouldn't matter because it'd be inside a library the user would import), > > eventually for certain more advanced tasks, this might be possible and > > I'd like to maintain consistency and, most importantly, a sense of > > familiarity to the target developer base. > > > > Any point against this change in elev8? Are there any major changes > > waiting to be merged that I should worry about? > > > > Cheers, > > Leandro > > > > > > > > ------------------------------------------------------------------------------ > > 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 > > > ------------------------------------------------------------------------------ > 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 > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ 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
