interface Efl.Ui.View ├ (P) model ├ (E) model,changed
Description
Details
Status | Assigned | Task | |
---|---|---|---|
· · · | |||
Open | None | T7845 Unstructured stabilization items | |
Open | CHAN | T7868 efl.ui.clock | |
Resolved | None | T7846 efl.ui.button | |
Resolved | None | T7859 efl.ui.box | |
Resolved | CHAN | T7869 efl.ui.datepicker | |
Resolved | None | T7870 efl.ui.grid | |
Resolved | None | T7873 efl.ui.image | |
Resolved | None | T7880 efl.ui.bg | |
Resolved | None | T7881 efl.ui.list | |
Resolved | cedric | T7885 efl.ui.list_view | |
Resolved | None | T7891 efl.ui.scroller | |
Resolved | None | T7893 efl.ui.slider | |
Resolved | None | T7897 efl.ui.spin | |
Resolved | None | T7899 efl.ui.table | |
Open | None | T7849 efl.ui.text | |
Resolved | CHAN | T7901 efl.ui.timepicker | |
Resolved | None | T7902 efl.ui.popup | |
Resolved | None | T7905 efl.ui.item | |
Resolved | None | T7578 efl.ui.view | |
· · · |
If @cedric @felipealmeida , and @SanghyeonLee don't have any objection on this definition, I think there would be no problem.
This one is very simple, the question left open is where are the binding defined and if it shouldn't be on this class.
I personally feel that this API is simple and ready from that point of view. Documentation needs to be improved still.
Docs need to be improved for everything, that's not a blocker. It seems like this is simple enough that nothing could go wrong.
I also agreed @cedric.
once we were talking about name change to "model_client" but view is more generic and acceptable.
Lets wait with this until model is stable, otherwise it has no functions, which is kind of useless
Is this interface responsible to implement affine transformation ? or is it implemented in other place ?
Efl.Ui.View is the interface for View as in Model View ViewModel (MVVM) infrastructure.
This interface has not evolved much since we started working on MVVM and if everyone is ok with it, I would like to take it out of @beta.