You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, given that Inset takes some responsibilities away from View, it still does not stop users from using View to achieve what Inset is meant to do. What if we use the configuration that we apply to Inset and takes that to create a View that is "neutered" so that some concerns that Inset is meant to take are removed from View (like padding, margin, etc,).
There are going to likely be some overlaps since cleanly separating View into Inset and NeuteredView (I need a better name) would probably prove to be inconvenient.
The text was updated successfully, but these errors were encountered:
So, given that
Inset
takes some responsibilities away fromView
, it still does not stop users from usingView
to achieve whatInset
is meant to do. What if we use the configuration that we apply toInset
and takes that to create aView
that is "neutered" so that some concerns thatInset
is meant to take are removed fromView
(like padding, margin, etc,).There are going to likely be some overlaps since cleanly separating
View
intoInset
andNeuteredView
(I need a better name) would probably prove to be inconvenient.The text was updated successfully, but these errors were encountered: