[sphere]

Hi,

it looks like the add-on frontend only uses a 1:n relation between extension-point and add-on, same with providing media and add-on. In fact add-ons can have multiple extension points and some extension points may have multiple provide-entries.

IMO this should be n:m to "kind" (script, plugin, screensaver, scraper, etc) AND n:m to providing media (image, music, pictures)

Here are two examples:
My Apple iTunes Podcast Plugin has the following extension point:

PHP Code:

<extension point="xbmc.python.pluginsource" library="addon.py">
    <provides>video audio</provides>
</extension> 


which means that it is a plugin providing video and audio. On the Page it is only listed as providing video (audio missing).

Another example is my The Big Picture Script, it has the following extension points:

PHP Code:

<extension point="xbmc.python.script" library="script.py">
    <provides>image</provides>
</extension>
<extension point="xbmc.python.pluginsource" library="plugin.py">
    <provides />
</extension> 


Means, it is a script providing images, but is only listed as script (image missing). The second extension points that it is a plugin which is not shown under any media - but it can be called via plugin:// URI for the slideshow mode as VFS-folder.

Other than that, good work!

I am currently in some kind of "no time for opensource"-mode due to working on my own house but after that I can help with the needed changes if you agree in them.

regards,
sphere