3 Replies Latest reply on Feb 28, 2010 9:08 PM by crsby

    Standard vs. Proxy Plugins vs. Reference Plugins


      Is there somewhere I could go for a better understanding for the differences in how to implement standard vs. proxy vs. reference plugins.


      Standard Plugins seem pretty straight forward, add MediaFactoryItem to the PluginInfo's mediaFactoryItems list, and it creates the MediaElements based on the mediaElementCreation function.


      Proxy plugins aren't really an issue for me - Create your MediaFactoryItems and pass in MediaFactoryItemType.PROXY and then deal with the mediaElement in the overridden methods of an extended Proxy class.


      Reference Plugins are where I run into issues. As far as I  understand it, the plugin should receive a reference of each MediaElement  created by the MediaFactory (for those created before and after the plugin was loaded) - I'm not clear on the API for that - where  and how does that happen - or has this changed (I'm currently working  off rev. 14237 from the public trunk)?


      On a side note I've read in a couple of places that you could add visual element via a plugin - for example, if i wanted to add a stats panal to a media player that displays the mediaElement's info (MIME type, currentTime, url etc) in an overlayed panel I'm not sure what I'd need to work with to implement this from a plugin. Or, am I even on the right track with this thought?


      References I've found at so far:

      Dev Guide: http://help.adobe.com/en_US/OSMF/1.0/Dev/osmf_dev_guide.pdf

      User Group Plugin Preso: http://experts.na3.acrobat.com/p17613147/

      and of course the ASdocs


      Thanks in advance,