Hi, Perfect, that's the site updated to only include Efl.* (and eina.* as I realised there are some objects aliased).
However this highlights an issue - the Efl.Ui widgets (or at least most of them) inherit from Elm.Widget and so their parent is no longer in the docs. The contents of Elm.Widget 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 <ced...@ddlm.me> wrote: > > -------- 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: a...@andywilliams.me > > To: Enlightenment developer list < > enlightenment-devel@lists.sourceforge.net> > > > > 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? > > Yes, indeed it makes sense to not have the Eo documentation available for > those. > > Cedric > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- http://andywilliams.me http://ajwillia.ms ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
