We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In Beta 1 Release 2, OPEL Manager has very complex architecture.
There is no MVC decoupling and it is the heaven of singleton objects.
The abuse of strong couplings makes the understanding and extending of OPEL Manager difficult.
Therefore, I propose to modularize OPEL Manager.
Previously, I wrote a proposal about "Modularization of App Core Manager (#132)".
Decoupling message routing part and message handling part from other code is the most important point of the issue.
As App Core Manager is, the most important point of OPEL Manager is decoupling them.
I have plan to introduce it in OPEL Beta 2(#144).
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
RedCarrottt
No branches or pull requests
In Beta 1 Release 2, OPEL Manager has very complex architecture.
There is no MVC decoupling and it is the heaven of singleton objects.
The abuse of strong couplings makes the understanding and extending of OPEL Manager difficult.
Therefore, I propose to modularize OPEL Manager.
Previously, I wrote a proposal about "Modularization of App Core Manager (#132)".
Decoupling message routing part and message handling part from other code is the most important point of the issue.
As App Core Manager is, the most important point of OPEL Manager is decoupling them.
I have plan to introduce it in OPEL Beta 2(#144).
The text was updated successfully, but these errors were encountered: