Revising the Python API

[Mike Fletcher]

I've just uploaded a patch (http://code.google.com/p/sfapi/issues/
detail?id=39) which is intended to open discussion on making a more
comprehensive and useful Python API for SFAPI.

We are using this package internally to test a somewhat large multi-
control Flex GUI (along with a number of patches now in the tracker).
It allows us to use Python's nosetest package and module setup/tear-
down features during integration tests to share heavy fixtures.

The API here is automatically generated from the .as files, including
extraction of doc-strings so that the resulting Python package is
pydoc-able (approximately as much as the .as code is documented,
anyway). It is also packaged with the intention that the results be
uploaded to PyPI for automatic installation.

[Mike Fletcher]

There were a number of issues with the patch due to poor extraction
from our internal code-base. I've created a branch with the updated
code/fixes (as well as all of my other patches to the project that we
use internally). There are also some new fixes that eliminate a
number of errors in the AppTreeParser as well (basically the code
could miss elements in the tree due to erroneously considering them
sprites), while reducing the amount of code involved in the "parsing"
substantially.

Branch is here:

bzr branch lp:~mcfletch/+junk/sfapi-python

The updated "parser" is here:
http://bazaar.launchpad.net/~mcfletch/%2Bjunk/sfapi-python/annotate/head%3A/flex_source/src/sfapi/core/AppTreeParser.as