[dj_gerbil]

Read the wiki pages on setting up a pluginsource. There's also detailed info on the exact form of addon.xml. A couple of obvious things wrong:

1. xbmcaddon.getSetting should be used rather than xbmcplugin.getSetting.
2. you need the xbmc.addon.metadata extension point for your summary.

Cheers,
Jonathan

Not sure I'm understanding you correctly, but is this a bit more like it??

Code:

<?xml version="1.0" encoding="UTF-8"?>
<addon
  id="tvc.plugin"
  version="1.2.3"
  name="TVCatchup"
  provider-name="DJ_Gerbil and the guys at TVC">
  <requires>
    <import addon="xbmc.gui" version="2.11"/>
  </requires>
  <extension
    point="xbmc.python.pluginsource"
    defaultresolution="720p"
    defaultresolutionwide="720p"
    library="default.py"
    debugging="false"/>
  <extension point=""xbmc.addon.metadata"" >
    <summary>TVCatchup plugin for XBMC</summary>
    <description>This plugin allows UK users to view free-to-air channels on XBMC courtesy of TVCatchup.com</description>
    <disclaimer>This plugin is provided as is. Although all attempts will be made to help resolve issues, no promises can be made.</disclaimer>
    <platform>all</platform>
    <provides>video</provides>
  </extension>
</addon>

[jmarshall]

You're definitely on the right track, but defaultresolution etc. is meaningless for a pluginsource. See the wiki pages on the exact syntax - there's also XML schemas to use for validation of the XML if you like (though for these it shouldn't really be necessary).

Cheers,
Jonathan

[dj_gerbil]

Jonathan, has xbmcplugin been completely replaced by xbmcaddon.Addon or is it just for the settings?

[dj_gerbil]

Bump.. Calling Mr. JMarshall

[jmarshall]

No - xbmcplugin still has the plugin-specific stuff.

For settings and strings however, you should use the xbmcaddon as it's more efficient.