;ve postponed the rename
> of Widget (from Elm. to Efl.Ui.) until those are also merged.
> I think we will be able to do that renaming soon.
>
> Hope that clarifies it :)
>
>
>
> >
> > Thanks,
> > Andy
> >
> > On Sun, 10 Dec 2017 at 21:23 Cedric Bai
postponed the rename
of Widget (from Elm. to Efl.Ui.) until those are also merged.
I think we will be able to do that renaming soon.
Hope that clarifies it :)
>
> Thanks,
> Andy
>
> On Sun, 10 Dec 2017 at 21:23 Cedric Bail wrote:
>
> > > -------- Original Message -
idget is almost all efl_ui_* - is there some reason
why it still uses the legacy namespace for the class?
Thanks,
Andy
On Sun, 10 Dec 2017 at 21:23 Cedric Bail wrote:
> > Original Message
> > Subject: Re: [E-devel] Interfaces API not in EFL namespace
> > Local
> Original Message
> Subject: Re: [E-devel] Interfaces API not in EFL namespace
> Local Time: December 9, 2017 1:01 AM
> UTC Time: December 9, 2017 9:01 AM
> From: [email protected]
> To: Enlightenment developer list
>
> Hi,
>
> That makes sen
On Fri, 08 Dec 2017 18:35:45 + Andrew Williams said:
> Hi,
>
> I've been going through our API documentation generation (for Eo API) and I
> found some interesting numbers. We all know there is a lot to do in terms
> of porting legacy to Eo API but I found a lot of API that is in Eo but is
>
Hi,
That makes sense, thanks.
I’d like the API docs to reflect what we intend to release and an api level
- would it be ok then for me to filter for just “Efl.” prefix as the others
will be legacy?
Thanks,
Andy
On Sat, 9 Dec 2017 at 00:10, Cedric Bail wrote:
> > Original Message --
> Original Message
> Subject: [E-devel] Interfaces API not in EFL namespace
> Local Time: December 8, 2017 10:35 AM
> UTC Time: December 8, 2017 6:35 PM
> From: [email protected]
> To: Enlightenment developer list
>
> Hi,
>
> I've been going through our API documentation gener
