On 28/10/13 22:17, Felipe Magno de Almeida wrote:
> Hello all,
>
> I'm working on an Eo API change for EFL. We're working on top of
> Jérémy Zurcher's eo2 branch.
> The problem with creating Eo API with the current Eo or with eo2 is
> that information about a Eo class becomes inevatibly scattered a
Hi Felipe,
I think Cedric told you but we have a project for the boilerplate that
is called Eolian. You describe a Eo class in JSON format (at least for
the moment according to the vote that was in the ml) and then can
generate the EO1/2 API functions, legacy functions, classes information
in
Em Seg, 2013-10-28 às 21:03 -0200, Felipe Magno de Almeida escreveu:
> Also,
>
> The C++ binding is not just the generated headers, there is going to
> be a EINA-specific C++ API and more classes that will help with MVC
> and other helpful abstractions that aren't attainable with generated
> code
Em Seg, 2013-10-28 às 20:55 -0200, Felipe Magno de Almeida escreveu:
> We're not creating a preprocessing tool as moc. The tool is just used
> to generate C++ classes from C, so that we have C++ classes that we
> can inherit, instantiate and call with a C++ familiar syntax. It will
> not be requir
Also,
The C++ binding is not just the generated headers, there is going to
be a EINA-specific C++ API and more classes that will help with MVC
and other helpful abstractions that aren't attainable with generated
code. The generated C++, though, gives a type-safe layer and makes
evolution easier an
Hello Vinicius,
On Mon, Oct 28, 2013 at 8:48 PM, Vinícius dos Santos Oliveira
wrote:
> Em Seg, 2013-10-28 às 20:17 -0200, Felipe Magno de Almeida escreveu:
>
>> The tool that will generate the C++ binding will read the header files
>> and with a CPP library it wil hook on EO3_DEFINE_* and EO3_DEC
Em Seg, 2013-10-28 às 20:17 -0200, Felipe Magno de Almeida escreveu:
> The tool that will generate the C++ binding will read the header files
> and with a CPP library it wil hook on EO3_DEFINE_* and EO3_DECLARE_*
> to read the class informations. This part of the tool will be written
> as a C++ li
Hello all,
I'm working on an Eo API change for EFL. We're working on top of
Jérémy Zurcher's eo2 branch.
The problem with creating Eo API with the current Eo or with eo2 is
that information about a Eo class becomes inevatibly scattered and
adds a lot of redudancy. For example in eo1 there's the ne
