[b2g] (no subject)

dear all, i wanted to know the amount of porting that is required to port android kernel to b2g specific changes that need to be done in kernel for b2g files that need to be changed , thanks ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://l

Re: [b2g] [Port] Firefox os to Samsung Galaxy tab 10.1

On Monday, January 14, 2013 9:10:32 PM UTC-7, Gioyik wrote: > Yes it's a problem of the manifest because in the mozilla-b2g/b2g-manifest > > repo there's not a manifest file with that name, i have some work ready for > > the Port of FirefoxOS for this device. Would you like work with me testing >

Re: [b2g] [Port] Firefox os to Samsung Galaxy tab 10.1

Yes it's a problem of the manifest because in the mozilla-b2g/b2g-manifest repo there's not a manifest file with that name, i have some work ready for the Port of FirefoxOS for this device. Would you like work with me testing my sources? It's better that you work on it building this new Port becaus

[b2g] [Port] Firefox os to Samsung Galaxy tab 10.1

Hello, I'm working on porting Firefox os/B2G to the galaxy tab. I have assembled my device configuration tree and edited the necessary files (e.g. config.sh, init.rc, manifest.xml, etc) I have been having trouble when trying to run the ./build.sh command though. Take a look: [CODE]~/B2G$ ./conf

[b2g] 01-14-2013 Unagi Smoke Test Results - 41 passed, 3 failed, 1 partial, 3 blockers

41 out of 45 tests passed for the 1/14/2013 build. Here are the major issues that prevented the smoke tests from passing: - Smoketest: https://docs.google.com/spreadsheet/ccc?key=0AqDJxnTd7VDLdDRKOE1uanE3M3FtMDBOVjRIV253S1E#gid=65 Tests were performed with: - gecko: 5a367713bfa4 - gaia: 45a31

[b2g] Tackling and blocking post-basecamp

Quick guide on how to nominate and prioritize work for the post-basecamp milestone. =Milestones= We have successfully completed the basecamp milestone thanks to some heroic efforts last week, yay for all! Please do not use the blocking-basecamp flag anymore, unless you are still working on an

[b2g] Latest Flags and Landing, explained

Below are a few notes on flags, for all of those interested. Queries can be found at https://wiki.mozilla.org/B2G/Triage#Joint_Triage_Queries. * blocking-basecamp will be deprecated as soon as possible - https://bugzilla.mozilla.org/show_bug.cgi?id=830433 * blocking-b2g:tef? is for CRITICAL bug

Re: [b2g] Debugging apps on B2G

2013/1/14 Jim Blandy > Your argument about developer time and clients' willingness to pay is a > strong one. I worked as a contractor for a while. Before I started, I > was looking forward to spending time building tools that would help make > me really effective. But once I'd begun, and was nego

Re: [b2g] Debugging apps on B2G

On Mon, Jan 14, 2013 at 10:29 AM, Jeremie Patonnier wr > I think the concern is a bit different than that. An interoperable protocole > will allow web developers to use third party tools that will allow them to > debug both Chrome and Firefox (and any browser that will implement it) at > the same

Re: [b2g] Debugging apps on B2G

Hi, 2013/1/14 Rob Campbell > If interoperability ever does become a concern (we want to debug chrome > through the Firefox debugger for example), I think the concern is a bit different than that. An interoperable protocole will allow web developers to use third party tools that will allow the

Re: [b2g] Debugging apps on B2G

Your argument about developer time and clients' willingness to pay is a strong one. I worked as a contractor for a while. Before I started, I was looking forward to spending time building tools that would help make me really effective. But once I'd begun, and was negotiating contracts and rates, I

Re: [b2g] Debugging apps on B2G

Hi 2013/1/14 Jim Blandy > Obviously, there's no reason we couldn't implement the WebKit/chrome > protocol - it works for them, so it must also work as well for us. > > However, our protocol has some nice characteristics. It's easy to > extend and specialize for other kinds of tools and instrumen

Re: [b2g] Debugging apps on B2G

Hi Jim, I was talking with Panos about this as well this morning. If interoperability ever does become a concern (we want to debug chrome through the Firefox debugger for example), we could probably implement a protocol translation layer to talk to a foreign browser / debugger server. That way

Re: [b2g] Debugging apps on B2G

Obviously, there's no reason we couldn't implement the WebKit/chrome protocol - it works for them, so it must also work as well for us. However, our protocol has some nice characteristics. It's easy to extend and specialize for other kinds of tools and instrumentation, like the profiler, or to pro

Re: [b2g] [Port]Firefox OS/B2G on Samsung Galaxy S3

Hi, Now, i uploaded the manifest files for those devices: i9300 p500 pyramid tass msm7x27-common Someone can test it, and tell what works and what not? I only have a Samsung Galaxy S3 for test, i am planning post this on XDA Developers, to get people involved in the Testing of this and others Po

Re: [b2g] 1/14/2012 Unagi Smoke Test Results - 36 passed, 5 failed, 3 partial

Thanks for the explanation Jason. It is clearer now. Regards, Isabel -Mensaje original- De: dev-gaia-bounces+isabelrios=aurigae@lists.mozilla.org [mailto:dev-gaia-bounces+isabelrios=aurigae@lists.mozilla.org] En nombre de Jason Smith Enviado el: lunes, 14 de enero de 2013 14:27 Pa

Re: [b2g] Debugging apps on B2G

Hi, 2013/1/14 Panos Astithas > This is getting off-topic, so if you want to talk about this further, > let's continue the discussion in the dev-developer-tools mailing list. > Agreed, feel free to remove the B2G/Gaia ML if it's to noisy :) > In a nutshell, we originally considered using WebKi

[b2g] Firefox webapp file input

Hey guys, Can someone help me with this question: http://stackoverflow.com/q/14187259/1107651 The answer provide , says this is only possible with privileged apps, this is true? If so, when privileged apps will be available for firefox-android ? Another question is about device-storage-api ,

Re: [b2g] 1/14/2012 Unagi Smoke Test Results - 36 passed, 5 failed, 3 partial

The packaged app test case there won't work, but that's expected, as by default, you can only install signed packaged apps from a trusted store. So bug 830279 is invalid. bug 830028 is not a smoketest blocker - it's actually minor, as that only applies when the app is being downloaded or never

[b2g] 1/14/2012 Unagi Smoke Test Results - 36 passed, 5 failed, 3 partial

Hi All, 36 out of 45 tests passed for the 1/14/2013 build. 5 failed, 3 partial and 1 untested - Smoketest: https://docs.google.com/spreadsheet/ccc?key=0AqDJxnTd7VDLdDRKOE1uanE3M3FtMDB OVjRI

Re: [b2g] Debugging apps on B2G

This is getting off-topic, so if you want to talk about this further, let's continue the discussion in the dev-developer-tools mailing list. In a nutshell, we originally considered using WebKit's protocol, but it proved too limiting in some ways. Jim can provide the details here. There is no such