With all due respect tom, your comments are the very reason why Adobe tends not to let things publically available this early. They are afraid that people like you will make comments/judgements like this. You need to understand a little bit about software development, this is called an alpha build. Yes they say it's a public beta but it's just been released, it's so fresh any developer would still classify this as an alpha. Adobe is TRYING to open it's doors to us, it's trying to ditch the old secretive, cloak and dagger business model and give us a real opportunity to provide useful, contructive feedback. Not complaining about aeshtetics on a product that brand spanking new (essentially) and still in development. So I think I speak on behalf of the Adobe team when I say, you're welcome for the opportunity to get exclusive preview access to this free software you didn't have to pay a dime for.
with all due respect, but your comment is the very reason why i do consider not using adobe technologies in the future. what you describe as opening doors is a long overdue step to provide early access to a properitary technology that struggles to survive due to the advances of concurrent approaches. if you intend to speak on behalf of the adobe team i'm sorry to say that your answer has this type of arrogance that i really dislike. and i agree, i'm not going to pay a dime for that.
This preview release is designed for evaluation purposes only. We do not recommended that this release be used on production systems or for any mission-critical work. So the answer is no - there is no way to remove the watermark.
I hope that once you show off the amazing things you can do with Flash, decisionmakers aren't going to focus too much on the fact that a tech preview has a watermark that is clearly not part of the final product.
Group Product Manager, Adobe Flash Runtimes
Incubator builds are not preview, alpha or beta quality. It's before that state - this is code under active development. The watermark is a visual indicator of that fact. Many companies follow this practice for pre-release software - for example, Microsoft Windows pre-release builds have a watermark with version in the bottom right corner of the screen to indicate it an evaluation and not a final version.
Also, Flash Player is one of the most widely distributed pieces of software and our audience is quite broad. End users are by far our biggest customer segment. We need to make sure people - developer or end user - that install Incubator builds know and understand what they're getting themselves into. In the past, we have seen links to previews and betas delivered out of context of the content we have on Labs that explains that pre-releases have not yet gone through security review, may not be stable, etc. These builds don't give users auto-update notification and can make it difficult for a user to install a release player (because it is a later version, or you must run the uninstaller before you install a different version).
Comon, we are all intelligent enough to know what we're using, and why should people knows about it if they downloaded themself the incubator and they're there to test, view and enjoy it and during that time, if the developpers face a huge watermark like this it's a pain and it's a no need for them. At least, get this watermark out of the way.
It can be anything but not as aggresive as this.
If you want Flash to continue being widely used, listen the people that uses it. Yes it's free we know that so if it is why are you working so hard to have it out there ?
first: sorry for my englsh:
I think the problem is, that the most developers aren't 100% professionals. The most have only one computer for developing and for else.
So when you have installed flashplayer 11 every swf in the internet have the build information.
Couldn't it be possible to integrate in the context menu a button to switch display buidinformation on or off.
I think flashplayer 11 is also flashplayer10.2 without any bugs.
The bugs in the incubation build concern only the core classes for 11??
And should one normal user download and install flashplayer, he should be aware of using the buildinformation.
OK. Perhaps a button in the context menu wouldn't be not so perfect, because normal users would forget using flashplaer11. But there should be a possibility to change a line in some configuration files to toggle display off.
Use Inteligent Navigator as Chrome, in Chrome://plugins you can Disable your actual version of flash player an enable Incubator for test o evaluation, and for daly use enable your normal version and disable Incubator. Not unistall your actual version of flash player when install Incubator. Any way this bottom copyraight is a famous one more bad ideas of adobe genius. But Flash is exceptional, you have patients for small fails.
Saludos amigos from Cancún México
sorry for my short english
Going one step further, it would be handy for testing to display actual info like render mode and fps automatically down there, too, because many demos don't do so, and we can only guess which demo seems to fall back to software mode in some environments.
I fully understand the watermark. GPU accelerated demos in flash are very interesting for a broad mass, and many non-developers will download the incubator build just to see some demos live. If there was no watermark, most users would leave this player as a standard as long as their daily flash apps like video portals i.e. are working. This behaviour could result in very many unstable builds around the world for a long time, even after final flash players 11 and even 12 are distributed.
The watermark is the best direct way to avoid this.
I have one additional idea.
You can place a Button in the contextmenu, with which you can turn off this watermark for 30 times or so. After the player was started 30 times the watermark is shown again.
I think the context menu fulfill security issues, because it also manage camera access and so on.
Europe, Middle East and Africa