Sometimes we want people to supply an alternate interface to "swap out" certain things. For example, they might want a totally different user authentication system, and maybe we'd have some sort of user authentication api.

Altenately, the storage interface is a good example.

In this method we set up a minimal interface and a default implementation. Users then have the option to swap out this implementation.

I think the way storage interfaces look are already currently pretty good, so swapping out the interface could probably be like:

  pluginapi.set_component('public_storage', BagOfHolding())

Plugins need a way to add their own static files, like CSS, images, etc. They also need ways for them to be linked and statically served. Then they also need a way to include those files in templates.

The docs make some mention of this... the assetlink command we have can be extended for this, and I think we can both extend staticdirect to take a "domain" like:

  {{ request.staticdirect('/images/foo.jpg', domain='plugin:someplugin') }}
  {{ request.staticdirect('/images/foo.jpg', domain='theme') }}

This could also have fallback support... it would be good maybe to try to do something like this:

  {{ request.staticdirect(
         '/images/foo.jpg',
         ["__theme__", "someplugin", "__main__"]) }}

That above example would first try assets from the theme, then someplugin, then __main__. It would be good if the location where these things were found would be cached so as to not have to do more checks for os.path.exists() than we have to.

If you run paste with CELERY_ALWAYS_EAGER=false, but celery is not running, it queues the media for processing with celery. However, the media does not show up in the media processing panel as media in-processing.