I think it's pretty clear LL will broach no more discussion on this
matter, as the only people complaining are "non contributors" -- as
clear a statement yet that realXtend and OpenSim are not considered
contributions to SL.
As far as I'm concerned, this is a complete FUD own-goal, and
realXtend n
In the list I made, that would be for the wearer only -- not the creator.
There are:
(A) creators of the layers
(B) creator of the outfit list.
(C) wearer of the outfit
By default, (B) & (C) are the same -- the wearer.
(A) is able to supply a outfit list to help suggest layer order, but it
does
That's actually what I would like to avoid, specifically. That forces
the creator to continue to dictate whether your underwear goes on top of
your pants or not. There's no added flexibility for the resident in that.
Here's why I'll be an advocate of just a few extra numbered layers on
top of t
An easier way may just to have list without ordinals. Example:
Outfit:
* Upper-body
** Jacket
** Shirt
** Undershirt
** upper-tattoos
** custom-upper-body-skin
** another-custom-upper-body-skin
* Lower-body
** Pants
** Underpants
** lower-tattoos
** custom-lower-body-skin
** another-custom-lower-
Actually, I don't mind "undies, shirt, and jacket." What I'm really
referring to is maybe 3 undies layers numbered 1,2,3. Creators can still
specify which of those three as they do now, but the user would choose
the 1, 2, 3 bit. The creator doesn't lose the ability to choose which of
the three
I like this idea a lot. While we're talking about about increasing
flexibility though, why have a low hardcoded limit to the number of layers?
The new tattoo and alpha layers are great, but what comes next, and how
long do we keep hardcoding more specific layers? If someone wants to layer
on ten
Nyx,
Oh, I actually do have one functionality idea / request: rather than
allowing the creator to dictate the clothing layer of a wearable, can we
allow the wearer themselves choose where it goes? I can't tell you how
many times I've had to not wear something because the original creator
did
I'm a little unsure what the tiny robot means about the appearance
floater being all yucky
We'll still need it for the shape sliders, will we not? After all, it's
incredibly convenient to just put it where you want it in order to
reduce the mouse-miles involved. Sticking it ALL on the right
I threw a copy of my haphazard Snowglobe 2 PowerPC build notes onto
https://blogs.secondlife.com/message/148902#148902 - maybe they'll be
useful for someone with the time to flesh it out into something
suitable for public distribution. Look at cache and logging too, for
opportunities to skip /tmp c
On Wed, 24 Mar 2010 18:11:03 -0500
Michael Dickson wrote:
> On Wed, 2010-03-24 at 22:58 +, Tayra Dagostino wrote:
> > On Mon, 8 Mar 2010 09:39:00 +0100
> > Lance Corrimal wrote:
> >
> > > Anyways, shouldn't SLPlugin exit when it is done doing what it
> > > thought it should be doing?
> >
>
On Wed, 24 Mar 2010 18:11:03 -0500, Michael Dickson
wrote:
> On Wed, 2010-03-24 at 22:58 +, Tayra Dagostino wrote:
>> On Mon, 8 Mar 2010 09:39:00 +0100
>> Lance Corrimal wrote:
>>
>> > Anyways, shouldn't SLPlugin exit when it is done doing what it
>> > thought it should be doing?
>>
>> ins
On Wed, 2010-03-24 at 22:58 +, Tayra Dagostino wrote:
> On Mon, 8 Mar 2010 09:39:00 +0100
> Lance Corrimal wrote:
>
> > Anyways, shouldn't SLPlugin exit when it is done doing what it
> > thought it should be doing?
>
> installed and configured Pulseaudio
> now only ONE SLPlugin thread execut
On Mon, 8 Mar 2010 09:39:00 +0100
Lance Corrimal wrote:
> Anyways, shouldn't SLPlugin exit when it is done doing what it
> thought it should be doing?
installed and configured Pulseaudio
now only ONE SLPlugin thread executed, with very low processor
usage.
___
As an epileptic, let me do say that the viewer has caused "auras" (sort
of a buzzing in my head that warns me of an impending seizure) and has
caused migraines, particularly due to the GL rendering area getting
"squashed" by the sidebar. It's also very disorienting to people.
On Wed, 2010-03-24
On Wed, Mar 24, 2010 at 2:57 AM, Joe Linden wrote:
>
> There is no "catch 22" here. No "overstepping", and no rocket science.
> The terms of the GPL are clear and well understood. The arguments around
> clauses 11 and 12 of the GPL are completely baseless.
Here are GPLv2 clauses 11 and 12, J
It's basically the same as seasickness, or motion sickness in general...
you feel sick, because your eyes and your sense of balance tell your brain
different things. that's why a cure for seasickness is being in a spot on the
boat where you can see the horizon... so that your brain realizes that
Just a reminder that this page exists even if
it hasn't been updated since 1 month
https://wiki.secondlife.com/wiki/FLOSS_community_concerns_about_the_Linden_Lab_policy_on_third-party_viewers
It seems the best place where to point people at,
and I'd suggest to developers and open source supporte
Sounds like Virtual Environment Sickness (a perceptual dissonance malady
somewhat akin to seasickness). While it affects about 30% of the
population from the USAF studies that I've seen, I haven't read anything
to suggest that either the SL viewer or LCD monitors affect the overall
prevalence of th
Not to disagree with the entirety of your rant, but this bit seems
completely off the wall.
On 2010-03-23, at 21:39, Jonathan Irvin wrote:
> Not to be rude, but if people are getting vertigo, epilepsy, etc.
> from SL...viewer 2.0 isn't going to make a difference. Viewer 1.23
> would have th
Am Mittwoch, 24. März 2010 03:57:17 schrieb Joe Linden:
> Let me take just one more crack at explaining the situation here, then I'll
> let the TPV Policy document stand on it's own.
Joe,
if the policy does not MEAN "you take all responsibility", why does it SAY so?
and... if you (LL) don't WANT
@Darmath
You wrote you are a law student and this is certainly a very interesting
subject to explore, without getting really involved. Unless you make your own
viewer.
I think we agree here about the underlying common sense and the good intentions
of everyone in this discussion. I believe we c
21 matches
Mail list logo
