Re: Use-case for consideration, which will be difficult post-NPAPI
Have you considered using a local web server? That way you can use any native code you want, and it's a reasonably common approach. On many platforms you can even use socket activation to avoid the need for a always running server process. On 25 June 2015 at 21:04, Alex Taylor alex.tay...@referencepoint.co.uk wrote: Good morning. I have a use-case which will be difficult to reproduce in the post-NPAPI world: The use-case is a Java/NPAPI applet which uses the javax.smartcardio library to communicate with USB-connected contactless smartcard readers, from a web-page. Extremely useful functionality for our customers. Currently the applet will work in Firefox, Chrome and IE. With the deprecation of NPAPI, we are looking into ways to continue offering that functionality, and need to continue to target all three of those browsers if possible. For Chrome, I have looked into re-implementing the Java applet as a Chrome App, or using NaCl/PPAPI etc. I have not found any equivalent technology for Firefox as yet. Chrome Apps can connect to USB ports via the chrome.usb API, but there is currently no implementation of PC/SC for it (the smartcard access specifications that javax.smartcardio is also built on). Due to time constraints, re-implementing PC/SC ourselves is an option we would only choose as a last resort. In any case, that would only solve the problem for Chrome, not Firefox. Unfortunately, no technology I have looked into so far to solve this problem is able to offer the cross-browser support that Java/NPAPI enjoyed, and has an available PC/SC library. I flag this use-case for consideration in a future web-platform. I am sure we are not the only company who have combined smartcard io functionality with the web, and wish to continue doing so. If anyone knows of any technology or open-source project which might be useful for this situation, please let me know. Alex Taylor | Lead Developer [logo-291px] T: +44 (0)1753 27 99 27tel:+441753279927 | DD: +44 (0)1753 378 144tel: +441753378144 E: alex.tay...@referencepoint.co.ukmailto: alex.tay...@referencepoint.co.uk | Lync: alex.tay...@referencepoint.co.uk sip:alex.tay...@referencepoint.co.uk W: www.referencepoint.co.ukhttp://www.referencepoint.co.uk/ A: Reference Point Limited, Technology House, 2-4 High Street, Chalfont St. Peter, Gerrards Cross, SL9 9QA Right People. Right Skills. Right Place. Right Time. Registered in England No. 02156356 ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Use-case for consideration, which will be difficult post-NPAPI
Good morning. I have a use-case which will be difficult to reproduce in the post-NPAPI world: The use-case is a Java/NPAPI applet which uses the javax.smartcardio library to communicate with USB-connected contactless smartcard readers, from a web-page. Extremely useful functionality for our customers. Currently the applet will work in Firefox, Chrome and IE. With the deprecation of NPAPI, we are looking into ways to continue offering that functionality, and need to continue to target all three of those browsers if possible. For Chrome, I have looked into re-implementing the Java applet as a Chrome App, or using NaCl/PPAPI etc. I have not found any equivalent technology for Firefox as yet. Chrome Apps can connect to USB ports via the chrome.usb API, but there is currently no implementation of PC/SC for it (the smartcard access specifications that javax.smartcardio is also built on). Due to time constraints, re-implementing PC/SC ourselves is an option we would only choose as a last resort. In any case, that would only solve the problem for Chrome, not Firefox. Unfortunately, no technology I have looked into so far to solve this problem is able to offer the cross-browser support that Java/NPAPI enjoyed, and has an available PC/SC library. I flag this use-case for consideration in a future web-platform. I am sure we are not the only company who have combined smartcard io functionality with the web, and wish to continue doing so. If anyone knows of any technology or open-source project which might be useful for this situation, please let me know. Alex Taylor | Lead Developer [logo-291px] T: +44 (0)1753 27 99 27tel:+441753279927 | DD: +44 (0)1753 378 144tel:+441753378144 E: alex.tay...@referencepoint.co.ukmailto:alex.tay...@referencepoint.co.uk | Lync: alex.tay...@referencepoint.co.uksip:alex.tay...@referencepoint.co.uk W: www.referencepoint.co.ukhttp://www.referencepoint.co.uk/ A: Reference Point Limited, Technology House, 2-4 High Street, Chalfont St. Peter, Gerrards Cross, SL9 9QA Right People. Right Skills. Right Place. Right Time. Registered in England No. 02156356 ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: [feature] open certain domains into a private window
On 2015-06-24 4:27 PM, Nicholas Alexander wrote: This would be valuable, I think. We have a (new) flag for opening all links in PB mode; this should work with that. Worth filing a ticket (if there is not yet one). Nick Filed bug 1177472. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Linked Data and a new Browser API event
To follow up on this, there is resistance against implementing the more complex Microdata or RDFa specifications in Gecko. We definitely now need some form of Linked Data support for Firefox OS 2.5 so I'm suggesting the following: We should support Open Graph (because of its wide usage by existing web content) and JSON-LD (because it supports Gaia's more complex use cases). Both of these should be simple to implement in Gecko as events on the Browser API, without requiring any complex parsing on the Gecko side. Open Graph just requires firing metachange events (see bug 962626 for an example) for all meta tags which specify a property attribute. (This would be a crude subset of RDFa. We don't need to specify particular vocabularies in Gecko, just include the value of the property attribute in the payload of the event). meta property=og:title content=The Rock / JSON-LD just requires firing a new linkeddatachange event whenever a JSON-LD script tag is encountered, sending the contents of the script tag in the payload of the event. script type=application/ld+json We can then easily parse the JSON in Gaia and even directly store it directly in our Places database. If there's resistance against implementing the more complex Microdata and RDFa specifications in Gecko then I don't think we should implement Microformats either, the data I have and our experience through prototyping just don't justify it. Unless there's a really good reason not to do so, I'm going to file the bugs and look towards getting this implemented on the Browser API as soon as possible. Thanks Ben On 4 June 2015 at 10:19, Benjamin Francis bfran...@mozilla.com wrote: On 3 June 2015 at 19:42, Benjamin Francis bfran...@mozilla.com wrote: This is what I'd really like to get more of, particularly usage data. I've reached out to a few people at Yahoo, Google and a couple of universities and have managed to turn up a few studies with useful data [1][2][3][4]. My conclusions so far are: - Microformats are used on a large number of web sites but are limited by their case by case syntax and more fixed vocabulary and are less formally defined. - Microdata and RDFa are vocabulary agnostic which makes them inherently more extensible, they're increasing in popularity due to schema.org and consumption by major search engines, whilst the use of Microformats has remained relatively constant over time. - Microdata is a bit more concise than RDFa but doesn't allow for the mixing of vocabularies. - Open Graph is a simplistic form of RDFa with a limited vocabularly and limited usefulness in comparison to other formats, but is very widely used due to Facebook and Twitter being major consumers. - Microformats is used by more websites (domains) but Microdata is used by more web pages (more URLs, more typed entities and more triples) and is growing the fastest. Microformats has the breadth, but Microdata has the depth. In our case I think what we care about is the latter - the amount of pinnable content. - JSON-LD is the newest format, the main difference being that it isn't intended to be embedded in with HTML markup, but is included separately in a script tag. It's also useful as a canonical JSON-based format to represent all of the other formats. That leads me to recommend that we do the following: - Parse Microdata and RDFa (including Open Graph) from web pages in Gecko - Expose all of this data to Gaia via a single getLinkedData() or getStructuredData() method on the Browser API which returns a Promise that resolves with the data in a canonical JSON-LD format - Also consider supporting JSON-LD directly as no parsing is required, we just need to detect a script tag If anyone finds any more usage data, or has a different interpretation of the data below, then please do share. Thanks Ben 1. Web Data Commons website based on Common Crawl corpus (2009-2014) http://webdatacommons.org/ 2. Web Data Commons Paper based on Common Crawl Corpus (2009-2012) http://events.linkeddata.org/ldow2012/papers/ldow2012-inv-paper-2.pdf 3. Yahoo post based on Yahoo corpus (2011) https://tripletalk.wordpress.com/2011/01/25/rdfa-deployment-across-the-web/ 4. Yahoo paper based on Bing corpus (2012) http://events.linkeddata.org/ldow2012/papers/ldow2012-inv-paper-1.pdf ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Help with building Xulrunner windows 64 bit.
On Friday, June 19, 2015 at 10:31:34 AM UTC+5:30, Abhay Kumar Somani wrote: On Wednesday, June 17, 2015 at 10:29:24 PM UTC+5:30, Adrian Kalla wrote: W dniu 06/17/2015 o 06:33 PM, Abhay Kumar Somani pisze: Hi, I am working in a company and we are using XULRunner to deploy our app. Now we have decided to upgrade our app to 64bit. While upgrading we got to know that Mozilla doesn't provides 64bitXULRunner for windows. However, while searching in the net, I found a website that provides 64bit binaries for windows but it is unofficial, and no source code is available there, so don't know whether it is safe to consume them as per our security concerns. So, if anybody could help me with building a 64bit XULRunner for windows or if Mozilla team plan to provide 64bit Windows build anytime soon, it will of great help. Otherwise if someone can kindly help with building 64bit binaries. Thanks in advance. Hi, building XULRunner is not different from building Firefox. When already deploying an own app, I expect you know the basics of how to compile an application ;) You should start with this three links: https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Windows_Prerequisites https://developer.mozilla.org/en-US/docs/Simple_Firefox_build https://developer.mozilla.org/en-US/docs/Configuring_Build_Options There also are official Win64 builds, but only for central, aurora and the beta stage, e.g.: https://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/latest-beta/runtimes/xulrunner-39.0b6.en-US.win64.zip Best regards FYI: I'm not sure if you are aware of this, but XULRunner is in the process of a slow and painful death, as no-one seems to care about it anymore. So I'm not so sure, if it is a good idea to depend on it... Thanks Adrian for your help. And also thanks for the information about XULRunner in the process of end, I didn't knew that. Hi, I used the beta build but I am stuck at a point in windows. Whenever my application tries to open a new window or a popup, I get the login page in the popup and the previous Xulrunner session gets closed. I am not getting it, whether it is a problem related to session management or popup related. Everything works well for linux. It is only in windows where I am getting this issue. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
