On Mon, Mar 10, 2014 at 1:33 PM, Justin Novosad wrote:
>
>
>
> On Mon, Mar 10, 2014 at 4:22 PM, Rik Cabanier wrote:
>
>>
>>
>>
>> On Mon, Mar 10, 2014 at 11:38 AM, Justin Novosad wrote:
>>
>>>
>>>
>>>
>>> On Mon, Mar 10, 2014 at 2:14 PM, Rik Cabanier wrote:
>>>
On Mon, Mar 10, 2014 at 11:07
On Mon, Mar 10, 2014 at 4:22 PM, Rik Cabanier wrote:
>
>
>
> On Mon, Mar 10, 2014 at 11:38 AM, Justin Novosad wrote:
>
>>
>>
>>
>> On Mon, Mar 10, 2014 at 2:14 PM, Rik Cabanier wrote:
>>
>>> On Mon, Mar 10, 2014 at 11:07 AM, Joe Gregorio >> >wrote:
>>>
>>> >
>>>
>>> > What part is slow, the dec
On Mon, Mar 10, 2014 at 11:38 AM, Justin Novosad wrote:
>
>
>
> On Mon, Mar 10, 2014 at 2:14 PM, Rik Cabanier wrote:
>
>> On Mon, Mar 10, 2014 at 11:07 AM, Joe Gregorio > >wrote:
>>
>> >
>>
>> > What part is slow, the decoding and re-encoding, or is just always the
>> > encoding step
>> > that i
On Mon, Mar 10, 2014 at 11:38 AM, Justin Novosad wrote:
> On Mon, Mar 10, 2014 at 2:14 PM, Rik Cabanier wrote:
>> On Mon, Mar 10, 2014 at 11:07 AM, Joe Gregorio > >wrote:
>> > What part is slow, the decoding and re-encoding, or is just always the
>> > encoding step
>> > that is slow?
>>
>> It's d
On Mon, Mar 10, 2014 at 2:14 PM, Rik Cabanier wrote:
> On Mon, Mar 10, 2014 at 11:07 AM, Joe Gregorio >wrote:
>
> >
> > What part is slow, the decoding and re-encoding, or is just always the
> > encoding step
> > that is slow?
> >
>
> It's decoding/re-encoding of an already constructed path.
C
What about making the Path2D constructor a property of each context? E.g.
var path = new myContext.Path2D(...);
Each context would have a different constructor tied to it, allowing this kind
of optimization.
On Mar 10, 2014, at 7:02 PM, Rik Cabanier wrote:
> On Sun, Mar 9, 2014 at 10:52 PM, Dirk Schulze wrote:
>
>>
>>
>>> On Mar 10, 2014, at 3:44 AM, "Rik Cabanier" wrote:
>>>
On Wed, Mar 5, 2014 at 1:46 PM, Rik Cabanier
>> wrote:
While implementing the Path2D object in mozilla
On Mon, Mar 10, 2014 at 11:07 AM, Joe Gregorio wrote:
>
>
>
> On Mon, Mar 10, 2014 at 2:02 PM, Rik Cabanier wrote:
>>
>>
>> What are you not sure about?
>>
>> The current Path2D interface might be unacceptably slow under certain
>> circumstances and there's currently no way for authors to work ar
On Mon, Mar 10, 2014 at 2:02 PM, Rik Cabanier wrote:
>
>
> What are you not sure about?
>
> The current Path2D interface might be unacceptably slow under certain
> circumstances and there's currently no way for authors to work around this.
> There has to be a hint. If not, I don't see a way that f
On Sun, Mar 9, 2014 at 10:52 PM, Dirk Schulze wrote:
>
>
> > On Mar 10, 2014, at 3:44 AM, "Rik Cabanier" wrote:
> >
> >> On Wed, Mar 5, 2014 at 1:46 PM, Rik Cabanier
> wrote:
> >>
> >> While implementing the Path2D object in mozilla, we ran into a
> performance
> >> issue.
> >>
> >> The mozilla
> On Mar 10, 2014, at 3:44 AM, "Rik Cabanier" wrote:
>
>> On Wed, Mar 5, 2014 at 1:46 PM, Rik Cabanier wrote:
>>
>> While implementing the Path2D object in mozilla, we ran into a performance
>> issue.
>>
>> The mozilla implementation uses different "backends" for the canvas 2D
>> context.
>>
On Wed, Mar 5, 2014 at 1:46 PM, Rik Cabanier wrote:
> While implementing the Path2D object in mozilla, we ran into a performance
> issue.
>
> The mozilla implementation uses different "backends" for the canvas 2D
> context.
> Even within the same document, different canvas objects can be on top o
On Thu, Mar 6, 2014 at 2:28 AM, Dirk Schulze wrote:
>
> On Mar 5, 2014, at 11:54 PM, Rik Cabanier wrote:
>
> > On Wed, Mar 5, 2014 at 2:43 PM, Ian Hickson wrote:
> >
> >> On Wed, 5 Mar 2014, Jeff Muizelaar wrote:
> >>> On Mar 5, 2014, at 5:34 PM, Ian Hickson wrote:
> On Wed, 5 Mar 2014, R
On Mar 5, 2014, at 11:54 PM, Rik Cabanier wrote:
> On Wed, Mar 5, 2014 at 2:43 PM, Ian Hickson wrote:
>
>> On Wed, 5 Mar 2014, Jeff Muizelaar wrote:
>>> On Mar 5, 2014, at 5:34 PM, Ian Hickson wrote:
On Wed, 5 Mar 2014, Rik Cabanier wrote:
>
> To work around this, we could add a
On Wed, Mar 5, 2014 at 2:43 PM, Ian Hickson wrote:
> On Wed, 5 Mar 2014, Jeff Muizelaar wrote:
> > On Mar 5, 2014, at 5:34 PM, Ian Hickson wrote:
> > > On Wed, 5 Mar 2014, Rik Cabanier wrote:
> > >>
> > >> To work around this, we could add a couple of constructor methods to
> > >> the 2D context
On Wed, 5 Mar 2014, Jeff Muizelaar wrote:
> On Mar 5, 2014, at 5:34 PM, Ian Hickson wrote:
> > On Wed, 5 Mar 2014, Rik Cabanier wrote:
> >>
> >> To work around this, we could add a couple of constructor methods to
> >> the 2D context:
> >>
> >> Path2D createPath();
> >>
> >> Creates a new empt
On Mar 5, 2014, at 5:34 PM, Ian Hickson wrote:
> On Wed, 5 Mar 2014, Rik Cabanier wrote:
>>
>> To work around this, we could add a couple of constructor methods to the
>> 2D context:
>>
>> Path2D createPath();
>>
>> Creates a new empty Path object [...]
>
> This used to be how many Web APIs
On Wed, 5 Mar 2014, Rik Cabanier wrote:
>
> To work around this, we could add a couple of constructor methods to the
> 2D context:
>
> Path2D createPath();
>
> Creates a new empty Path object [...]
This used to be how many Web APIs worked, but over the years we've
received enormous volumes of
While implementing the Path2D object in mozilla, we ran into a performance
issue.
The mozilla implementation uses different "backends" for the canvas 2D
context.
Even within the same document, different canvas objects can be on top of
different graphics libraries. For best performance, the Path2D
19 matches
Mail list logo
