page is long.
> Perhaps the
> usage scenarios are different than what I am considering for my own
> application?
>
>
> --
> Aaron
>
> -Original Message-
> From: Alex Harui [mailto:aha...@adobe.com]
> Sent: Wednesday, November 21, 2012 2:35 PM
> To:
...@learnatvivid.com]
Sent: Wednesday, November 21, 2012 3:08 PM
To: flex-dev@incubator.apache.org
Subject: RE: Web to Print solutions
I actually had excellent performance in Android and iOS (only tested tablets)
using TLF based text rendering. In fact performance is one of our selling
points ove
s are different than what I am considering for my own application?
--
Aaron
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Wednesday, November 21, 2012 2:35 PM
To: flex-dev@incubator.apache.org
Subject: Re: Web to Print solutions
On 11/21/12 2:21 PM, "Harbs"
On 11/21/12 2:21 PM, "Harbs" wrote:
> The fact that performance was acceptable in AIR was what I was hoping to find
> out. This is not a game or anything, so frame rates is not a major concern
> (for the most partŠ).
I think it was scrolling TLF text that was the real killer, although someone
Hi Om,
This is great to hear!
The fact that performance was acceptable in AIR was what I was hoping to find
out. This is not a game or anything, so frame rates is not a major concern (for
the most part…).
I'm not surprised that HTML/JS/Webfonts did not work out well. Truth be told,
the only s
