Re: comments on Matrix

On Thu, Mar 21, 2013 at 2:31 PM, Dirk Schulze <dschulze@adobe.com> wrote:
> On Mar 21, 2013, at 2:24 PM, Rik Cabanier <cabanier@gmail.com> wrote:
>> On Thu, Mar 21, 2013 at 12:52 PM, Brandon Jones <bajones@google.com> wrote:
>> I'd like to throw another voice in against throwing exceptions. The faulty assumption here being that if a matrix fails to invert this is worth stopping the entire app for.
>>
>> Realistically most authors will blindly invert and never give a second glance to the result. If invert throws this will result in many apps simply halting, with the only way to get it back being a refresh. If invert returns NaNs or similar most apps will have a bit of graphical data flicker, become lit incorrectly, or possibly disappear. Depending on the structure of the app this may naturally resolve itself within a frame or two. While you can argue that a throw will make invert issues easier to debug I feel that most authors would rather have a suboptimal user experience than no user experience.
>>
>> If you absolutely MUST retain compatibility with this aspect of SVGMatrix then so be it, but I would highly favor including a non-throwing variant and promoting that one as the preferred call.
>>
>> I think that's fine. We'll add another invert call that returns a boolean and takes a matrix.
>
> Before we do that, we certainly should investigate in Tab's complain that applications may not even check for the exception or do not care. Tab, do you know how we could do that?

Look at a bunch of JS graphics libraries that use SVG and don't roll
their own matrices?

(If you can't find any, that's sufficient evidence that it's probably
safe to change. ^_^)

~TJ

Received on Thursday, 21 March 2013 21:37:25 UTC