Ad API 3 > Component Basics
Component Dependencies
When the Ad API object is passed to a component, it contains some basic functionality by default. However, a lot of additional functionality can be switched on using dependencies.
For example, by default a component does not have access to our feed proxy and feed parsing API. However, if you are building a component that contains feeds, you can switch on this access. This way, specialized functionality that is not necessary for a particular component is not loaded into that component, and can be activated on an as-needed basis for individual components. We do this in order to reduce the file size, and consequently the loading time, of our ads.
Configuring Dependencies
You can configure a component's dependencies in Component Studio as follows.
- In Component Studio, click the icon at the top to launch the Configuration screen.
- Check the Component has dependencies checkbox.
- Check the boxes next to the dependencies you want to add to this component.
- Click Publish Changes to publish the component with these new settings.
Available Dependencies
The following dependencies are currently available in our components:
- Animation: Enables our animations engine, which includes linear, exponential, elastic, and bounce transformations.
- Cookie Manager: Enables getting and setting cookies.
- Data Store: Enables storing and retrieving key/value pairs to/from Flite's servers, and creating custom forms and polls.
- Feed Parser: Enables RSS and Atom feed parsing functionality.
- Feed Proxy: Enables use of Flite's feed proxy.
- Geolocation: Enables basic geolocation functionality.
- Image Loader: Enables dynamic loading of images and SWF files, optionally using an image proxy.
- Theme: Enables use of Flite's theme elements, including scrollbar, loading spinner, and sharing controls.
- Video: Enables loading and playback of videos.