Does it *require* Mozilla? Because if it does, it should disable itself under browsers it's not designed for (if it's not compatible with Safari, it will simply cause interference).
the plugin does not require mozilla, it's called that way because it supports the mozilla plugin architecture and Safari supports plugins designed for mozilla.
I loaded it onto my test Mac, opened up Safari (Firefox not installed on my freshly imaged test Mac) and it says it's installed. Only problem is that QuickTime tends to register itself for every MIME type that the VLC plug-in supports, even if it can't handle all the codecs used.
This problem is not specific to MacOS X, it is a limitation of the plugin design, when 2 plugins supports the same mime type, the browser has to choose one, typically Safari will always prefer Quicktime over any other plugin (guess why !) where firefox would use either.
Not sure how to get VLC to handle certain media instead of QuickTime. Removing the QT plugins would be one way, but that would mean losing support for all the other things that QT registers but VLC doesn't (eg: audio/aac, video/flc...).
VLC has its own unique mime type: application/x-vlc-plugin, if you configure your web server to returns this mime type for all multimedia files, the Safari will choose VLC over QuickTime.
alternatively, in your HML pages you can use the OBJECT tag (instead of EMBED) as per following example:
Code: Select all
<OBJECT DATA="mymovie.avi" TYPE="application/x-vlc-plugin" TITLE="My Movie" WIDTH=200 HEIGHT=100>
I did disable my QT browser plug-ins and threw a couple of files at it, and wound up with differing results. Depending on the file type, mostly Safari either caused a window to open up in the Finder, showing where the file was (Safari acting as if it had "downloaded" the file rather than handling it internally), or a black browser window with "(no picture)" in it.
the back window with the "(no picture)" means that the plugin was loaded by safari but for some reason, the plugin is enable to retrieve the multimedia data
Which all leads me to believe that it is probably Mozilla-only?? So, yeah, disabling itself under other browsers like Safari would be a good idea.
the plugin was coded for Safari actually, it works with firefox as well (but not as well, more testing is required)