[sldev] s/Second Life/Snowglobe/g

[Boroondas Gupte]

[Again from my list address ... sorry Dzonatas for the duplicate]
My two Linden cents to the bike shed inline ...

Dzonatas Sol schrieb:
> [...]With a variable name like VIEWERNAME, however, it is explicit to the 
> viewer and maybe with the render engine and network bundled together it 
> implies those also. What happens when one separates the viewer (UI) from 
> the render engine and network parts. What do we call the render engine 
> and network? Or perhaps the render engine and network is best known as 
> Snowglobe and viewer is a client of Snowglobe's render engine and 
> network? I hope you see this issue I bring up here.
>   
I see the issue, but I don't think it has to concern us just now: While
a separation of render engine, network parts and the rest of the client
(the UI) is something we should aim for, it won't happen soon enough to
not give us the time to think about the naming scheme for these
components then. Already introducing the name tags for that scenario
might not be worth it, because

    * the clientvi might be separated into different components than
      we'd think today.
    * if there are several nametags that evaluate to the same value
      until such a separation, some of the tags will have been used
      wrongly once we're ready to introduce new names for the single
      components, so we would have to look at those strings again anyway
      before changing the tags' value.
    * While after a clean separation, some components might deserve own
      names, some of these names might never or very seldom be shown to
      the end user. (Ask some not-so-technical firefox users if they
      know what 'Gecko' or 'XULRunner' are ...)

> Maybe the best way to think of it is in Debian terms. What if (in Debian 
> world), the render engine and network code is distributed as 
> libsnowglobe.so and the viewer (UI) that loads libsnowglobe is 
> distributed as.... as what?  Snowglobe also? If this is fine with 
> everybody then ok!
>   
I think the name of the current render engine is "Windlight", so if it
is still the 'same' once it's been separated out, that'd probably be the
name for the component, too. But as long as Snowglobe is delivered as a
monolithic product, we won't have to care.
> If you think it needs more thought than that, maybe there needs to be 
> [RENDERNAME], [NETWORKNAME], [SERVERNAME], or something else that is not 
> bundled into VIEWERNAME that would work when there is no UI code (i.e. 
> just the shared library for a render engine and network code).
>   
The separation of which there should be taken care of soon in respect to
naming is the one on the server side (Agent Domain and Region Domain),
because that's something that's already being worked on. Though, as this
shouldn't have much impact on the client side strings, we should be able
to move on independently of that development.
> Cache will be cleared after you restart Rosebud
>   
:-)

Will you be able to restart Rosebud without also restarting Snowglobe?
> Rob Lanphier wrote:
>   
>> ...
>> Here's my thinking on how to tackle this.  Let's do the least disruptive
>> thing for now, which is to replace the instances of [SECOND_LIFE] in the
>> "Viewer" category with [VIEWERNAME], and then make
>> [VIEWERNAME]="Snowglobe"  Since  we're not likely to change the "Second
>> Life" string for those in this release, we can leave the others
>> "SECOND_LIFE" for now.  There's a lot of bikeshed arguments about what
>> to name the other categories, but it'll be more obvious not only what to
>> name the new token but where it should be sourced from at the time that
>> we're ready to change those to other values.
>>
>> Sound reasonable?
>>
>> Rob
Sounds reasonable to me.

cheers
Boroondas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20090521/b69ea56e/attachment.htm