On Dec 21, 2007 4:49 PM, Ed Trager [EMAIL PROTECTED] wrote:
A question to ask might be, when will the XO get updated to use FF3's
new rendering engine? The new engine is supposed to be faster,
although I have not found that to really be the case on our machines.
We are currently using the
Is the Browse activity using a stable version of XULRunner? If so, how
are you able to use the stable release of XULRunner, and still use
firefox 3 beta 1's rendering engine?
Please let me know. Thanks.
Jake
On Dec 23, 2007 8:56 AM, Marco Pesenti Gritti [EMAIL PROTECTED] wrote:
On Dec 21, 2007
We ship xulrunner on the builds, I'm not sure what kind of performance
we get out of SVG right now, though.
Marco
On Dec 20, 2007 9:06 PM, Jake B [EMAIL PROTECTED] wrote:
Hello All,
I am expecting to get my XO laptop in the mail any day now. I was hoping
someone could tell me, does the XO
I've seen some examples of this working, though none of them complex
enough to really test performance. The core problem when I used it was
that the coordinate system for the mouse events didn't map correctly
to the display, due to the browsers scaling algorithm. I'm not sure
in what timeframe
On Dec 20, 2007 9:30 PM, Eben Eliason [EMAIL PROTECTED] wrote:
I've seen some examples of this working, though none of them complex
enough to really test performance. The core problem when I used it was
that the coordinate system for the mouse events didn't map correctly
to the display, due to
On Dec 20, 2007 9:31 PM, Marco Pesenti Gritti [EMAIL PROTECTED] wrote:
On Dec 20, 2007 9:30 PM, Eben Eliason [EMAIL PROTECTED] wrote:
I've seen some examples of this working, though none of them complex
enough to really test performance. The core problem when I used it was
that the
On Dec 20, 2007 3:31 PM, Marco Pesenti Gritti [EMAIL PROTECTED] wrote:
On Dec 20, 2007 9:30 PM, Eben Eliason [EMAIL PROTECTED] wrote:
I've seen some examples of this working, though none of them complex
enough to really test performance. The core problem when I used it was
that the
Just to make sure I understand, do you still have problems even after using
the functions built into SVG for translating from screen coordinates to user
coordinates?
http://www.w3.org/TR/SVG11/coords.html#NestedTransformations
http://www.w3.org/TR/SVG/types.html
Using getScreenCTM and such
