Download
Did some more experimentation and you're right - you can simply use the autoloader off of the bat in the pluginname.php file.
This works simultaneously for the front and back-end without the need for any hooks. When adding new classes, there is no longer a need to manage the series of includes lists (wherever they might be).
You've already solved it shawn; one less thing for you to think about :-P
In coding supplementary Matrix plugins, there was an issue on Ubuntu that plugins were loaded in reverse alphabetical order, so the order of the dependencies was completely buggered (e.g. Matrix CUsers initialization would take place before plain Matrix init) though again, I'm not sure if that also comes down to where/when certain plugin hooks were used). Most of that came down to the fact that those dependencies weren't loaded dynamically. This could solve those problems, though.
PHP Code:
function my_autoloader($class) { ... }
spl_autoload_register('my_autoloader');
This works simultaneously for the front and back-end without the need for any hooks. When adding new classes, there is no longer a need to manage the series of includes lists (wherever they might be).
You've already solved it shawn; one less thing for you to think about :-P
Quote:loading a class does not execute anything does it?
In coding supplementary Matrix plugins, there was an issue on Ubuntu that plugins were loaded in reverse alphabetical order, so the order of the dependencies was completely buggered (e.g. Matrix CUsers initialization would take place before plain Matrix init) though again, I'm not sure if that also comes down to where/when certain plugin hooks were used). Most of that came down to the fact that those dependencies weren't loaded dynamically. This could solve those problems, though.
