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 Jul 22, 2021. It is now read-only.
I want to mess around with getting a step closer to react/angular/vue style approaches. Interface components are modularized. Similar to MVC controllers.
The current view-related modules are just giant balls of mud. They would become simpler to maintain if they instead were broken up into components.
I think I will visit the pages and go component by component, slowly migrating code from within a view module into a component, until the vast majority of the remaining code is just component initialization and binding.
The text was updated successfully, but these errors were encountered:
I think a good approach might be to try out the various frameworks using separate UIs.
I think backbone would be a good place to start.
I am currently thinking of the idea of recreating the options page using backbone. I would create a folder like 'backbone-options-page', put everything needed within it, and then try it out.
I want to mess around with getting a step closer to react/angular/vue style approaches. Interface components are modularized. Similar to MVC controllers.
The current view-related modules are just giant balls of mud. They would become simpler to maintain if they instead were broken up into components.
I think I will visit the pages and go component by component, slowly migrating code from within a view module into a component, until the vast majority of the remaining code is just component initialization and binding.
The text was updated successfully, but these errors were encountered: