[sldev] Re: Dazzle / Windlight merge?

[Tateru Nino]

That's good feedback for us - and I must admit that as far as the Dazzle 
project goes, I cannot help but be pleased about a more customizable, 
skinnable, themeable user interface (actually for my day to day work, 
I'd love to just hide 90% of the UI).

That work isn't easy to see, of course. There's a fair bit of WYSIWYG 
thinking when it comes to Dazzle (not on your part - on ours). The only 
part most of us really see is the new skin. Some of us like it. For 
others it is eye-watering.

A changelog about what's going on under the hood that to enable and 
extend those appearance changes - now that might help show off that the 
focus isn't really on a single set of  surface alterations. Just a 
suggestion.

Ramzi wrote:
> Thanks Harold, it's an important point-- the Dazzle project was the 
> first comprehensive change, and also a "proof of needed abstraction" 
> to the UI code.  Dazzle is what identified, for example, that the 
> color for Pie Menus shouldn't need to be hardcoded to the same color 
> as the MenuItemDisabledColor.  Or that we'd like to separate the icon 
> from its background art(or how about a gradient?) in sortable column 
> headers.
>
> I've seen the internal team take the feedback from the First Look very 
> seriously, every week, from the issue tracker & office hours.  Yes, 
> the further UI abstraction work and persistent skin installs aren't 
> complete yet; but we've made a heartfelt attempt to update the wiki 
> with real plans for [[Skinning]] this quarter & beyond, aggregate 
> issues in VWR-6027, document some current capabilities in a [[Skinning 
> HowTo/Basics]]*, and (hopefully) see more resident links to their 
> darker/classic skin creations in the meantime.
>
> W/r/t optional viewers -- I can say that Linden Lab heard great 
> Resident feedback recently about the advantages to having 2 supported 
> viewer versions available whenever possible.  Listening to that 
> feedback is what led to making 1.19.0.5 the minimum version /only 
> after/ 1.19.1 was released about a week ago.
>
> -Ramzi
> [[User:Ramzi Linden]]
>
>
> *this page can't be seen just yet, because wiki.secondlife.com is 
> having auth problems as I type this. sigh.
>
>
>
> Harold Brown wrote:
>> [and again for the entire list]
>>
>> There's a bit more to Dazzle then just changing the graphics.  There
>> were several internal changes that had to be made to allow some hard
>> coded colors to be changed as well as to allow for images to be loaded
>> differently.
>>
>> No I don't like the bright blue Dazzle graphics, and I did recolor
>> everything to be darker to fit my taste.  Once the 1.20 RC's are
>> available, even if there is not native skin support, I will write an
>> external program to allow for different UI sets at the very least.
>>
>> The external program would only be a stop-gap solution until true
>> "theme / skin" support could be added to the client.
>>
>> On Tue, Apr 8, 2008 at 7:31 PM, Tateru Nino <tateru.nino at gmail.com> 
>> wrote:
>>  
>>> Thomas Grimshaw wrote:
>>>    
>>>> Adric R wrote:
>>>>
>>>>      
>>>>> I really hope this 1.20 release isn't mandatory. It looks (at 
>>>>> least from
>>>>>         
>>> this outside observer) like as with the chatterbox, LL is going to 
>>> wait for
>>> resident outrage again before addressing problems members of the 
>>> community
>>> saw and were vocal about in advance: in this case, the lack of any 
>>> means for
>>> skin switching.
>>>    
>>>> Out of curiosity,
>>>>
>>>> Does anyone in this list like Dazzle ?
>>>>
>>>>
>>>>       
>>> Perhaps not in this list - but I have met two residents who are looking
>>> forward to it as is.
>>>
>>>
>>>
>>> _______________________________________________
>>> Click here to unsubscribe or manage your list subscription:
>>> /index.html
>>>
>>>     
>> _______________________________________________
>> Click here to unsubscribe or manage your list subscription:
>> /index.html
>>   
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
>