| Both sides previous revision Previous revision Next revision | Previous revision |
| andrewpantyukhin:npapi [2006/07/29 11:25] – AndrewPantyukhin | andrewpantyukhin:npapi [2022/10/04 00:51] (current) – Move to personal namespace KubilayKocak |
|---|
| NPAPI infrastructure provides macros for ports that install NPAPI plugins. | NPAPI infrastructure provides macros for ports that install NPAPI plugins. |
| |
| [http://en.wikipedia.org/wiki/NPAPI NPAPI] is a plugin architecture, supported by many browsers. To name a few: Mozilla/Seamonkey, Firefox, Opera and Konqueror. | [[http://en.wikipedia.org/wiki/NPAPI|NPAPI]] is a plugin architecture, supported by many browsers. To name a few: Mozilla/Seamonkey, Firefox, Opera and Konqueror. |
| |
| NPAPI plugins are currently installed in a variety of directories, usually under X11BASE. However, I hereby propose to install all plugins in LOCALBASE/lib/npapi/PKGBASE. We can then employ ["Linkfarming"] to make plugins available to browsers and let users actually tune what plugins to enable in which browsers. Look into www/linux-mplayer-plugin/Makefile.npapi for more info. I hope to convert other ports later. | NPAPI plugins are currently installed in a variety of directories, usually under X11BASE. However, I hereby propose to install all plugins in LOCALBASE/lib/npapi/PKGBASE. We can then employ [[AndrewPantyukhin/Linkfarming|Linkfarming]] to make plugins available to browsers and let users actually tune what plugins to enable in which browsers. Look into www/linux-mplayer-plugin/Makefile.npapi for more info. I hope to convert other ports later. |
| |
| To experience all the benefits of the infrastructure, support must be introduced into both plugin ports (miniports) and application ports (apps): | To experience all the benefits of the infrastructure, support must be introduced into both plugin ports (miniports) and application ports (apps): |
| ==== Miniport installation paths ==== | ==== Miniport installation paths ==== |
| |
| www/mplayer-plugin is installed into lib/npapi/mplayerplug-in/ | www/mplayer-plugin will be installed into lib/npapi/mplayerplug-in/ |
| [[/BR|BR]]Links are then made in lib/npapi/symlinks///browser// for each native browser | \\ Links are then made in lib/npapi/symlinks///browser// for each native browser |
| |
| www/linux-mplayer-plugin is installed into lib/npapi/linux-mplayerplug-in/ | www/linux-mplayer-plugin will be installed into lib/npapi/linux-mplayerplug-in/ |
| [[/BR|BR]]Links are then made in lib/npapi/symlinks///linux-browser// for each linux binary browser | \\ Links are then made in lib/npapi/symlinks///linux-browser// for each linux binary browser |
| |
| Links are also made in browser plugins dirs, like share/opera/plugins/ and lib/firefox/plugins/ | Links are also made in browser plugins dirs, like share/opera/plugins/ and lib/firefox/plugins/ |
| |
| In general, a miniport is installed into lib/npapi/PKGBASE/ by default (last component tunable by NPAPI_ID, the whole path tunable by NPAPI_NPAPIDIR) and links are made for browsers, supported by the plugin. Browser support is defined by miniport maintainers by setting the USE_NPAPI variable to strings like "*", "firefox thunderbird", "*-firefox-devel", "linux-*" and so on. It can be further fine-tuned by users by setting WITH_NPAPI variable. This way we avoid most name clashes (and in a lot better fashion that we currently do). | In general, a miniport is installed into lib/npapi/PKGBASE/ by default (last component tunable by NPAPI_ID, the whole path tunable by NPAPI_NPAPIDIR) and links are made for browsers, supported by the plugin. Browser support is defined by miniport maintainers by setting the USE_NPAPI variable to strings like "*", "firefox thunderbird", "*-firefox-devel", "linux-*" and so on. It can be further fine-tuned by users by setting WITH_NPAPI variable. This way we avoid most name clashes (and in a lot better fashion that we currently do). |
| | |
| | ---- |
| | |
| | {{tag>Ports}} |
| | {{tag>Stale}} |
| |