What is FlashPlayerControl? 
---------------------------

FlashPlayerControl is a .NET component to enhance Macromedia Flash
Player ActiveX features. It does not use its own engine to display
movies but provide a wrapper around official swflash.ocx/flash.ocx
code instead. Thus it is possible to avoid certain Macromedia Flash
Player ActiveX limitations.

Features at a glance 
--------------------

 * Load flash movies from memory directly (no temporary files!). 
 * Create flash-enabled applications which are ready to work even where Macromedia Flash Player ActiveX 
   is not installed! 
 * Write code which is compatible with any version of Macromedia Flash Player ActiveX (3, 4, 5, 6, 7, 8). 

Do all this and more with... FlashPlayerControl! 

Macromedia Flash Player ActiveX 3, 4, 5, 6, 7, 8 are supported. 

Load flash movies directly from any source (no temporary files!). Protect your flash movies. 
--------------------------------------------------------------------------------------------

It is known fact that the Flash Player ActiveX is able to load movies
at certain URLs only. You have to save the movie to a temporary
location from your application's resource before you can load it.
You'll have to generate a corresponding link that you can pass to the
Flash Player ActiveX and then delete the movie after. You'll have to
admit that this is extremely inconvenient. Apart from being
inconvenient there is a chance you'll fail when you try to create a
temporary file if you don't have the appropriate permission or don't
have access to a temporary folder. It is definitely not an appropriate
approach when security is an issue since your movie can be easily
intercepted. There is a solution! FlashPlayerControl uses a different
approach of swflash.ocx/flash.ocx code loading. It is able to load
your movies directly to the Macromedia Flash Player ActiveX thereby
avoiding the temporary file step. The advantages are pretty obvious.
And you can also protect your movies from unauthorized access using
your favourite software protection application.

Create flash-enabled applications which are ready to work even when Macromedia Flash Player ActiveX is not installed! 
----------------------------------------------------------------------------------------------------------------------
 
One of the biggest problem using the Flash Player ActiveX is the
mandatory component registration. The common approach is to save
swflash.ocx/flash.ocx code to temporary files and then register them.
The disadvantages are the same as above mentioned - insufficient
permissions to save and register an swflash.ocx/flash.ocx. Now you can
forget about these problems! FlashPlayerControl is able to use
swflash.ocx/flash.ocx from any source. For example, you can put an
swflash.ocx/flash.ocx code inside of your application's resources and
instruct FlashPlayerControl to use it. It is important to note that
FlashPlayerControl does not use temporary files and
swflash.ocx/flash.ocx registration but loads and uses the code
directly. No more user management rights problems - no more temporary
files and no more component registrations. It is up to you to decide
what swflash.ocx/flash.ocx to use - by default already registered
component is used.

-----------------------------------------------------------------
Copyright (c) 2004 - 2005 Softanics. All rights reserved.
Macromedia and Shockwave Flash are trademarks of Macromedia, Inc.
