To integrate or not to integrate

An existing or new Flash module? Here is a check list to help you make a decision.

Why is SWF Tools so large?

To use SWF Tools for your own Drupal project, you really only need one or two modules: swftools.module and perhaps something like swfobject.module to optionally enable flash replacement.

The plan is to ship a cut-down API-only version of SWF Tools containing only swftools and swfobject - this will demonstrate SWF Tools modularity and allow site administrators to keep a clean modules directory.

Is the full suite worthwhile?

There are a lot of nice-to-have features in SWF Tools which may become available to your users without any extra work on your behalf. Filters, alternative flash players, and alternative flash replacement techniques.

Why not code my own Flash embedding?

Mainly to avoid redundancy. There is a lot of code in Drupal contrib that replicates the basic process of embedding a flash file.

SWF Tools is also trying to focus community knowledge in one place, this should benefit all co-operating projects because the code is more stable, more flexible and feature rich. Perhaps there are skills and techniques you can add?

I want to use SWF Tools API for a new .swf media player, should I start my own project?

This is entirely up to you. You can start your own project, and add SWF Tools as a dependency. If you'd like to put your module within SWF Tools project, please add your code to the issues queue and it will be appreciated and considered for inclusion.

Data services with Flex and/or AMFPHP?

You should stop in at the Services module project page, as SWF Tools does not plan to extend into this area.