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
On Tuesday, May 22, 2012, Philipp Temminghoff <
[email protected]> wrote:
> agreed. especially because the users will have the possibility to
discover all the brand new options while setting the skin up.
> it´s really almost fun to set 3.0 up. pretty much everything is wysiwyg,
no endless radiobutton lists and we do not have one single scrollbar for
lists with custom content for example.
>
> cheers
> phil65
>
> On May 22, 2012 3:30 AM, ronie <[email protected]> wrote:
>>
>> after reading todays discussion in #xbmc, i'd like to add my voice to it
>> as well...
>>
>> if i understand correctly, the main hurdle is the fact all skin settings
>> get reset when a user receives the update
>> and we feel this should, preferably, be avoided at all costs.
>> furthermore, shouldn't there be any way to avoid it, we would only allow
>> this to happen on major XBMC releases.
>>
>>
>> well, in all fairness, i don't think we can expect major skin updates to
>> coincide with XBMC releases.
>> in a perfect word they would, but since we're all working on this in our
>> spare time, things may not always line up the way we would like to.
>>
>> so what basically happens when a user receive the skin update?
>> they get presented with a new and shiny interface, that's still very
>> much recognizable as being Aeon Nox.
>> the only things that's needed for the end-user is to reconfigure their
>> personalized skin settings, if any.
>>
>> it's not like it we leave them with a broken skin or anything like that.
>> so nothing life-threatening if you ask me and also no animals were
>> harmed during the production of Aeon Nox 3.
>>
>>
>> just some food for thought.
>>
>>
>> cheers,
>> ronie
------------------------------------------------------------------------------
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
