Dynamic Display Pictures are animated display pictures with advanced functionality (Moods, Animation) that users can create and purchase from third party partners. Due to security concerns, Dynamic Display Pictures can only be purchased from official Microsoft content partners such as:
American Greetings/Blue Mountain à http://www.aginteractive.com/products_overview.html
3H Group (MeeGos) à http://www.3hgroup.com/index.htm
Saw-You (Weemees) à http://www.weeworld.com/
Wisepost/YNK (Korea) à http://www.ynkkorea.com/
DDPs support Flash (.swf) files for animations and conversation-specific moods. You must also include a flat image (96 x 96 pixels, gif or png) for the default image to be used for downlevel applications, including Mac Messenger, mobile devices, etc. The default size and shape of a dynamic display file is 142 x 98 pixels. Since a dynamic display picture consists of multiple elements it needs to be shipped as a .CAB file. This .CAB file is cryptographically signed and placed along with the signature in a content pack (e.g. a theme). It will be shipped as a .CAB file inside a .CAB file. Sometimes .CAB files are also .MCT files. Despite the different extension, the contents are identical.
When developing a Windows Live Agent that uses a Dynamic Display Picture, use the following criteria:
- An *uncompressed* .CAB or .MCT file with the appropriate assets
- ASCII content.xml files. Unicode is not currently supported.
- A Microsoft signature -- this may be inside the .CAB or .MCT, or it may be a separate file
Add the following line to the service in your .bfg that should display the DDP:
You can also use buddyicon-dynamic, but it's deprecated in current builds of the SDK. It can be usefull in case you have a compressed .CAB file. You decompress it manually and setup the .BFG file with the individual components inside it.