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 Nov 16, 2017. It is now read-only.
There are some reasons to have editor UI controller class:
some methods and properties like _createEditableUIView, get editableElement(), featureComponents does not belong to the view, they could be moved to the Editor main controller, but then it would handle too much,
engine bring its controllers, so UI could do it too, it would create a nice separation where there are separated controllers to handle engine and UI and the main Editor class only bind these pieces together,
the editor API for plugins should be well defined, so every developer should know what classes/properties should be brought to make plugins works fine with his editor. The View should not be a part of such API, so featureComponents should be defined in a better place.
The text was updated successfully, but these errors were encountered:
There are some reasons to have editor UI controller class:
_createEditableUIView
,get editableElement()
,featureComponents
does not belong to the view, they could be moved to theEditor
main controller, but then it would handle too much,Editor
class only bind these pieces together,View
should not be a part of such API, sofeatureComponents
should be defined in a better place.The text was updated successfully, but these errors were encountered: