Hi On 05/07/2014 01:30 PM, Stefan Schmidt wrote: > Hello. > > On Wed, 2014-05-07 at 11:01, Stefan Schmidt wrote: >> Hello. >> >> On Wed, 2014-05-07 at 01:15, Daniel Juyung Seo wrote: >>> On Tue, May 6, 2014 at 8:51 PM, Stefan Schmidt >>> <[email protected]>wrote: >>> >>>> o Removed symbols seem only to come from the eo2 change which we have >>>> declared unstable right now. But please have another look if that is >>>> correct: >>>> >>>> elm_atspi_object_eo.h, libelementary.so.1.9.3 >>>> elm_atspi_component_interface_get ( ) >>>> elm_atspi_obj_class_get ( ) >>>> elm_atspi_widget_obj_class_get ( ) >>>> elm_atspi_window_interface_get ( ) >>>> >>>> elm_interface_fileselector.h, libelementary.so.1.9.3 >>>> elm_fileselector_interface_get ( ) >>>> >>>> elm_interface_scrollable.h, libelementary.so.1.9.3 >>>> elm_obj_pan_eo_class_get ( ) >>>> elm_scrollable_interface_get ( ) >>>> >>>> >>> Not sure about the removal of scrollable/fileselector_interface_get() APIs. >>> They were published in public headers. >>> Need to listen to others' opinions. >> Its an API break if it was available through public headers before and >> we remove it now. Why was it removed? Who did it? >> >> These look like problems and we need to find out about them and fix >> before the release. > elm_fileselector_interface_get was introduced with > 0b4b942bfc2ebb9c4ac7349232ff6fd428d21e1a by Ryuan Choi. > > Disabled with f7086e32ae1648515bf9f0ea86c80f4fdbee3c18 by Daniel Zaoui > and later removed. Supposed to be unstable Eo API. > > > elm_scrollable_interface_get was introduced with > dc95ebf215507dbd00827ec839f531a5c4ef84d2 by Yakov Goldberg and Daniel Zaoui. > > Disabled with 35f09ca0bd27020080665fb12d5dd1fe87672dc9 by Daniel Zaoui > and later removed.
This one too. > > The question is now if we considered these APIs as unstable EO APIs or > not. In the later case we need to get them back. > > regards > Stefan Schmidt > > ------------------------------------------------------------------------------ > Is your legacy SCM system holding you back? Join Perforce May 7 to find out: > • 3 signs your SCM is hindering your productivity > • Requirements for releasing software faster > • Expert tips and advice for migrating your SCM now > http://p.sf.net/sfu/perforce > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
