{"json_modified": "2016-03-28T08:13:05.863240", "uuid": "e9356bf3-d07c-472f-ba95-153431543a92", "title": "Obsolete: XPCOM-based scripting for NPAPI plugins", "url": "/en-US/docs/Archive/XPCOM-based_scripting_for_NPAPI_plugins", "tags": [], "translations": [], "modified": "2015-10-07T16:48:38", "label": "Obsolete: XPCOM-based scripting for NPAPI plugins", "localization_tags": [], "locale": "en-US", "id": 14309, "last_edit": "2010-02-21T16:56:21", "summary": "Plugins that used to take advantage of being scriptable via LiveConnect in 4.x Netscape browsers lost this possibility in the new world. The main reason for this is that there is no guarantee of Java compatibility on a binary level due to the jri/jni switch. The new Mozilla XPCOM architecture allows XPCOM components be scriptable via a different mechanism called XPConnect. We leverage some of these ideas to help you make your Netscape Communicator 4.x plugins exposed to JavaScript in Mozilla based browsers.", "sections": [{"id": "Introduction", "title": "Introduction"}, {"id": "What.27s_in_the_Mozilla_code.3F", "title": "What's in the Mozilla code?"}, {"id": "What.27s_in_the_plugin_code.3F", "title": "What's in the plugin code?"}, {"id": "How_to_call_plugin_native_methods", "title": "How to call plugin native methods"}, {"id": "How_to_build_and_install", "title": "How to build and install"}, {"id": "Related_sources", "title": "Related sources"}, {"id": "Examples", "title": "Examples"}, {"id": "Example_1._Sample_.idl_file", "title": "Example 1. Sample "}, {"id": "Example_2._Scriptable_instance_class", "title": "Example 2. Scriptable instance class"}, {"id": "Example_3._NPP_GetValue_implementation_and_possible_scenario_of_scriptable_object_life_cycle", "title": "Example 3. NPP_GetValue implementation and possible scenario of scriptable object life cycle"}, {"id": "Original_Document_Information", "title": "Original Document Information"}], "slug": "Archive/XPCOM-based_scripting_for_NPAPI_plugins", "review_tags": []}