Dear community ;
Because some user still think that i-MSCP is working like ispCP, I would clarify the situation a bit.
About 2 years ago, me and some other of my friends decided to fork ispCP to try to provide a better open-source panel. Since these two years, many things changed:
i-MSCP Engine
The engine has been rewritten from scratch and improved over the time. In few words, the i-MSCP engine, it's:
- Modular programming, which allow separation of concerns
- Event Driven Architecture (EDA), which allows to hook into the engine without changing any core file
- Plugin API, which allows to extends i-MSCP functionalities without changing any core file
- Composer package installer which allows to provide addons as composer packages
- and a lot more...
i-MSCP GUI
While in appearance, the GUI still coded in ispCP style, many things were added and/or improved:
- Event Driven Architecture (EDA), which allows to hook into the GUI without changing any core file
- Plugin API, which allows to extends i-MSCP functionalities without changing any core file
- and a lot more...
To resume here, when you are thinking about i-MSCP, you should stop to see it as a simple ispCP fork. This was true in past year but again, a lot of things were changed.
Refs:
- http://en.wikipedia.org/wiki/Modular_programming
- http://en.wikipedia.org/wiki/Event-driven_architecture
- http://en.wikipedia.org/wiki/Plug-in_(computing)
Thanks you.
