On Mon, 8 Jan 2018 10:40:13 -0200 Gustavo Sverzut Barbieri
said:
> On Mon, Jan 8, 2018 at 4:40 AM, Jean-Philippe André wrote:
> >> Efl.File -> Efl.Io.File
> >>
> >
> > This name makes sense
> > But I already see an Efl.Io.File class? Gustavo, any input here?
> > Efl.Io refers to actual I/O (open
On Mon, Jan 8, 2018 at 1:40 PM, Gustavo Sverzut Barbieri wrote:
> On Mon, Jan 8, 2018 at 4:40 AM, Jean-Philippe André
> wrote:
> >> Efl.File -> Efl.Io.File
> >>
> >
> > This name makes sense
> > But I already see an Efl.Io.File class? Gustavo, any input here?
> > Efl.Io refers to actual I/O (ope
On Mon, Jan 8, 2018 at 4:40 AM, Jean-Philippe André wrote:
>> Efl.File -> Efl.Io.File
>>
>
> This name makes sense
> But I already see an Efl.Io.File class? Gustavo, any input here?
> Efl.Io refers to actual I/O (open, read, write, close...) while Efl.File is
> just for the (image/edje) file set/g
On Mon, 8 Jan 2018 15:40:02 +0900 Jean-Philippe André said:
> More renaming ahead? :)
>
> I'll assume we might keep an "eo_prefix" for some APIs like "efl_part" or
> "efl_file" to not become too long in C (important: this affects only C!).
>
> On Sat, Dec 23, 2017 at 3:16 AM, Andrew Williams
>
More renaming ahead? :)
I'll assume we might keep an "eo_prefix" for some APIs like "efl_part" or
"efl_file" to not become too long in C (important: this affects only C!).
On Sat, Dec 23, 2017 at 3:16 AM, Andrew Williams
wrote:
> Hi all,
>
> I recently updated the API landing page to group by n
Hi all,
I recently updated the API landing page to group by namespace:
https://www.enlightenment.org/develop/api/start
What this has indicated is that there are a few things out of place. The
list as far as I can see it is:
Efl.Access.* -> Efl.Ui.Access
Efl.Animator -> Efl.Animation.Animator
Efl
