We actually know a lot of possible property on an object from the eolian file and could generate them automatically.
- Differential Revisions
- D7969: eo: make reflection getter const function.
D7946: efl: for consistency and effiency move Efl.Model event to send stringshare like Property_Bind event.
D7945: efl: add an event for the View to know if someone did bound a property.
D7944: eo: add helper for basic property type reflection.
D7943: elementary: rely on Efl.Ui.Widget to do more of property binding for MVVM in Efl.Ui.Layout.
D7942: elementary: Efl.Ui.Image now rely on Efl.Ui.Widget infrastructure for View and Property_Bind.
D7941: elementary: implemente property_bind support on all widget using property reflection.
D7940: efl: add an event to notify that the View property has changed.
D7939: efl: Property_Bind should actually tell us if it succeeded or failed by returning an Eina.Error.
D7938: eo: add tests for efl_property_reflection_exist.
D7937: eo: add efl_property_reflection_exist to be able to know if a property is available on an object.
D7936: eo: return an Eina_Value error when a get for a property is not implemented.
D7935: eo: make reflection setter able to return an error code in case of failure.
|Open||None||T7142 efl 2.0 considerations|
|Open||cedric||T5301 Make EFL easier to use by improving its interface|
|Open||felipealmeida||T5354 Provide infrastructure for MVVM|
|Resolved||cedric||T7668 Autogenerate property_bind View|
|Resolved||bu5hm4n||T7677 Add a little reflection API|
|Resolved||bu5hm4n||T7681 Eo simple reflection API|
|Resolved||q66||T7682 Eolian generation of the reflection API|