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
{{ message }}
This repository has been archived by the owner on Dec 23, 2019. It is now read-only.
At the moment the behaviour of the components is that a parent hands the child a jQuery selection, inside which the child is supposed to draw itself. Unfortunately at construction time this selection may not exist, and hence we get the setupPresenter/View/Model paradigm that is in the code. Instead, components should construct themselves and enable parents to retrieve the DOM element that is to be placed on the screen, and through which events will pass.
The text was updated successfully, but these errors were encountered:
Obviously this is then leading to the idea that components communicate through the DOM events on the returned element. Those events should be custom events as components should handle low-level DOM events internally.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
At the moment the behaviour of the components is that a parent hands the child a jQuery selection, inside which the child is supposed to draw itself. Unfortunately at construction time this selection may not exist, and hence we get the setupPresenter/View/Model paradigm that is in the code. Instead, components should construct themselves and enable parents to retrieve the DOM element that is to be placed on the screen, and through which events will pass.
The text was updated successfully, but these errors were encountered: