On 2/19/14 3:31 PM, Adam Roach wrote:
* Unit testing of client code will be performed with the mochi test framework.
The decision I thought I heard was that we were going to go find out more about cross-browser mochitest-ing before a call was made here. Did I misunderstand?
Action Items * L: *Nicolas* to examine use of client libraries (jQuery, Backbone) to determine how much effort we're likely to save versus the effort of ensuring we can run the libraries safely in the context of elevated privileges.
After talking with Kaze about MVC stuff, it sounds like there's no particular convention in B2G apps for this, and each app does, to some extent its own thing. He suggests talking to James Lal (who wrote the B2G calendar, which apparently includes its own hand-rolled framework), and who has lots of regular web experience (maybe including general mobile) with this stuff as well.
* V: *Adam* to research possibilities for running part of the code with chrome privileges and others with content privileges, so as to minimize the exposure to security issues.
Looking at the pdf.js code as possible prior art may be interesting here, though it may not be analogous enough to be worthwhile. See below.
* V: *Dan* to evaluate the use of <template>s for the use of l10n (will all WebRTC browsers have template support?).
I probably didn't communicate this clearly; apologies. I was actually referring to <shadow-dom> stuff, which I'm not even sure is a suitable for what we want. I had a bunch of discussions on with folks today, and have found something that appears suitable at first blush, as it's used in pdf.js (both on desktop and in b2g), as well as for all of b2g. <https://bugzilla.mozilla.org/show_bug.cgi?id=972884> has details.
Dan _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
