[eluser]esra[/eluser]
[quote author="strogg" date="1195396363"]@esra Modular Separation makes more sense about modular portal-like design, any usage example you have?[/quote]
In the past, there were no module submission guidelines. Various people were using different view schemes, different validation classes, etc. Zacharias has a user guide coming in the next release with guidelines for submitting modules. An svn site is also being set up for storing module submissions as well as the latest Modular Separation code. Afterwards, you should start to see module submissions as well as sample applications.
Because of changes to the directory structure in Modular Separation (now known as Matchbox) v2.4.1 and upcoming changes in the next release, a Matchbox module will effectively be an application which could have submodules. Each module can have directories for its own libraries, helpers, plugins, language files and configuration files. Each module can have one or more controllers and associated models and views.
I will be releasing a sample application based on Modular Separation, Coolfactor's View library and a GUI-like toolkit for wrapping the EXT JS libraries. It will be possible to create GridViews, EditViews, FormViews, TreeViews, AccordianViews, etc. which can be mixed and matched within Window-like templates. It's based on the EXT JS 2.0 Desktop sample application. Modules will be running in their own windows which can be minimized, maximized, resized, repositioned, etc. I do have CMS modules but store content centrally in a single table and use additional tables based on Joe Celko nested sets for creating separate hierarchial trees for blogs, content (articles/news), faqs, help, etc. From a feature standpoint, the CMS modules are equivalent to the Joomla core CMS components. However, the CMS modules are much more extensible and feature better encapsulation.
