[opensource-dev] Possibility to revert UI changes on snowstorm?

miss c miss_c_27 at yahoo.com
Tue Sep 21 14:05:26 PDT 2010

The point is people do not like change.  I love the new UI and to assist people 
with making that change I have been working today on making the UI look similar 
to the old one.  Such a coincidence this was brought up.  Its going to be the 
same color scheme with a few shiny upgrades to make it look more state of the 
art.  See link...  


From: Mike Monkowski <monkowsk at fishkill.ibm.com>
To: Ponzu <lee.ponzu at gmail.com>
Cc: opensource-dev at lists.secondlife.com
Sent: Tue, September 21, 2010 2:40:47 PM
Subject: Re: [opensource-dev] Possibility to revert UI changes on snowstorm?

I don't know what a model-view-controller approach is, but if you say it 
adds an extra layer of abstraction, then it doesn't matter anyway.

The UI is defined in XML and so is called XUI.  Admiral Admiral and I 
wrote some patches that, among other things, let you instantiate a 
floater from XML on the fly so that you could edit XML and reload 
immediately to see the effect of your changes.  See VWR-10924. 
Unfortunately the 2.x changes stomped all over the code affected by the 
patches and made it incompatible.

1.x was starting to implement callback functions that could be 
referenced by name rather than hardcoded as part of the floater 
initialization routine.  That was a good step toward being customizable. 
  I think there were some people in Linden Lab that may have been headed 
in that direction.

It's not "really hard."  It's just a matter of priorities.


Ponzu wrote:
> On Tue, Sep 21, 2010 at 2:51 PM, Daniel Smith <javajoint at gmail.com 
> <mailto:javajoint at gmail.com>> wrote:
>     +1 for customization.
> An effort to merge the 1.x and 2.x UI into a viewer with a highly 
> customizable interface might be fun.  At some point, I could even see 
> the Lindens being officially tasked with that effort.  For right now, it 
> is unlikely to be the Lindens who lead that way.
> Could you break the Viewer into two parts, the innards and then UI.  
> Sort of a model-view-controller approach?  Make the View a separate 
> process perhaps, that talks to the controller-model?  That might be 
> useful to people who want SL on their iPhone 8-)
> Sounds really hard to me, plus the extra layer of abstraction will 
> contribute to lag.  (Imagine a graphics engine that creates a movie 
> file, and then streams that to your phone).

Policies and (un)subscribe information available here:
Please read the policies before posting to keep unmoderated posting privileges

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/opensource-dev/attachments/20100921/8d2a6127/attachment-0002.htm 

More information about the opensource-dev mailing list