Proposal for extra file structure
Hello folks.
I'm a former contributor to QCubed project, but last 2.5 years and have been away from this project in behalf Drupal.
I want to back to this great open source project, I just download the 2.0.2 version and I'm trying to migration a personal project to this version in order to get familiar with new stuffs.
I want to suggest to core developer some extra structure to enable project be updated in a easy way.
Scenery:
We we built an application with QCubed we have 3 basic elements QForms, QTemplates, Assets ( JS, CSS, Images, Custom PHP Libraries).
So my ideas is create this extra files in filesystem of QCubed
QCubed
--------> App
----------------> QForms
----------------> QTemplates
----------------> Assets
------------------------> JS
--------------------------------> Images
------------------------> CSS
------------------------> PHP ( Custom Libraries)
So the idea is modify the core to enable QForms can be included in AutoLoad, and also templates, assets could be referenced include templates.
Now maybe are wondering, why is necessary, well my ides is when you get a full application working and a we have a new release i.e 2.1.x, we don't need to make a complex process of update, following this structure we need to do simple steps listed below
0) Backup our application folder
1) Download latest version of QCubed
2) Copy our app folder inside new QCubed version
3) QA our application
4) Enjoy
I know the auto generated form are really useful for small application, but for professional applications, we always needs to create our own version of QForms.
If the core team are agree ir little agree with this proposal, I can post this changes to subversion.
Regards,
enzo

Hi enzo, nice to meet another qbo =)
Is really interesting the proposal of this new folder order.
I was working lately in a proyect and also in guide of "How To Construct And Organize A Multi-Themeable Backend" (A.K.A Control Panel).
I have to recognice doing this in QCubed was so easy than other fremeworks - CakePHP - puaj!!! X-(
I never do a migration between QCubed versions, because I'm kind of "newbee" in the community (I meet QCubed since version 2.0) but I finish this proyect and I think this fit better in your folder structure than actual.
I think it's gonna be a great update and useful (Is kind of hard learn were QCubed left the files with out documentation and actual folder structure don't help much to be honest) but also maybe would be very challenging and need a lot of work, some core files would be involved, but the benefits will be outstanding.
Count with my vote ! =)
Regards,
JMI - Instinctively Moving...