>> Like I'd love to see efl_net being tested in the field as it's what >> ecore_con uses internally to provide legacy, as well as people being >> able to use the Eo API directly. >> > > People can't use the EO API directly. Or are we declaring EO stable now? If > so we need to properly separate which EO APIs are "final" and which are > still work in progress (all UI). So, efl_net will be tested only through > ecore_con. > > efl_net itself will wait until the rest of EO is released. Or did I miss > something?
ecore_con (old API is written on top of the EO api), as in one uses the other, as they are vastly different, "eo_legacy" shortcut couldn't be used. But they go to the same code, with all infra on top (ecore_ipc, ecore_file, elm_image...) -- Gustavo Sverzut Barbieri -------------------------------------- Mobile: +55 (16) 99354-9890 ------------------------------------------------------------------------------ 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
