Hello,

After using QCubed on several of my applications (with great success thanks to the great framework API documentation, forums, tutorials, and examples), I've decided that it would suit me better to have (on a per-server basis) one central QCubed framework installed (1.1.3, 2.0.2, etc.), which is then used by several different applications for code-generation, QCubed classes, etc.

I've been noodling on how I would achieve this, but haven't come up with much thus far. My basic idea is to have things laid out like this (must be semi-portable between Linux and Windows servers, though some edits/changes are expected):

1a) Reporting application -- Development version
- Files: /var/www/reporting-trunk/lib/qcubed/...
- DB: localhost:3306/reporting-trunk

1b) Reporting application -- Released version
- Files: /var/www/reporting/lib/qcubed/...
- DB: localhost:3306/reporting

2a) Mail application -- Development version
- Files: /var/www/mail-trunk/lib/qcubed/...
- DB: localhost:3306/mail-trunk

2b) Mail application -- Released version
- Files: /var/www/mail/lib/qcubed/...
- DB: localhost:3306/mail

[... etc ...]

As you can see, for each application (including whether or not it's the released version customers interface with or the TRUNK version where new development work happens), I have to have a QCubed framework for each one. It seems like I should be able to somehow define the QCubed framework in a more general fashion (where any application on the server could use it, e.g. /etc/php/qcubed/), and then take advantage of the code-generation for each application (which would put the code-generated files under each of it's own separate directories, like /var/www/{application}/lib/qcubed/includes/{formbase_classes_generated,meta_controls,model,tmp}/), and then each application would also have it's own configuration directory with codegen_settings.xml, {configuration,footer,header,prepend}.inc.php, etc.

My first thought was to somehow use the SERVER_INSTANCE constant, but I'm not sure how that would fit in. At a more meta-level, I need to know if doing this type of shared framework is even advisable (one framework to rule them all I suppose, right? ;-)).