Originally Posted by nvidia2008
Come to think of it, basically this tablet is going to be predominantly Flash-on-QNX. It's more risky the more I think of it.
The old skool Flash was where everything had to be running in an animation, and you poll for events every 1/25 of a second (eg. running 25 fps). As Groovetube mentions now it's more of something where there are listeners for events, you don't need the timeline running. But Flash player still has to be *listening* for events.
I have dabbled in animation and compositing with FCP and Motion... everything from simple transitions, titles, tracking, rotoscoping, particle generation, morphing, tweening... could someone 'splain to me how you do some of these things without a timeline.
There are two forces at work. As Groovetube mentions, on the dev side, there is smart coding and so on. On the other side though, pre-10.1 as we know things are not very pretty no matter what the dev does. The problem is not so much the code but as soon as you start having animations, etc. the render engine starts to chew up CPU. I don't think listeners and idling is the issue as much as animation and sound.
For purposes of this question, ignore the old, bad, legacy Flash and focus specifically on 10.1 or state-of-the-art Flash.
Let me make sure I understand.
1) Flash remains an interpreted language, correct?
2) Instead of being poll-driven, it is interrupt-driven (listeners)
3) when a listener is triggered, an "animation" runs
4) the animation is coded in ActionScript and must be interpreted
5) once interpreted the graphics generation is handled by a real-time render engine
Put all this on top of QNX and you've got an interesting but risky situation. Everyone is going to go nuts on the animation of apps because they can and because of current Flash habits. On top of that the PlayBook OS itself is supposed to be intensely animation heavy and especially, transparency-compositing-heavy. As Flash designers and devs know, once you have transparency, be prepared for some CPU nom nom nom. Throw in on-the-fly drop shadow, blur and other render effects on a per-element(symbol) basis. Mmm...
I understand the attractions/costs to use dynamic, real-time animation at the app level.
But, you are saying that the QNX/Flash hybrid OS is going to do animations at the system level.Certainly that won't be ActionScript and interpreted then rendered-- rather some very tight code like CoreAnimation on iOS... right?
Here's a Flash from the past, ca 1994:
Macromedia Director (1993-2005)
The "multimedia" hype is now in full swing. Myst is a big seller and 'multimedia CD-Roms' are selling in shops. Bill Gates announces the licensing of Director player. Marc Canter said that this " was a trip - as I knew he didn't really get the ramifications of building animation into Windows".3 Marc had been a strong advocate of OS level support for playback and worked hard to get the MS deal done. He thought that animation should be an OS level data type like text, sound and images. Marc's successor thought that system level support (in essence writing parts of the OS) was too grandiose for such a small company and relegated the system players to the back burner where they quietly died.
I re-watched the PlayBook video paying close attention to the animation.
I think that, now, I better understand-- they were showing off the OS's animation/presentation capability.
To be fair, Apple and Android Device mfgrs do this in their presos, to some extent -- but it is always in conjunction with a user...
The PlayBook video didn't show any user interaction, not even one finger -- Don't touch that touch screen!
Seriously, it was just one big [Flash] movie... more of a cartoon, actually.
Above, you said: "Put all this on top of QNX and you've got an interesting but risky
It appears, at least for now, that RIM/Adobe have fallen victim to the "animation" temptress, and forgotten the user.
Will they be able to kick the habit?
Basically what happened is Adobe and RIM got together based on their desire to stick it up Apple. RIM of course wants to be back in the limelight and prevent tablets and iPhones from invading their business domain. Adobe is pissed that a major, popular mobile OS almost completely locked them out. They want to get back on Flash on mobile in a big way, who knows how Froyo adoption and Flash-on-Froyo is doing. So Adobe goes to RIM, promises some very, very, very big things, they scheme, and voila. A Flash-driven, RIM developed iPad killer.
It will be good times to see how this plays out.
Adobe is smart, in terms of betting on both Android and RIM. But time will reveal the payout from the gamble.
Just for the record, I ran the PlayBook vid at 720P, full screen, on a 24" iMac 2.8 GHz, Core 2 Duo with 4 GB RAM, ATI Radeon HD2600 GPU. The Flash plugin spiked from about 12% CPU up to about 104% CPU for the duration