[sldev] VWR-10311 Enabling lip sync by default

[Andromeda Quonset]

Jumping in here on this conversation......

I am finding it incredible that a new feature would be suggested, be 
enabled by default, and then have it decided to not have a way of 
disabling the feature in preferences because someone thinks 
preferences menu is so crowded.  If the lip sync "feature" MUST be 
added, to add it without some way of turning it off is 
unconscionable.  If the preferences menu is not the place to disable 
it, then where do you proposed disabling it?  Use a command line 
argument, perhaps?  Or maybe I have to place a secret text file in 
some directory you specify that contains a keyword like NO_LIP_SYNC 
?  Maybe it can be linked to a new ctrl-alt-shift-function key 
combination?  Or do you have a different idea?

Andro

At 08:53 AM 5/2/2009, you wrote:
>Gordon, let's look at history. Color TVs. In particular, evolution 
>from black and white TV to color TV. My grandma used to have a color 
>TV set. It had all kinds of controls that I cannot dream of having 
>today. The controls reflected the unanticipated technological 
>features that got injected into the TV set. You had Red Green Blue 
>controls (each with dials), Another color control, in passing, a 
>full blown equalizer for sound (let's not go there). For some people 
>color was a luxury...or even something to mess up the 'quality' of 
>the artistic experience. Evolution has a tendency to kill things 
>that are not needed. Today I find it hard to find a TV set with an 
>easily accessible control to turn off color.
>This is just an example. We can look at every device in the real 
>world and trace back the history of its interface and u will see 
>that. From cars, planes to anything...
>
>OK. This is my last word on this topic, promise.... we have already 
>discussed about face processing and its importance in immersion, 
>turn taking, expressiveness, footprint issues..and I think there are 
>good chances the right decision will be made.
>
>On Sat, May 2, 2009 at 8:49 AM, Ramesh Ramloll 
><<mailto:r.ramloll at gmail.com>r.ramloll at gmail.com> wrote:
>.
>
>On Sat, May 2, 2009 at 6:55 AM, Gordon Wendt 
><<mailto:GordonWendt at gmail.com>GordonWendt at gmail.com> wrote:
>Kent, then don't put it on by default.  You can't really have it 
>both ways, if you have it on by default then there has to be an easy 
>way to turn it on and off and advanced is not an easy way.  I agree 
>that prefs is already overcrowded but if you can't spare room in 
>prefs for new items then maybe STOP PUTTING NEW FEATURES ON BY 
>DEFAULT.  The caps are meant just to emphasize my point btw not to be rude.
>
>-Gordon
>
>
>
>On Sat, May 2, 2009 at 12:42 AM, Kent Quirk (Q Linden) 
><<mailto:q at lindenlab.com>q at lindenlab.com> wrote:
>Given the excessive complexity of the preferences dialog already, we 
>should take every opportunity to remove things from prefs, and there 
>should be a VERY high bar for adding anything to prefs. It's all too 
>easy for open projects to grow massive preferences systems and 
>configuration files because the outcome of most feature debates is 
>to compromise and add a preference.
>
>In this case, especially given that it already lives in Advanced, I 
>strongly recommend we not move it to Preferences.
>
>        Q
>
>
>
>On May 1, 2009, at 7:12 PM, Gordon Wendt wrote:
>
>No no and no, if it's optional then by all means hide it in advanced 
>but if you have it switched on by default you have to have an easy 
>way to turn it on and off which means the preferences, otherwise 
>don't turn it on by default.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20090502/42ae8125/attachment.htm