08/09/2010, 02:50 AM
As far as porting goes, it's VERY difficult to port a closed source application.
In fact, it's more or less impossible.
Whenever anybody ports a closed source app, what they're really doing is either wrapping it in some sort of compatibility layer, or reverse engineering and re-writing it.
We can pretty well eliminate the possibility of reverse engineering. The results are always iffy at best, and there are already open-source implementations of flash that work as well as an RE would.
As far as wrapping it up in a compatibility layer, that is completely different for every combination of application and system. Basically, you're talking about wrapping flashplayer inside of another app or library so that the flashplayer thinks it's running on a supported system. Then you have to make the browser think it supports your special flashplayer, and make sure the browser knows what to do with flash content.
As you can imagine, that's a huge undertaking. You need skilled and clever programmers, a large enough user-base that people will care, and you need reasonable assurance that your effort won't be wasted. WebOS has a comparatively small user base, and Adobe has promissed flash for WebOS. iOS on the other hand, has a very large user base, and no chance of flashplayer without this kind of project.
In short, there are few enough people who care, enough difficulty, and enough risk of a 'real' flash plug-in making your work wasted; that there is pretty much no chance of this happening.