Allowing users to cancel the add-on compatibility check for Firefox updates

2014-02-09 Thread Irving Reid
In the early days of rapid release, we switched the default behaviour of (some) add-ons from strict compatibility checks against Firefox (and other toolkit-using application) versions, to compatible-by-default. This was to make life easier for add-on authors and users. We were worried that we

C++ Standards Committee meeting in Issaquah

2014-02-09 Thread Botond Ballo
Hi everyone, I mentioned already [1] that I will be at the upcoming C++ Standards Committee in Issaquah, Washington (near Seattle) next week. I thought I'd mention it again in a new thread to make sure people who might be interested don't miss it. See this thread [2] for my report on the last Com

Cairo being considered as the basis of a standard C++ drawing API

2014-02-09 Thread Botond Ballo
The C++ Standards Committee is aiming to standardize a 2D drawing API in the post-C++14 timeframe. A study group (SG 13 - Graphics [1]) has been created to investigate possible approaches. SG 13 is considering using Cairo as the basis for a lightweight C++ drawing API [2] [3]. The idea would b

Re: Cairo being considered as the basis of a standard C++ drawing API

2014-02-09 Thread Andreas Gal
It seems to me that we have arrived at the conclusion that a good drawing API should be mostly stateless (like Moz2D), instead of Cairo's stateful API. As a result we are currently removing all uses of the Cairo API and we will eventually remove Cairo from our codebase altogether (in favor of D

Re: DXR UI refresh is live!

2014-02-09 Thread Edwin Flores
On 08/02/14 10:26, Erik Rose wrote: > https://blog.mozilla.org/webdev/2014/02/07/dxr-gets-a-huge-ui-refresh/ > > Happy hacking! Looks awesome! But... (there's always a but) I notice the "click here to view all search results" link is at the top of the code listing now, instead of being with the

Re: Cairo being considered as the basis of a standard C++ drawing API

2014-02-09 Thread Robert O'Callahan
I've already given my feedback on the cairo mailing list. Summary: Moz2D is the right thing for us, and probably for other application frameworks, but for applications that just want to draw their stuff on the screen or to print, cairo might be a better fit. Anyway ti doesn't really matter to us wh

Re: Cairo being considered as the basis of a standard C++ drawing API

2014-02-09 Thread Brian Smith
On Sun, Feb 9, 2014 at 2:38 PM, Robert O'Callahan wrote: > I've already given my feedback on the cairo mailing list. Summary: Moz2D is > the right thing for us, and probably for other application frameworks, but > for applications that just want to draw their stuff on the screen or to > print, cai

Re: Cairo being considered as the basis of a standard C++ drawing API

2014-02-09 Thread Robert O'Callahan
On Mon, Feb 10, 2014 at 11:49 AM, Brian Smith wrote: > On Sun, Feb 9, 2014 at 2:38 PM, Robert O'Callahan > wrote: > > I've already given my feedback on the cairo mailing list. Summary: Moz2D > is > > the right thing for us, and probably for other application frameworks, > but > > for application

Re: Cairo being considered as the basis of a standard C++ drawing API

2014-02-09 Thread Brian Smith
On Sun, Feb 9, 2014 at 2:54 PM, Robert O'Callahan wrote: > On Mon, Feb 10, 2014 at 11:49 AM, Brian Smith wrote: >> It seems likely that if something like Moz2D became the standard API then >> we'd be able to optimize it more easily than we'd be able to optimize an API >> that worked much differen

Re: Cairo being considered as the basis of a standard C++ drawing API

2014-02-09 Thread Till Schneidereit
On Mon, Feb 10, 2014 at 12:00 PM, Brian Smith wrote: > On Sun, Feb 9, 2014 at 2:54 PM, Robert O'Callahan > wrote: > > On Mon, Feb 10, 2014 at 11:49 AM, Brian Smith > wrote: > >> It seems likely that if something like Moz2D became the standard API > then > >> we'd be able to optimize it more eas

Re: Cairo being considered as the basis of a standard C++ drawing API

2014-02-09 Thread Robert O'Callahan
On Mon, Feb 10, 2014 at 12:00 PM, Brian Smith wrote: > I don't think it is fixed in stone that asm.js code must go through > Web Platform APIs. I believe the requirement is that it must be > possible to translate asm.js code into Web Platform APIs in a way > where the result works reasonably. AFA