Remove View::content property and View::set() method#2073
Conversation
97662f9 to
eae3e66
Compare
3ed3857 to
1198841
Compare
d520fe4 to
51fe277
Compare
7f03ecd to
9270290
Compare
a65e787 to
714f8e6
Compare
1d3aedd to
ad7aff6
Compare
|
I am using content frequently. |
|
In all atk4/ui classes which use content property all works as before. Bare So the question is, if you are using |
|
I am using View class often for simple views or Fomantic UI elements or fast prototyping of controls saving time to explicitly extend that class. |
I am using view directly. What about creating a new extended class named "\Atk4\Ui\Content" which can have the content property? |
That is how it is done - the class is named |
continue #2075 and #2239
View::setmethod was too abstract and clean override using LSP was not possible.If
View::$contentproperty is needed (and optionally set the data using constructor and/orView::setmethod), migrate toViewWithContentclass which behaves like the originalView.There were two major usecases for
View::$contentproperty /View::set()method:Contenttag