On 3 November 2016 at 23:14, Daniel Hirt <daniel.h...@samsung.com> wrote:
> Hi, > > Continuing the efl_part work, I couldn't find a valid reason to keep the > part logic in widgets that are not layouts. > All I see is internal usage of elm_widget_part_xxx. > > I plan to remove the part_xxx property from Elm.Widget and keep it only > in Elm.Layout. > > This doesn't concern Edje.Object. Only referring to widgets here. > > Any objections? Anyone thinks it should stay in Eo? > I agree. Our elm_widget API is not stable, while elm_object is stable API. For EO we don't actually have elm_object so we need to clean up elm_widget as best as we can to expose it in EO land. Thus, part APIs should use Efl.Part only. -- Jean-Philippe André ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
