flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: Web to Print solutions
Date Wed, 21 Nov 2012 23:50:00 GMT

On 11/21/12 3:08 PM, "Aaron Miller" <amiller@learnatvivid.com> wrote:

> 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 over competing products in our niche. I didn't even have any problems
> with scrolling (using a Scroller to scroll a parent container), bounce effect,
> "swipe away navigation," and all. I am using standard TLF with a slightly
> modified RichText component for the view. I don't even see why it would be a
> problem. Isn't it essentially just a bit map once it's rendered?
If you render the entire page and then scroll the page, then it should be
fast, but Spark TextArea virtualizes the lines that you can't see and the
recalculation of which lines to show is a killer.  But so can rendering an
entire page if the 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:aharui@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" <harbs.lists@gmail.com> 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
> else recently complained about scrolling renderers as well.
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui

Alex Harui
Flex SDK Team
Adobe Systems, Inc.

View raw message