Another, Better, even simpler override idea

So the other override idea was to put a new override subfolder into each folder, and then put the contribbed version of the file being replaced into that folder. If an override existed, use it, otherwise, fallback to the core. This worked good, but it can be a lot of extra folders which can get confusing.

The New, NEW, idea is to have a separate main folder for "contribs" which would run along side of the main folders, and follow the same directory structure as the rest of the files.

For Example:

Core file:
/catalog/controller/product.php

Contrib override file:
/contrib/catalog/controller/product.php

The same easy code change would still apply to the library files:
- library/application/controller.php
CHANGE: TO: The same global on/off option could be used as well from the admin section.
But in comparison to my other override idea, this one is:
- a lot less excess (and usually empty) folders.
- a lot less confusing (since there won't be an intermingling of core and custom throughout the main folders)
- a lot easier to debug and follow which contribs you've installed and which is causing the problem.
- a lot easier to see if 2 contribs conflict (since it will warn you about file overwrite)
- a lot easier to use existing contribs without them having to be restructured and reuploaded. Just tell people to extract them into the "contrib" folder
- a lot easier for me to release it as a contrib for people to try (other idea would be hard to make as a contrib)

So I think I just beat out my genius idea with an even geniuser idea

Visual example:

How does it work?
It is very simple to use the override. There are no files to modify or any special versions needed. The only thing you need to change is the location that you upload the files to.

Normally, you would install a contribution to match the directory structure of your cart. For example:
If your file directory is like this, you would normally upload the files to match the directory structure:

http://www.unbannable.com/old.jpg[/img]


Now, instead of using the normal directory structure, just upload the full structure to the “contrib” folder. Like this:

http://www.unbannable.com/new_contrib_override.jpg[/img]


That’s it! The contribs will still behave normally and OpenCart will have no problem interfacing with the files.

Just can't let it go, can you. 

NEVER! 
My genius just evolves!

You build it, they will come.

How about something like this, to better take into account multiple contributions:

First. I like that blue folder tree:)

Second. It is a good idea to keep them all separate, but where are those folder titles defined at? Adds another level of definition.

Third. The simple way also allows for multiple contribs.

Fourth. The simple way and even your way still have the problem of 2 contribs changing the same file (exluding the admin menu, just talking controller files, etc).

There is still just no good way to run 2 files of the same kind without merging their contents on the fly, unless each line is it's own include file.

product.php would remove all functional code, then create a product subfolder and have only a recursive file loop:
        And in the controller/product folder would be:
- name.inc
- price.inc
- options.inc
- addtocart.inc
etc.

Then each contrib could modify the individual pieces that they changed, without hogging the whole file.