Right now we have this manifest key for plugins: "plugins": [ {"path":
"path/to/file", "public": true}
]
This won't work well for cross platform extensions. Here's a simple addition
to address that:
"plugins": [
{
"platform_paths": [
{"winxp": "plug_xp.dll"}, {"winvista": "plug_vista.dll"}, {"linux":
"libplug_linux.so"}, {"osx": "libplug_osx.so"}
],
"public": false,
"path": "fallback/path/here"
}
]Note: the idea of keeping support for the "path" key is mostly for backwards compatibility. If the plugin is loaded on an OS that isn't present in the "platform_paths" key, we can fall back to the plugin in "path". Obviously it'll fail to load on the wrong platform (hopefully gracefully). Question: What platforms will we need to specify for different plugin versions? Do we need to distinguish between XP/Vista/7? Any other feedback? --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
