3f10890319
These are just the doc strings I created as I was spelunking through to see how Sugar manages launching applications. The resulting auto-documentation is neither polished or finished, but it should help people reading the code somewhat. There are a few minor code cleanups: * activityhandle (replacing C idiom for initialisation with a Python one) * bundle registry (using a parameterised directory name so that it shows up in the documentation) * validate_activity_id function, use isinstance( item, (str,unicode)) for the query, rather than two separate checks with isinstance |
||
---|---|---|
.. | ||
__init__.py | ||
__init__py | ||
activity.py | ||
activityfactory.py | ||
activityfactoryservice.py | ||
activityhandle.py | ||
activityservice.py | ||
bundle.py | ||
bundlebuilder.py | ||
bundleregistry.py | ||
Makefile.am |