On Tue, 1 Jul 2008, Philip Taylor wrote:
On 01/07/2008, Ian Hickson i...@hixie.ch wrote:
It seems better for the browser to simply detect when the graphics
burden being placed on the hardware by the page is too much to be done
at high quality given the current load on the CPU, and for
: Vladimir Vukicevic; Robert O'Callahan; WHATWG; David Hyatt; Jerason
Banes; Ian Hickson; Robert O'Callahan
Subject: Re: [whatwg] [canvas] imageRenderingQuality property
So now we need to define levels of graphic burden? and at what level
of burden does the quality suffer? Seems just as hard
;
Jerason
Banes; Ian Hickson; Robert O'Callahan
Subject: Re: [whatwg] [canvas] imageRenderingQuality property
So now we need to define levels of graphic burden? and at what level
of burden does the quality suffer? Seems just as hard to define.
Having the author explicit say this has to be as high
'
Subject: Re: [whatwg] [canvas] imageRenderingQuality property
How can an author know which is appropriate?
Erm, presumably because they're the author -- it seems quite valid
to for an author to be able to say Just make this happen quickly, I
don't care about the quality or Take extra time to make
On Mon, 30 Jun 2008, Vladimir Vukicevic wrote:
On Jun 11, 2008, at 3:34 AM, Ian Hickson wrote:
On Mon, 2 Jun 2008, Vladimir Vukicevic wrote:
I'd like to propose adding an imageRenderingQuality property on the
canvas 2D context to allow authors to choose speed vs. quality when
How can an author know which is appropriate?
Erm, presumably because they're the author -- it seems quite valid
to for an author to be able to say Just make this happen quickly, I
don't care about the quality or Take extra time to make this the
highest quality you can.
No problem, all
On Mon, Jun 30, 2008 at 7:30 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Mon, 30 Jun 2008, Vladimir Vukicevic wrote:
On Jun 11, 2008, at 3:34 AM, Ian Hickson wrote:
On Mon, 2 Jun 2008, Vladimir Vukicevic wrote:
I'd like to propose adding an imageRenderingQuality property on the
On Jun 30, 2008, at 4:14 PM, Vladimir Vukicevic wrote:
On Jun 11, 2008, at 3:34 AM, Ian Hickson wrote:
On Mon, 2 Jun 2008, Vladimir Vukicevic wrote:
I'd like to propose adding an imageRenderingQuality property on the
canvas 2D context to allow authors to choose speed vs. quality when
On 01/07/2008, Ian Hickson [EMAIL PROTECTED] wrote:
[...]
It seems better for the browser to simply detect when the graphics burden
being placed on the hardware by the page is too much to be done at high
quality given the current load on the CPU, and for the browser to
automatically drop
So now we need to define levels of graphic burden? and at what level
of burden does the quality suffer? Seems just as hard to define.
Having the author explicit say this has to be as high quality as
possible or less can be low quality seems better and we have
examples of other specs
On Thu, 12 Jun 2008, Robert O'Callahan wrote:
On Wed, Jun 11, 2008 at 10:34 PM, Ian Hickson [EMAIL PROTECTED] wrote:
Why not just have the UA run in a high quality mode the first time it
is painted on, but if the script tries to paint again within a certain
amount of time, switch to
On Mon, 2 Jun 2008, Vladimir Vukicevic wrote:
I'd like to propose adding an imageRenderingQuality property on the
canvas 2D context to allow authors to choose speed vs. quality when
rendering images (especially transformed ones).
How can an author know which is appropriate?
This is
On Wed, Jun 11, 2008 at 10:34 PM, Ian Hickson [EMAIL PROTECTED] wrote:
Why not just have the UA run in a high quality mode the first time it is
painted on, but if the script tries to paint again within a certain amount
of time, switch to high speed?
This makes sense.
However, there is still
If you don't mind someone weighing in who's been working with the Nintendo
Wii for the past year and a half, I have found that the quality setting in
Flash is tremendously useful. While the march of Moore's law has ensured
that Flash on the desktop is zippy, it has also created a gap whereby
I'd like to propose adding an imageRenderingQuality property on the
canvas 2D context to allow authors to choose speed vs. quality when
rendering images (especially transformed ones). This is modeled on
the SVG image-rendering property, at
Um, could you actually give some kind of reasoning for these? I am
not aware of any significant performance issues in Canvas that cannot
be almost directly attributed to JavaScript itself rather than the
canvas.
--Oliver
On Jun 2, 2008, at 12:19 PM, Vladimir Vukicevic wrote:
I'd like
Sure; bilinear filtering is slower than nearest neighbour sampling,
and in many cases the app author would like to be able to decide that
tradeoff (or, at least, to be able to say I want this to go as fast
as possible, regardless of quality). Some apps might also render to
a canvas just
I like the idea of this property. I actually would love to see the
SVG property applied to HTML img as well. :)
dave
On Jun 2, 2008, at 4:15 PM, Vladimir Vukicevic wrote:
Sure; bilinear filtering is slower than nearest neighbour sampling,
and in many cases the app author would like to
Yeah, I agree -- I thought that there was some plan somewhere to
uplift a bunch of these SVG CSS properties into general usage? I know
that Gecko uplifted text-rendering, we should figure out what else
makes sense to pull up. (If image-rendering were uplifted, it would
apply to canvas,
On Jun 2, 2008, at 4:34 PM, Vladimir Vukicevic wrote:
Yeah, I agree -- I thought that there was some plan somewhere to
uplift a bunch of these SVG CSS properties into general usage? I
know that Gecko uplifted text-rendering, we should figure out what
else makes sense to pull up. (If
That's exactly what i would be afraid of people doing. If I have a
fast system why should i have to experience low quality rendering? It
should be the job of the platform to determine what level of
performance or quality can be achieved on a given device. Typically
such a property would
On Jun 2, 2008, at 2:39 PM, Oliver Hunt wrote:
That's exactly what i would be afraid of people doing. If I have a
fast system why should i have to experience low quality rendering?
It should be the job of the platform to determine what level of
performance or quality can be achieved on a
On Jun 2, 2008, at 4:57 PM, Vladimir Vukicevic wrote:
On Jun 2, 2008, at 2:39 PM, Oliver Hunt wrote:
That's exactly what i would be afraid of people doing. If I have a
fast system why should i have to experience low quality rendering?
It should be the job of the platform to determine
On Tue, Jun 3, 2008 at 9:34 AM, Vladimir Vukicevic [EMAIL PROTECTED]
wrote:
Yeah, I agree -- I thought that there was some plan somewhere to uplift a
bunch of these SVG CSS properties into general usage? I know that Gecko
uplifted text-rendering, we should figure out what else makes sense to
On Tue, Jun 3, 2008 at 9:39 AM, Oliver Hunt [EMAIL PROTECTED] wrote:
That's exactly what i would be afraid of people doing. If I have a fast
system why should i have to experience low quality rendering? It should be
the job of the platform to determine what level of performance or quality
On Jun 2, 2008, at 3:19 PM, Robert O'Callahan wrote:
On Tue, Jun 3, 2008 at 9:39 AM, Oliver Hunt [EMAIL PROTECTED] wrote:
That's exactly what i would be afraid of people doing. If I have a
fast system why should i have to experience low quality rendering?
It should be the job of the
26 matches
Mail list logo
