I believe you lose the ability to perform any background tasks by
setting rendermode to direct, at least on IOS. This will be a
dealbreaker for many apps. See this bug for more details and be sure to
vote:
https://bugbase.adobe.com/index.cfm?event=bug&id=3349232
On 8/23/2013 1:47 PM, jude wrote:
When using direct mode do you lose any functionality? I think there was a
GPU mode and you lost filters and other features so I could not use it at
the time. Is direct mode the same? Thanks
On Fri, Aug 23, 2013 at 5:17 AM, Deepak MS <megharajdee...@gmail.com> wrote:
Hi Swen,
Thanks a lot. That really helped. It works fine now :)
I'll surely be blogging about performance boost that we have in 4.10 soon
in my blog...I just felt like adding up NOS (Nitrous) in NFS, while using
my app ! ;) Thanks for such a cool release!
Cheers!
Deepak
http://deepflex.blogspot.com/
On Fri, Aug 23, 2013 at 2:50 PM, Swen van Zanten <f...@hdsign.nl> wrote:
Hi Deepak,
I also had that problem,
this one is easily fixed by editing the skin.
inside the scroller it looked like this:
<s:Grid id="grid"
itemRenderer="spark.skins.spark.DefaultGridItemRenderer">
<s:GridLayer name="backgroundLayer"/>
<s:GridLayer name="selectionLayer"/>
<s:GridLayer name="editorIndicatorLayer"/>
<s:GridLayer name="rendererLayer"/>
<s:GridLayer name="overlayLayer"/>
</s:Grid>
now it looks like this:
<s:Grid id="grid"
itemRenderer="spark.skins.spark.DefaultGridItemRenderer">
<s:gridView>
<fx:Component>
<s:GridView>
<s:GridLayer name="backgroundLayer"/>
<s:GridLayer name="selectionLayer"/>
<s:GridLayer
name="editorIndicatorLayer"/>
<s:GridLayer name="rendererLayer"/>
<s:GridLayer name="overlayLayer"/>
</s:GridView>
</fx:Component>
</s:gridView>
</s:Grid>
Hope it helps you.
Regards,
SWEN VAN ZANTEN
Hoofdstraat 160
2171 BL, Sassenheim
Op 23 aug. 2013, om 11:08 heeft Deepak MS <megharajdee...@gmail.com> het
volgende geschreven:
I had built an iPad app using Flex 4.6|AIR 3.6 sometime back. Looking
at
this email, I got curious to see how my app would perform on 4.10.
Agreed! Overall performance in comparatively good.
- Popups used to have a delay of 3-4 seconds, but now it just pops up
without any
delay.
- Switching between tabs(for the first time) in a TabbedViewNavigator
had
a delay of 3 to 4s (based on number of UI elements on each of the tab
views). But now it takes 1.5s or less.
But size got increased a little:
- Compiled size was 9,178,761 bytes using flex 4.6|AIR 3.6 and it is
9,762,490 bytes using flex 4.10|AIR 3.8, which is just fine for me, it
not
a big issue.
However, I came across one issue(which wasn't there in Flex 4.6). I am
using a datagrid with a skinClass. If I use a skin class, it shows up a
blank datagrid on the screen. But when I remove this skinclass
property,
it
displays the datagrid properly with all data in it.
Though datagrid is not optimized for mobile, I am still using it for my
app(iPad), as I did not find any scrolling issues. It works smoothly as
it
works for web.
Screentshots for reference:
http://snag.gy/nAcyD.jpg - with skinClass in flex 4.10
http://snag.gy/zwWnA.jpg - without skinClass in flex 4.10
On Fri, Aug 23, 2013 at 1:05 PM, DarkStone <darkst...@163.com> wrote:
Great!
But my friend is getting married this weekend, I've got no time to do
a
benchmark test.
Maybe next weekend I can do it, I'll try my best, I'm too busy just
like
everybody else.
DarkStone
2013-08-23
At 2013-08-23 14:13:21,"OmPrakash Muppirala" <bigosma...@gmail.com>
wrote:
On Aug 22, 2013 10:21 PM, "DarkStone" <darkst...@163.com> wrote:
Can anyone help spreading the good news?
I think we need Apache's official support to publish the news,
indicating
that Flex 4.10 + AIR 3.8 running very smooth on iOS and Mac devices
when
renderMode is set to direct.
This is very important for the rise of the Flex.
Can someone from the inside verify it and take it seriously,
please~~~
We can probably do a blog post about it. But we need some solid
benchmarks that compares prior versions to current versions. Is that
something you can help build and publish?
Thanks for all your help!
Om
DarkStone
2013-08-23
在 2013-08-22 16:37:22，"Ram Lee" <ranbolee...@gmail.com> 写道：
Good to know that, I will try Adobe Scout sometime, I think your
data
is
awesome!
Ram Lee
在 2013-8-22，14:58，DarkStone <darkst...@163.com> 写道：
Hi Ram,
You're welcome.
If you want precise performance benchmark, you can use Adobe
Scout.
A friend of mine said, by using Scout, a Flex mobile application
which
has a Spark List of 500 itemRenderers on it, running on the iPod
touch
5,
madly swiping finger across the itemRenderers, Scout reported this:
If set Flex Application' framerate to 24, the runtime testing
result
is 24, no dropping frames!
If set framerate to 60, the result is 48-55 frames per second,
which
is already a big deal!
You can do your own test using Adobe Scout, good luck.
DarkStone
2013-08-22
At 2013-08-22 14:09:48,"Ram Lee" <ranbolee...@gmail.com> wrote:
Thanks a lot for the notes and good to know that!
I did try the direct renderMode on my retina Macbook and feel the
performance improvement!
And I was wondering if there are some good performance test tools
to
make this improvement more qualified? because what I do now is just
resizing the app window to see if it renders the diplay object faster
and
smoother.
Again, thanks a lot for the NEWS!
Ram Lee
在 2013-8-22，13:28，DarkStone <darkst...@163.com> 写道：
Hi Ram,
The major performance improvement is done by AIR 3.8 (not
earlier
AIR versions), and the reason why Adobe didn't mention this is
because
they
always have the lousy PR (Public Relations), which hide the good news
and
spread the bad news, they should fire their PR managers immediately.
At the same time, Flex 4.10 fixed a lot of bugs, which improves
the
framework perfomance as well.
So with Flex 4.10 and AIR 3.8, you can really build mobile apps
with
it, and running smooth on iPhone & iPad & Mac & PC.
Now, we can proudly say that Flex has become the best
crossplatform
application development & deployment solution on earth!
DarkStone
2013-08-22
At 2013-08-22 13:10:38,"Ram Lee" <ranbolee...@gmail.com> wrote:
Is this from AIR 3.8 or earlier versions? just searched the
internet, wonder why Adobe didn't mention such performance boost on
the
Apple devices?
李楠
在 2013-8-22，12:23，Joel Tan <joel...@cype.com.my> 写道：
Yes, I can feel the performance improvement as well on Flex
mobile
app!
On Aug 21, 2013, at 7:20 PM, DarkStone <darkst...@163.com>
wrote:
It surprised me when I try to recompile my old Flex 4
projects
with Flex 4.10 & AIR 3.8 SDKs, and deploy them to iPhone & iPad &
MacBook,
they runnning incrediblely smooth, like 2 to 3 times faster than
before,
nealy native app performance!
The trick is you need to set <renderMode>direct</renderMode>
in
the -app.xml file, this will boost performance on iOS and Mac OS, so
everybody just keep in mind of this.
Now that the performance issue of Flex has been greatly
improved
on mobile devices, I'm very excited, finding that Apache Flex has a
great
future!
Flex is an awesome framework, which has great development
efficiency, I think it's time to let the world know that Flex is
still
kicking and it is the best solution for application (not game)
development
and deployment across all platforms.
So we should really working on the official Flex Showcase,
more
video demos of Flex Mobile Apps on iPhone & iPad will be great! I'm
planning to submit my own demo to the showcase when I got the time.
I've already wrote a decent blog post to spread the good news
to
the Chinese Flex Developers, here is the link:
http://blog.sina.com.cn/s/blog_6f56a2bf0101dm98.html
Many thanks to the Apache Flex Community, I love Flex, and we
shall attract more and more people to the Flex community!
DarkStone
2013-08-21
