Mockup

http://static3.filefront.com/images/personal/l/lordspidey/78836/edmwulrptz.jpg

sorry about the small size of the text and all im working on the eee :)

anyways the mockup speaks for itself the idea is pretty much to have a ui for looking at files and folders in vo

An addition to this I think it would be really cool for vendetta to associate to filestypes like ".vop" ".vos" for skins and plugins

all it would do is that when people finish a plugin they change the file extension to .vop then when a user click on that file vo will extract it to the appropriate folder and put the plugin name and info under the [plugins] take with a little checkbox to unload the plugin, same goes for skins.

on a semi related note could the devs add a command or an option to reload only the skin files without having to reload all the textures?

no comment?

If we had access to the filesystem it could be done as a community plugin.

Unfortunately, we don't, and it doesn't look like we will anytime soon, so it isn't going to be possible in such a fashion. Best you can really do is just change the gkini string, but then you depend on the user knowing exactly what the names of skins/plugins that are available.

made these for the file association idea

http://static3.filefront.com/images/personal/l/lordspidey/78836/ebgioigvdx.jpg

http://static3.filefront.com/images/personal/l/lordspidey/78836/yinoymirlr.jpg

Hmm, I think I found a way to make it possible.

O_o

It requires an external app right?

It requires integration with each OS to varying extents. For *nix, that might not be so hard, due to it's open source nature.

No, I was more thinking about registering plugins with some kind of master plugin:

local plugin = vupa.New('vupa_example_plugin')
if plugin.disabled then return nil end

if plugin.disabled is set to true, it would completely disable the execution of the code after that line. It would still require the plugins to be put in the plugins folder, but it allows disabling them individually from one place.