On 17 March 2016 at 12:18, Benjamin Francis <[email protected]> wrote:
> On 16 March 2016 at 21:56, Aus Lacroix <[email protected]> wrote: > >> - *Are there any guidelines on what's changed and what's necessary to >>> get things working again?* >>> I don’t have a good answer for that. I think the main focus for the >>> transition is removing Packaged apps support, and some of the b2g specific >>> API’s, but that didn’t happen yet, so I’m not why the tests are currently >>> failing :/ >>> >> >> Neither do I honestly. But, what I can tell you is that the only build >> that will work is coming from the Pine branch and that the Kanikani branch >> will have good examples on how to update your application as we'll be >> updating System and Settings. >> > > Not all apps should follow the example of the system app. As we get rid of > app:// our intention is to turn the system apps (all the apps with > role=system and possibly others like Settings) into chrome:// and > everything else into standard http:// web content. You can read more > about that on the wiki <https://wiki.mozilla.org/B2G/Transition_Project>. > > We should try to avoid just turning all of Gaia into chrome, we should > ideally aim to turn most of it into web content. It may be that certain > apps do end up being chrome (e.g. the camera and dialer), but we should > look for alternative solutions where possible. For example. Gabriele has > been investigating whether we can turn the telephony API into a local > RESTful web service outside of Gecko. > +1000 > > For some reason the Contacts API appears to have recently been made > chrome-only (we're not sure why), but ideally we'd come up with a more > webby solution (e.g. a contacts web service backed by IndexedDB) rather > than make the contacts app into chrome. > I think I have some code (maybe not tested 100%), to mock mozcontacts api with indexeddb. Will try to have it working to fix the lack of mozcontacts. Will spend some time tomorrow to revive it! > > Fabrice and Alexandre have come up with a set of patches to get the system > app booting as chrome:// which is our starting point, that's in bug > 1256506 <https://bugzilla.mozilla.org/show_bug.cgi?id=1256506>. Once that > is landed we should be in a better position to get builds up and running > and then start to fix stuff, including figuring out how to port over each > app. Contributions to that effort are very welcome! > > Thanks > > Ben > > > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos > >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
