On Thu, Apr 9, 2015 at 3:50 PM, Tom Hacohen <tom.haco...@samsung.com> wrote: > On 08/04/15 07:37, Jean-Philippe André wrote: >> @Eo guys,
[snip] >> Evas_Image for evas_object_image functions, >> Evas_Object for generic evas_object functions, >> And Eo only as a last resort? >> >> I spotted those in the ABI report. > > The Evas_Image and etc. are new. We should use them when appropriate > (think normal OOP, common ancestor). However I'd be wary about using > them now as iirc they should be BETA_API. Maybe I'm wrong and they > aren't yet. > > Either way, in the .eo files, you should definitely use the correct > class, in the form of: Elm.Button or Edje.Object. Yes. True. And _not_ Edje_Object, but Edje.Object. They are both going to work for C, but for other languages that is quite different. > -- > Tom. Regards, -- Felipe Magno de Almeida ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
