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
Right now the Delegate code has to create and accept "materialized" public classes (State, Application, and Window), which in turn depend on the delegates, for implementing object properties and in order to emit events. An abstraction layer which converts between the two is needed so there's clean separation of concerns.
The text was updated successfully, but these errors were encountered:
tmandry
changed the title
Cleanly separate {State,Application,Window}Delegate from public classes
Cleanly separate delegates from public classes
Jan 24, 2016
Right now the Delegate code has to create and accept "materialized" public classes (State, Application, and Window), which in turn depend on the delegates, for implementing object properties and in order to emit events. An abstraction layer which converts between the two is needed so there's clean separation of concerns.
The text was updated successfully, but these errors were encountered: