While this sounds like a good solution to this specific use case, and
while I agree that js-ctypes is horribly fragile, I'm not certain that
this solution can be generalized to AMO-released add-ons that need
access to OS-specific features, since we don't really like add-ons that
ship native code.
On 8/28/2015 10:25 AM, Tony wrote:
Our product makes use of a 3rd party medical device that requires a C library
for usage. We created a NPAPI plugin that wraps this C library so we can
access the device from JavaScript.
Here's where the lawyers get involved...
The medical device, **includ
On 2015-08-28 10:25 AM, Tony wrote:
Our product makes use of a 3rd party medical device that requires a C library
for usage. We created a NPAPI plugin that wraps this C library so we can
access the device from JavaScript.
Have you considered creating an extension that calls into the C librar
Our product makes use of a 3rd party medical device that requires a C library
for usage. We created a NPAPI plugin that wraps this C library so we can
access the device from JavaScript.
Here's where the lawyers get involved...
The medical device, **including** the software included with the de
So...may I know if a decision was made?
element is marked as deprecated on MDN, and as stated by rsleevi,
Chrome seems will drop it.
Will Mozilla do the same? Do you have a roadmap/date for such change? It's
going to be supported "by now" until next call?
Please, consider we are *that little per
5 matches
Mail list logo
