What is the best way to maintain two version of a plugin, where basicly
only the addon.xml will differentiate? Branching?
I will change the things you requested - hopefully tonight - and then push
v1.1.1 for Eden.
On 25 April 2012 08:53, Arne Morten Kvarving <[email protected]>wrote:
> On Tue, Apr 24, 2012 at 1:27 PM, Tim Steinmetz <[email protected]> wrote:
> > * addon - plugin.audio.di.fm
> > * version - 1.1.0
> > * url - git://github.com/Bitcrusher/Digitally-Imported-XBMC-plugin.git
> > * revision - 6b54c5b865
> > * branch - master
> > * xbmc version - dharma
>
> apart from the xbmc version being wrong (not pulling anything new into
> dharma, certainly not pulling anything at xbmc.python 2.0 into
> dharma),
>
> 1) don't write to getaddoninfo('path') - you can write to
> getaddoninfo('profile')
> 2) localize on-screen strings
> 3) language subdirs should be properly cased
> language/English/strings.xml not language/english/strings.xml
>
> cheers
>
> spiff
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Xbmc-addons mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbmc-addons
