Installer and more Components

[eyezberg]

Hi,

just installed Phils mosDirectory yesterday for the 1st time (great!),
and noticed something: there are quite a few included modules and/or bots,
which the component uploads with itself, but which are not installed.
You later have the option of (un)installing these from the component interface.

This made me think:
couldn't Mambo Core come also as/with different add-on packages:
-commerce (phpshop, partner module, help desk etc..)
-community (CB, simpleboard, userlist xtd, mypms, whatever..)
-artitst site (bibliography, artist directory, gallery,..)
-fully featured (every usefull CMT (whoever decides on the term usefull..) ..)
-...

where these components would be bundled into one pack, uploaded all at once, but not installed, and then a separate page in admin provides links to install/de-install any of these components or modules?
Something like an extra "com_install_cmt" component they could hook up with, or just a page with links to (un)install ...

I guess this wouldn't be part of the official downloads,
but parallel projects, which take care of bundling the latest CMT versions into each "pack" ...

Would that interest anybody?
Just so you can pack this all up,
one single upload for the user,
(Mambo is installed)
and then no need to upload anything else,
the whole "pack" is there already,
you just have to "activate" the parts you want to use ...
kinda like "Fantastico", click a link, and you got it..

..?

(I guess this should be moved somewhere else, it's not really a core feature, sorry for that, maybe just the part about providing post-upload install facilities for CMTs..? mods, feel free to place where you see fit ;) )

[pagerefiner]

I've been really getting deep into the Mambo code lately and comparing it to the classical MVC 2 approach. In a sense, Mambo uses MVC at both the core framework level and within individual component frameworks. With a bit of work, Mambo could become more like a application server or more appropriately a package server using Mambo lingo.

If you replaced the current components/, modules/, and mambots/ directories with a packages/ directory, this might be a good approach. There could be a packages/services/ package that included all site wide services such as login, registration, banners, user accounts, polls, etc. Then the remaining CMS oriented components could be moved under a packages/mambo/ directory. That is treat the CMS itself as a Mambo package with its own set of components, modules, and plugins. Then third-party developers could build other packages to expand on the Mambo platform.