Plugins should have dependencies
Brought to you by:
chris_a_thomas
Menu
▾
▴
#4 Plugins should have dependencies
certain plugins require other plugins to work,
VFSPlugin_Q3BSP requires that VFSPlugin_TGA and JPEG
are available in order to load textures from the disk
and apply them to polygons.
so you can't use Q3BSP without TGA and JPEG already loaded.
the current solution is to search for the plugins in
the VFS system and fail if they are not located.
the problem with this, is that it makes the order in
which the plugins are included in the configuration
file, the master of whether a plugin will load or not.
a better system would be this
a plugin attempts to load, looks for it's dependencies,
can't find them, attempts to load them, if successful,
loads itself, otherwise, THEN fails.
so the system will attempt to automatically configure
plugins, so then the order in which they are declared
inside the configuration file is irrelevant to whether
a plugin will load or not.
Logged In: YES
user_id=682144
I have started work on this bug, basically I've removed any
code from a VFSPlugin dll which isnt actually part of the
plugin, and I've moved some code in VirtualFS object, the
Find{Plugin/Transport/Filter} functions in order to search
for a plugin.
the status up to now, is that the plugin will search for
it's dependencies when it attempts to load, if it finds
them, it'll construct the plugin, otherwise, it will fail
the best solution of course, is to load the plugins it
requires when it attempts to look for them, but the problem
with this, is how do you know what the plugin is called and
where it's located?