I believe you tried to assemble an OOP system there, but it looks like you have left all the OO concepts behind. For example, there is no abstractization. Second, every plugin and class you write - including Config?! - (you assumed) it must extend the DingoCore class, which is wrong. I'll give you an example: you want to create a logging "plugin". In that case, you would need to extend the DingoCore class, right? Well, in the case of a logging plugin, you wouldn't need the templates methods and all that stuff in the core class. That's useless overloading, thus longer loading times. Same applies to the config class. You don't need to parse templates or load models or plugins in a config file, do you? I wouldn't go there, anyway, but probably you have a different motivation and config files mean something else to you that they mean to me.

This is just a scratch of the surface, I'll probably be back with more later...

__________________