Re: Java plugin phase out timeline

hi Fábio, an alternative to js-ctypes is to create a Firefox extension 
that communicates with a child process written in native code that calls 
your DLL. The Addon SDK's system/child_process API allows pipe-based 
communication with an external binary:

https://developer.mozilla.org/en-US/Add-ons/SDK/Low-Level_APIs/system_child_process 



chris


On 2/24/16 9:25 AM, Mikael Haltali wrote:
> Hi,
> the best solution currently is js-ctypes which enables you to build an
> extension that calls a custom dll written in C
> That's what my team is currently doing to migrate a NPAPI plugin.
> Documentation is good but the only drawback currently is the lack of end to
> end examples.
> Here is a link to official documentation
> https://developer.mozilla.org/en-US/docs/Mozilla/js-ctypes
>
> Hope this helps
>
> On Wed, Feb 24, 2016 at 2:30 PM, <[email protected]> wrote:
>
>> Hello, I have some use cases, which currently are "solved" with Java
>> Applets:
>>
>> 1 - Control a Twain scanner. (kodak scanner i2800)
>> 2 - Control a fingerprint reader (Nitgen Fingkey Hamster I DX).
>> 3 - Control a barcode reader.
>>
>> All of these involve access dll's (or .so ) via JNI.
>>
>>
>> What technology Firefox provides so I can migrate and continue to
>> access/control hardware as i can now via dll's + JNI + Java Applets?
>>
>>
>>
>>
>> --
>> Fábio C. Barrionuevo da Luz
>> Palmas - Tocantins - Brasil - América do Sul
>>
>>
>> Em terça-feira, 23 de fevereiro de 2016 15:35:46 UTC-3, Chris Peterson
>> escreveu:
>>> On 2/23/16 10:03 AM, Java Dev wrote:
>>>> Hope all is well. The company I work for uses Java applets for our web
>> products and we are currently planning our release schedules to replace
>> Java applet tech, as it will affect many users in our product community and
>> several products. As such, our dev team would like to better understand the
>> "drop dead date" of when the Java plugin will stop working in Firefox.
>>>>
>>>> We are aware that the announcement was for end of 2016, but wanted to
>> confirm if there is a more specific date other than 12/31/2016. Also, we
>> would like to know if Firefox will follow a similar path as Chrome to
>> provide a way to still manually enable the Java plugin for some time
>> (disabled by default), perhaps even past end of 2016.
>>>
>>>
>>> hi Alexandra, our tentative schedule is to remove NPAPI support in
>>> Firefox 53 (which will be in the Firefox Nightly channel in November
>>> 2016 and released in April 2017). These versions or dates are not
>>> official or set in stone. They could conceivably be postponed if we need
>>> to continue supporting NPAPI for some reason.
>>>
>>> The next Firefox ESR (Extended Support Release) version is 52 and will
>>> receive security updates for a year. By removing NPAPI in Firefox 53,
>>> the release *after* the ESR, users that need NPAPI support can continue
>>> to switch to Firefox ESR 52 and keep using NPAPI plugins until May 2018.
>>>
>>>
>>> chris
>> _______________________________________________
>> dev-tech-plugins mailing list
>> [email protected]
>> https://lists.mozilla.org/listinfo/dev-tech-plugins
>>

_______________________________________________
dev-tech-plugins mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-plugins