Hello, On Mon, Nov 3, 2008 at 2:51 AM, rFobic <[EMAIL PROTECTED]> wrote: > IDEA that came up to my mind is: > - It might be a great idea to implement some way for plugging XPCOMs > into gears as addons or something similar to be used from the browser > - Maybe having some kind of repositories of XPCOMS that can be > specified to gears for not making it too heavy > - Site can request permission from user to use some of the XPCOM's > the way it request now but with little more details. > - For avoiding the security issues it might be god idea to make site > specific XPCOMS > Example: it can be some member constant member in the idl > specifying to the domains that current component can be used for. > - For the developers on both sides gears or xulrunner will be really > easy to work jump into this model
It is already possible to extend web apps with custom native code today, using regular plugins like Flash or QuickTime. The standard interface, NPAPI works well across all browsers except (gar!) IE. If you wanted to go further, you could use Gears itself as a template to create cross-browser plugins. We have a system internally in Gears that abstracts away the differences between IE and other browser's plugins, and it could be used to create a cross-browser plugin system. As for Gears itself, we don't plan on adding the ability to dynamically load native sub-plugins anytime soon. The security issues are pretty scary and supporting third-party code is not high on our priority list. Thanks, - a
