Yop, On Thu, Feb 23, 2012 at 9:16 PM, Leandro Pereira <lean...@profusion.mobi> wrote: > 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?
The main difference with elixir and elev8 is that we choose to take a more JS approach with no one to one mapping with EFL C API. I think that switching to CamelCase would be one more step in that direction. It will make the code written for elev8 more like other JS script. So I vote for it, and soon. -- Cedric BAIL ------------------------------------------------------------------------------ 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
