Page MenuHomePhabricator

efl_canvas_vg_object/evas_object_vg: Change to legacy naming rule.
ClosedPublic

Authored by jsuya on Aug 22 2019, 9:43 PM.

Details

Summary
Enum and object decleared in efl_canvas_vg_object_eo.legacy.*
use Efl_Canvas_Vg_* nameing rule.
This skips the definition of type declared in Efl.Canvas.Vg.Object class.
So change these to legacy names.
Test Plan

N/A

Diff Detail

Repository
rEFL core/efl
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
jsuya created this revision.Aug 22 2019, 9:43 PM
jsuya requested review of this revision.Aug 22 2019, 9:43 PM
Hermet requested changes to this revision.Sun, Aug 25, 9:29 PM

It looks unnecessary, do we need to define one more naming => Evas_Object_Vg_Object ?

Eo = Evas_Object = Efl_Canvas_Vg_Object = Efl_Vg = Evas_Object_Vg_Object ...

This revision now requires changes to proceed.Sun, Aug 25, 9:29 PM
jsuya updated this revision to Diff 24484.Mon, Aug 26, 12:43 AM

This just follow the naming rule for legacy naming.
However, there is no need to maintain this because there are no generated legacy apis anymore.
So I changed it to Efl_VG.
(Efl_Canvas_Vg_Object cannot be used by clearing the typedef because of the header call order.)

Hermet accepted this revision.Tue, Aug 27, 10:08 PM
This revision is now accepted and ready to land.Tue, Aug 27, 10:08 PM
This revision was automatically updated to reflect the committed changes.