Modular system design
Posted: Thu Apr 12, 2007 4:34 pm
When PHP 5 came out, a friend of mine who was much more into programming than me at that point tried to roughly explain the design principles behind a modular platform, whereby small modules that performed various functions would "connect" to a core framework that, by itself, has very little functionality.
I wasn't very clear on what he was talking about back then, but now I'm working on a large scale project and I feel like a system designed like that would be ideal.
I spent some time trying to reason out what elements a "core" would contain and how "modules" might be installed, etc.
I assume that the core would contain all the language variables and methods of translating customized markup (like BB Code, etc,) as well as the elements that determine the overall display of the site, things related to the DOM, global methods, global DB calls, XML parsers, and some sort of "Installation" system that allows modules to instruct the core how to display and interoperate with them.
Again, this is strictly guess work. I'm very vague on what the hell he was talking about. Perhaps someone can help me out here?
Thanks.
I wasn't very clear on what he was talking about back then, but now I'm working on a large scale project and I feel like a system designed like that would be ideal.
I spent some time trying to reason out what elements a "core" would contain and how "modules" might be installed, etc.
I assume that the core would contain all the language variables and methods of translating customized markup (like BB Code, etc,) as well as the elements that determine the overall display of the site, things related to the DOM, global methods, global DB calls, XML parsers, and some sort of "Installation" system that allows modules to instruct the core how to display and interoperate with them.
Again, this is strictly guess work. I'm very vague on what the hell he was talking about. Perhaps someone can help me out here?
Thanks.