View Single Post
Guest | Posts: n/a | Thanked: 0 times | Joined on
#1806
Originally Posted by attila77 View Post
WHAT ? Adobe makes the final decision, always did, based on certification/distribution/whatever. It controls distribution of all desktop builds, and until very recently, it was Adobe who distributed the Android Flash builds, too (and still does do that for the betas).
Erm... still no. Adobe handles the port - upon vendor solicitation, they had worked with ARM for processor optimization, tailors the plugin for the platform. Beta testing - view http://labs.adobe.com - is still done by Adobe, once it is "finished" it is released to the vendor/manufacturer for their approval and implementation.

Find where Adobe has stated that they've "done the work" and it's up to Nokia to distribute it. It's been listed in this thread a few times.

What you are proposing is that a 3rd party (Adobe) has the ability to distribute, approve and push into another vendor's OS or app store an application/plugin and they're the ones that certify it... that's totally incorrect. Google approved Adobe AIR, Google approved Flash Player 10.1 - that's after QA testing and the like.

To repeat the for the millionth time - where is that public (beta/techpreview/Idontcare) ARM Linux Flash build ?
You can keep repeating all you like, there was never a public for ARM. There was a public beta for Windows, Mac, Linux - you know... the operating systems where you can install things as such. How hard is that to understand? You're going at this like the ARM based OS's are not under some form of version control to avoid the diversity that's on x86 based OS's - you know... where people can add, change, modify hardware and the OS. Each and every ARM based OS on the tablets, phones, et al are under the control of somebody else, usually the vendor. And then Adobe has to play by those rules. Everybody does... care to name one plugin that breaks this observation?

Anyway, Adobe does the work, Nokia does the implementation and distribution. Ever care to ask the better question as to where Texas Instruments got their Adobe Flash from?

Which other platforms are you talking about, not counting hacks, previews, announcements, unsanctioned builds, etc ?
Which platforms support your verbiage? Don't list Mac, Windows nor Linux. Start there.

Flash has nothing to do with computers, its bastard versions are available on basically anything.
Yet on my computer, I'm already running 10.2 beta. But on the "mobile computer" you can't even install a newer version of a plugin, get an updated version of Skype, update or maintain the BME... face it, if it's closed source on Maemo, you're SOL.

Because TI is not releasing it, that is the problem. Their license is only for hardware OEM manufacturers. Let's say for argument's sake Nokia had the same thing (disclaimer: I have no idea if it does). It still couldn't give it to you as the Adobe T&C specifically forbids it. Back to square one.
TI got it from Adobe. TI has to state that they will not distribute it based on the manufacturer of the handset and OS. Until Nokia gets off their fat arse and says "It's ok to distribute", TI and Adobe can't distribute it.

As it stands, it is unoptimized, ultimately unusable as it stands. Either Nokia needs to work on its implementation better, TI needs to optimize it better for Nokia or Adobe needs to get paid to finish the work that Nokia is unwilling to do.

You've somehow applied open source logic - public betas - and desktop OS - ability to install closed source betas and updates - to this situation.

It just doesn't fit. If you think it does, please show me where this has been allowed in the past. VLC? Silverlight? Skype? Real? Give me a place where updates and/or betas have been installable that affect another piece of software that's tied to the OS - read: browser - that supports your position.

Last edited by gerbick; 2011-01-02 at 18:22.
 

The Following 3 Users Say Thank You to For This Useful Post: