cascading resource loading

[JAAulde]

FOR ALL RESOURCES EXCEPT CONFIGS: Can be placed anywhere in the search path. Loader scans UP the search path and includes the first match it comes to causing the most ‘localized’ to take precedence. (this is what is currently being done for everything except controllers and the 2 previously mentioned config files)

FOR ALL CONFIGS: Can be placed anywhere in the search path. Loader scans DOWN the search path and includes ALL matches it comes to. This means that more generic (default) configs can be stored higher in the search path, while those more localized will load up and override with more specific data if necessary.

[JAAulde]

Branch created for this large enhancement: http://www.ciforge.com/trac/blueflame/browser/branches/modLoader

[JAAulde]

Branch removed until everything settles down and all rebranding and licensing is done for Johana

[JAAulde]

r303 and r304 contain modLoader as existed in the CI version documented here: http://codeigniter.com/forums/viewthread/49157/P15/#248449

More to come for handling controllers and such.

[JAAulde]

r306 holds the changes for allowing controllers to be globally searchable and up to one dir deep in controllers/

[Shadowhand]

As of r419, Kohana fully supports the functionality of modLoader, plus allowing controllers to be stored at any depth.