On 20-05-12 07:49, Cory Fields wrote:
> On Sun, May 20, 2012 at 1:46 AM, Jezz_X<[email protected]>  wrote:
>> I honestly don't think that the people who bother to go in and change
>> skin settings would care about going in to change them again as long
>> as it doesn't happen every week.  Most normal people probably didn't
>> even bother to change any
>>
>> On Sun, May 20, 2012 at 3:21 PM, Big Noid<[email protected]>  wrote:
>>> It's needed because of the way we converted existing radiobuttons to normal
>>> buttons with 3 or more states that depend on having a setting or not
>>> (conditional onclicks). I can imagine in some cases if there are existing
>>> settings combination of previous separate radiobuttons, we can have
>>> untoggable buttons. Other then that some settings have been inverted,
>>> variables have been renamed etc. Also the Home window has a new structure
>>> where old background and widget settings were going to get lost anyway. So
>>> it's going to be needed for users to set most stuff up again anyway, even
>>> without resetting the settings, the only problem I see with this is that a
>>> rollback of previous version does not restore the guisettings for the skin.
>>>
>>> Cheers,
>>>
>>> Rutger
>>> 2012/5/20 Cory Fields<[email protected]>
>>>> On Sat, May 19, 2012 at 1:50 AM, Big Noid<[email protected]>  wrote:
>>>>> Please see updated rev below. Some last minute fixes/ translation
>>>>> additions.
>>>>>
>>>>> *addon - skin.aeon.nox
>>>>> *version - 3.0.0
>>>>> *url - git://github.com/BigNoid/Aeon-Nox.git
>>>>> *revision - 525715f66a850673d9d5d02aec713a8d1675a3d8
>>>>>
>>>>> *branch - eden
>>>>> *xbmc version - eden
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Rutger
>>>>>
>>>>> 2012/5/18 Big Noid<[email protected]>
>>>>>> *addon - skin.aeon.nox
>>>>>> *version - 3.0.0
>>>>>> *url - git://github.com/BigNoid/Aeon-Nox.git
>>>>>> *revision - 9f6de34e4d0ab8a1736d077b7dd55655a5da2924
>>>>>> *branch - eden
>>>>>> *xbmc version - eden
>>>>>>
>>>>>> This is basically a new iteration of the skin, so its probably better
>>>>>> to
>>>>>> review this as a new entry rather then comparing to the one currently
>>>>>> in
>>>>>> repo.
>>>>>>
>>>>>> Changelog is here:
>>>>>> https://github.com/BigNoid/Aeon-Nox/blob/eden/changelog.txt
>>>>>>
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Rutger
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> 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
>>>>>
>>>> What's up with the settings being lost? As a user I'd be pretty pissed
>>>> if I got an auto-update that changed the way everything looks.
>>>>
>>>> I'm tempted to say that's a no-go for a stable repo. What's the hurdle
>>>> for keeping the settings? Maybe we can help out here.
>>>>
>>>> Cory
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> 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
>>>
> That would be OK, if they had some kind of notice/explanation. As it
> is now, one minute they'll be using what they're next to, the next,
> the settings are changed with no warning.
>
> And I'm not sure about that argument, Jezz. If not many people change
> the settings, then why should we bother sending out an update for
> changing settings? :p
>
> Cory
>
> ------------------------------------------------------------------------------
> 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

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

Reply via email to