???? there is no wrong or right on both opinions. You have to respect skin author's decision if he decides to require re-setting and on the other side you have to consider users disappointment (and blame on) when they will see favorite skin settings disappears. The important thing is how this will affect users?.
In my opinion.... NOT AT ALL. IMO... if you decide to use a kind of skin that requires an hour of customization to use all skins futures then you don't mind to do it again once in a while. Cheers Nessus -------------------------------------------------- From: <[email protected]> Sent: Tuesday, May 22, 2012 12:09 PM To: <[email protected]> Subject: Re: [Xbmc-addons] [GIT PULL] Aeon Nox 3.0.0 > There is no nice solution for this problem, IMHO. > > Alternatives would be: > > - Keep a version in main repo as is. Offer new version from private > repository only > - Change skin name to Aeon Nox 3 and push it as "separate skin" leaving > existing one as is > - Bump GUI requirements and force pre-Frodo XBMC builds only > > Not very nice, right? > > I would respect skin author's decision if he decides to require re-setting > of the skin. Those are not XBMC settings but skin specific ones after all. > > He will probably need to deal with lots of users asking "what happened?" > in forum and if he decided to go through that than it is probably because > update is worth while and there was not other sane way to do it. > > Pedja > > ----------------------------- > > From: Martijn Kaijser <[email protected]> > Subject: Re: [Xbmc-addons] [GIT PULL] Aeon Nox 3.0.0 > Date: 22. kv?tna 2012 7:36:03 GMT+02:00 > To: Philipp Temminghoff <[email protected]> > Cc: "[email protected]" > <[email protected]> > > > So this means that any skin that has done some code and feature > improvement all in the benifit of the user will have to wait till Frodo is > released? Some where next year perhaps. > > I do understand the point of view that it can be confusing that all of a > sudden some customization has been reset. But be honesed, a user that > installs a skin other than the default one and then tweaks it will usually > also love new shiny features. Getting things back how you wanted perhaps > takes an hour with the new layout for regular users. > > If you don't want a user to suddenly have something change the auto update > should be turned off by default and a huge warning sign if they recieve an > update 'this update might screw up your tweaks'. > > If you do deside to not allow 3.0 to be added it would discourage the > skinners to push xbmc skinning to the limits cause they can only update > once a year. > Getting current one marked broken and add a new skin id doesn't sound like > a good idea either. Then you could allow modded versions as well. > > Just my humble point of view. > > Perhaps other skinners would like to give their thoughs? > > Regards, > Martijn ------------------------------------------------------------------------------ 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
