Description

|interface Efl.Ui.View
|├ (P) model

Related Objects
Search...

Status	Assigned	Task
Resolved	None	T7866 efl.ui.nstate
Resolved	None	T7846 efl.ui.button
Open	None	T7510 evaluate stabilization potential of efl.ui classes and dependencies
Open	None	T7845 Unstructured stabilization items
Open	None	T7849 efl.ui.text
Open	CHAN	T7868 efl.ui.clock
Open	CHAN	T7869 efl.ui.datepicker
Open	None	T7870 efl.ui.grid
Open	None	T7873 efl.ui.image
Open	None	T7880 efl.ui.bg
Open	None	T7881 efl.ui.list
Open	cedric	T7885 efl.ui.list_view
Open	None	T7891 efl.ui.scroller
Open	None	T7893 efl.ui.slider
Open	None	T7897 efl.ui.spin
Open	CHAN	T7901 efl.ui.timepicker
Open	None	T7904 efl.ui.grid_item
Open	None	T7906 efl.ui.list_item
Open	None	T7905 efl.ui.item
Open	None	T7947 Efl.Ui.Anchor_Popup
Open	None	T7951 Efl.Ui.Text_Alert_Popup
Open	None	T7952 Efl.Ui.Scroll_Alert_Popup
Open	None	T7948 Efl.Ui.Alert_Popup
Open	None	T7902 efl.ui.popup
Resolved	None	T7859 efl.ui.box
Resolved	None	T7899 efl.ui.table
Open	None	T7578 efl.ui.view

zmike triaged this task as TODO priority.

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.

What's going on with this?

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