I'm wondering why phpmyadmin, webmail, filemanager etc part of the omega tree?

They're big (phpmyadmin is HUGE) and do not interact in any way with omega.

Each single release of these packages can be installed independently.

IMHO they are only taking space in the svn tree and do no good at all (we're just tracking someone else's repository).

I think a plugin system with these components detached would be much better.

Or am I missing something?

ispcomm

You're missing the one point: "it is because it was like this...".

Example: in pma it's the config.inc.php and the omega theme (folder) - but this could be delivered separately... (great would be: automated installation of the newest pma version :-)))

We should discuss this for version after 1.0

/J

Yes... I missed that It has always pissed me off that I had to keep pma in my local repository, so seeing it in omega too was not nice.

My main reason is more technical: having a local package (even worse: a customized package) of another project means that I have to follow the development of the other project and fix bugs in parallel in my customized version.

Making omega work with the default squirrel and pma and whatever on a server is much easier in the long run and updates are a matter of apt-get update; apt-get upgrade (that's why I love debian).

I think a generic "plugin" system and packages would be nice but I'd limit their number (perhaps pma, a couple of webmails like squirrel and roundcube). Installing anything more would become troublesome (like in cpanel... it never works).

Also, a theme for the webmail is the maximum I'd do (just because end users might like it). A theme for pma for example is not something a developer will appreciate that much (i.e.... a dev is likely to upload the last pma to their site instead of using our own version).

ispcomm

+1 this is the roadmap for the future of ispCP after v1.0 - to turn it into a framework.

already planed

already planed

Nice to hear that.

ispcomm