context:
http://apache-flex-development.247.n4.nabble.com/Flex-Scroller-optimization-tp46074p46116.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
version.
>
>
>
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/Flex-Scroller-optimization-tp46074p46090.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.
Hello DarkStone,
Can you access the apache flex JIRA ? If you can, I could attach the .apk of
the demo version.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Flex-Scroller-optimization-tp46074p46090.html
Sent from the Apache Flex Development mailing
ps with
>> cacheAsBitmap
>> - 60 fps with the blitting approch (and a frame budget around 8-10 ms)
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-flex-development.247.n4.nabble.com/Flex-Scroller-optimization-tp46074p46084.html
>> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>>
; cacheAsBitmap
> - 60 fps with the blitting approch (and a frame budget around 8-10 ms)
>
>
>
> --
> View this message in context:
> http://apache-flex-development.247.n4.nabble.com/Flex-Scroller-optimization-tp46074p46084.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>
>http://apache-flex-development.247.n4.nabble.com/Flex-Scroller-optimization-tp46074p46084.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.
ficant, on a nexus 7 : - 25/30 fps with cacheAsBitmap
- 60 fps with the blitting approch (and a frame budget around 8-10 ms)
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Flex-Scroller-optimization-tp46074p46084.html
Sent from the Apache Flex Development
t;
>
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/Flex-Scroller-optimization-tp46074p46081.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.
<https://www.imageupload.co.uk/image/ZTUi>
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Flex-Scroller-optimization-tp46074p46081.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Hi after24,
I believe I had replied you on this topic, in case you missed it, here is the
link (at the 13th floor):
http://apache-flex-development.247.n4.nabble.com/Scroller-optimization-td41774.html#a42858
What I'am saying is, by simply using the cacheAsBitmap mechanism, you can
ac
y.google.com/store/apps/details?id=air.fr.after24.ViewportCacheDemo>
I opened a Jira ticket with the source code FLEX-34821
<https://issues.apache.org/jira/browse/FLEX-34821>
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Flex-Scroller-opt
map is much easier to
>>>>> understand and handle, so we don't have to do the modify the
>> Scroller.as
>>>>> any more, the cacheAsBitmap approach is the best way to improve the
>>>>> scrolling performance now!
>>>>> If you not beli
>>> DarkStone
> >>> 2014-11-30
> >>>
> >>>
> >>>
> >>> At 2014-10-29 18:56:09, "after24" wrote:
> >>>> Hi Jude,
> >>>>
> >>>> /*have you tried setting include in layout to
de in layout to false when setting visible
>>> to
>>>> false?*/
>>>>
>>>> Yes, this property is set to false during scroll operations.
>>>>
>>>> It seems that this performance decrease is caused by scout... when scout
>>> is
>>>> off, there is no difference between the two approaches (visible = false or
>>>> removeElement).
>>>>
>>>> So it looks like this optimization is viable :-)
>>>>
>>>> I am a bit busy this week but I will add a ticket on the JIRA with a
>>> sample
>>>> application as soon as possible.
>>>>
>>>> Thank you.
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>> http://apache-flex-development.247.n4.nabble.com/Scroller-optimization-tp41774p41910.html
>>>> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>>>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
to false during scroll operations.
>> >
>> >It seems that this performance decrease is caused by scout... when scout
>> is
>> >off, there is no difference between the two approaches (visible = false or
>> >removeElement).
>> >
>> >So it looks like this optimization is viable :-)
>> >
>> >I am a bit busy this week but I will add a ticket on the JIRA with a
>> sample
>> >application as soon as possible.
>> >
>> >Thank you.
>> >
>> >
>> >
>> >--
>> >View this message in context:
>> http://apache-flex-development.247.n4.nabble.com/Scroller-optimization-tp41774p41910.html
>> >Sent from the Apache Flex Development mailing list archive at Nabble.com.
>>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
e?*/
> >
> >Yes, this property is set to false during scroll operations.
> >
> >It seems that this performance decrease is caused by scout... when scout
> is
> >off, there is no difference between the two approaches (visible = false or
> >removeElement).
>
usy this week but I will add a ticket on the JIRA with a sample
>application as soon as possible.
>
>Thank you.
>
>
>
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/Scroller-optimization-tp41774p41910.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.
Great news!
On Oct 29, 2014, at 12:56 PM, after24 wrote:
> So it looks like this optimization is viable :-)
= false or
removeElement).
So it looks like this optimization is viable :-)
I am a bit busy this week but I will add a ticket on the JIRA with a sample
application as soon as possible.
Thank you.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Scroller
So the horizontal and vertical scroll
> positions
> >shouldn't affect the actual viewport layout during scroll operations.
> >
> >This stackoverflow
> ><
> http://stackoverflow.com/questions/10037262/building-small-gui-engine-visible-vs-addchild-removechild
> >
> >post could be an explanation of the difference in performance.
> >
> >Vincent.
> >
> >
> >
> >--
> >View this message in context:
> http://apache-flex-development.247.n4.nabble.com/Scroller-optimization-tp41774p41883.html
> >Sent from the Apache Flex Development mailing list archive at Nabble.com.
>
Hello Frédéric,
Sure, I will post an android .apk sample application with the source code. I
just want to clean up the ViewportCache class before.
Vincent.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Scroller-optimization-tp41774p41876.html
Sent
? is the decrease in
> performance between the two approaches is due to the the scroller component
> ?
>
> I will make some tests with scout to see if I can identify the difference.
>
> If this problem can be solved, this optimization will have a huge impact on
> scrolling perf
Cache, but I can
not reflect this interaction on the actual viewport i.e. the actual
ToggleButton should be toggled, when it’s added back to the display list.
Do you think it's feasible ? anyone has an idea ?
--
View this message in context:
http://apache-flex-development.247.n4.nabble.co
23 matches
Mail list logo
