Closed Bug 145274 Opened 23 years ago Closed 12 years ago

[RFE] Allow plugin XPT to live inside OSX bundle

Categories

(Core Graveyard :: Plug-ins, enhancement, P3)

PowerPC
macOS
enhancement

Tracking

(Not tracked)

RESOLVED WONTFIX
Future

People

(Reporter: peterlubczynski-bugs, Assigned: peterl-bugs)

References

Details

(Keywords: topembed-, Whiteboard: [PL2:P3])

On OSX, some plugins are in a packaged bundle which is really just a set of directories made to appear in the Finder as a single file. Quicktime is an example. If you right click to 'show contents', you'll notice many subdirectories. Since plugins need an XPT file for scripting support, it would be nice if this file could live inside the plugin bundle. This would allow for easier installation of 'scriptable' plugins and reduce the likelyhood that the XPT file would be not found. ------------------------------------------ So xpt does support multiple directories as this is being done with the plugins directory service provider list: http://lxr.mozilla.org/mozilla/source/xpcom/reflect/xptinfo/src/xptiInterfaceInfoManager.cpp#247 We could possibly change our plugin logic that if we see a special directory for XPT in the plugin bundle while looking for the plugin, we add this to the NS_APP_PLUGINS_DIR_LIST and ask the component manager to ->AutoRegister() (again)? Thoughts?
This is a _great_ idea from my perspective, it makes our installation much much simpler. If you can decide on the name and location of the directory within the bundle REALLY, REALLY quickly I might be able to get it into the next version of QuickTime.
Another possible idea (maybe more cross-platform) is to create a new NPN_SetValue variable to allow the plugin to dynmically specify the path of its XPT file during initilization.
This is a nice feature we'd like to implement in the future.
Priority: -- → P3
Whiteboard: [PL2:P3]
Target Milestone: --- → mozilla1.2beta
Keywords: topembed
Target Milestone: mozilla1.2beta → mozilla1.3alpha
[RFE] is deprecated in favor of severity: enhancement. They have the same meaning.
Severity: normal → enhancement
Keywords: topembedtopembed+
Blocks: grouper
This is dependent upon being able to scan arbitrary xpt files. We must first discuss the scanning issue with jband and work through functional issues. Marking as topembed-
Keywords: topembed+topembed-
Target Milestone: mozilla1.3alpha → Future
Depends on: 184506
QA Contact: shrir → plugins
XPCOM plugins/XPT support is gone.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.