Maybe we should consider splitting the configuration system into a seperate library though. It would suck if Windows users could not use Jabo's Direct3D plugin. Its nice to try to unify the plugins and such, but you're probably better off creating extensions to the link level API in this case if you want to keep into consideration 3rd party plugins. Yes, we may have breaken the link level compatibility. Is it impossible to fix? Impossible to provide a loader for standard plugin? I think its worth mentioning that unifying the plugin's configuration systems does not necessarily have to be specific to the core, and even if so, we don't necessarily need to completely ruin support for other plugins.
The unified GUI API idea isn't too hard if we abstract at a high enough level and there are many other ways to provide support for multiple GUI libraries, probably better.
The unified GUI API idea isn't too hard if we abstract at a high enough level and there are many other ways to provide support for multiple GUI libraries, probably better.