Second Life Wiki - User contributions [en]

Talk:Web Browser

2010-05-12T11:52:03Z

Vernes Veranes: /* change in browser behaviour between old en v2.0 */

== change in browser behaviour between old en v2.0 ==

When llLoadUrl is executed, when opening the webpage, it is opened twice accourding to the webserver logs.
Unsure if this happens during actual viewing, or if the popup in teh interface does some sort of pre-caching.
I thought I'd make a note of this since one of my own products has to be rewritten.
I can imagine this affecting others too. --[[User:Vernes Veranes|Vernes]] 10:08, 11 May 2010 (UTC)
: Further tests show that the two http-gets are preformed when the browser actually shows the page. I was suspecting the loadurl pop-up might be trying to pre-load the page incase it could be previewed (thumbnail preview). Still no idea why the broser does 2 http-gets though. --[[User:Vernes Veranes|Vernes]] 11:52, 12 May 2010 (UTC)

Talk:LlLoadURL

2010-05-11T10:12:30Z

Vernes Veranes: change in behaviour internal browser

== change in behaviour internal browser ==

I'd like to point out https://wiki.secondlife.com/wiki/Talk:Web_Browser concerning the change in browser behaviour.
I noticed the webbrowser in viewer 2.0 somehow views a page twice accourding to the webserver's log.
Also, is a link from this page to the webbrowser page usefull? --[[User:Vernes Veranes|Vernes]] 10:12, 11 May 2010 (UTC)

Talk:Web Browser

2010-05-11T10:08:16Z

Vernes Veranes: change in browser behaviour between old en v2.0

User:Nyx Linden/Office Hours Agenda

2010-02-03T20:10:06Z

Vernes Veranes:

==Nyx Linden's Office Hours Agenda==

Office hours are on Wednesdays at Noon in Pacific time (SL standard time) located in Borrowdale at: http://slurl.com/secondlife/Borrowdale/74/217/32

Topics are focused on avatars, content creation efficiency, content creation tools and methods, rendering issues, and many related random topics.

Please add topics for discussion / agenda items to the end of the list below prior to 11:50 AM. Priority will be given to topics that are posted in advance and are relevant to the goals of the office hour. Feel free to include relevant links to JIRA or wiki pages. Contact Nyx Linden if you are unsure if your topic is relevant or appropriate.

Archived agendas can be found at the [[User:Nyx_Linden/Office_Hours_Agenda_Archive|agenda archive]].

Next meeting scheduled for: February 03, 2010.

===Agenda===

==February 03, 2010==
# Firefly - are you involved with this Nyx? Can you tell us anything? - Xugu Madison
# Throwing an idea into the group: [[User:Vernes_Veranes/Static_Content_Cache|Static Content Cache]]

User:Vernes Veranes/Static Content Cache

2010-02-03T19:46:06Z

Vernes Veranes: Created page with '== Static Content Cache == Additional caching procedure, implemented on server- as well as viewer-side. Idea is focused on increasing performance for island-sims, mainland imple...'

== Static Content Cache ==

Additional caching procedure, implemented on server- as well as viewer-side.
Idea is focused on increasing performance for island-sims, mainland implementations not worked out.

Objects can be tagged as being "static".
''Example: Roads, Walls, Floors, Signs''

'''Assumtions:'''
Cache stores not only prim definitions, but also the uuid of the prim.
Servers can handle unsupported messagetypes.

'''Server:'''
The sim owner tags objects he/she deems to be static accordingly.
This will result in a list of uuid's that get collected under a common timestamp along with the sim/region the list is associated to.

'''Client:'''
I've been told clients do not fare well when unsupported message are presented.

Clients that support this feature will need to request this information from the server.
This request contains optionally the timestamp of the previously received uuid-list, or is kept empty.
In the case where an timestamp is included, the server checks if it matches with the current list.
If it does match, it will only reply with an acknowledgement.
If it doesn't match it will reply with a timestamp followed by a list of uuid's
This list is stored locally.
The timestamped list of uuid's serves as an exclusion list for the pruning mechanism the cache currently applies.

This list is stored indefinitely or until one of the two events occur:
# The sim owner manipulates an object (or any of its sub-parts), causing the sim to drop the timestamped entity.This causes the server to drop it's timestamped list, and responds negative to the client's request for a timestamped list for that sim/region.
# The User manually forces its viewer to dump the timestamped list for a certain sim/region, no longer excluding the associated cache from the pruning mechanism.

'''Expected result:'''
When a viewer connects to a sim/region of which it has a timestamped uuid list, it will also have all its cached data.
Cached data doesn't have to be received by the sim.
The assumption is that locally stored content loads faster into the scene then streamed content.
Time waiting for the whole scene to load through streaming is made shorter.
The user is able to start navigating sooner after arriving.

The server could skip 90% of the time spend streaming static content to viewers that already have the data.

'''Additional:'''
Is it possible to insert premade cache-files?

User:Vernes Veranes

2010-02-03T19:37:53Z

Vernes Veranes:

{{SL-hCard|name=[[User:Vernes Veranes|Vernes Veranes]]
|uuid=33345f37-bfc0-4599-ac80-ac9ca77129e2
|mode=size
|photo_x=200
|photo_y=200
|image=
|rezday=01/01/2000
|rezdayISO=2000-01-01
|account=
|partner=
|about=
|achieve=
|links=
}}
This profile is still under construction.

Pet bugs:
* {{jira|VWR-1171}} - Velocity interpolation causes weird physical behaviour client-side - {{User|Vernes Veranes}}

[https://wiki.secondlife.com/w/index.php?title=Special%3AAllpages&from=&namespace=10 Full list of existing templates]

Current project:
* Dom API specificly for xml generation, written in sls.
* <del>Trying to mimic php's implementation (using objects as arguments of function).</del>
* linkedmessage based protocol for inter script communication

Links:
[http://www.slnn.com/article/virtualcomex-laval/ I was qouted]

[http://wiki.secondlife.com/wiki/LSL_Script_Memory/ LSL Script Memory]

[[llMessageLinked]](integer linknum, integer num, string str, key id);

{|
|Host Script
|action
|Function script
|-
|Hello
|action
|
|-
|
|return
|Yes?
|}

Where are my borders?

{|style={{Prettytable}}
!Host Script
!action
!Function script
|-
|Hello
|action
|
|-
|
|return
|Yes?
|}

THERE are my borders!

[[User:Vernes_Veranes/Static_Content_Cache]]

User:Nyx Linden/Office Hours Agenda

2010-01-20T18:03:43Z

Vernes Veranes: grr, can't be present, removed entry

==Nyx Linden's Office Hours Agenda==

Office hours are on Wednesdays at Noon in Pacific time (SL standard time) located in Borrowdale at: http://slurl.com/secondlife/Borrowdale/74/217/32

Topics are focused on avatars, content creation efficiency, content creation tools and methods, rendering issues, and many related random topics.

Please add topics for discussion / agenda items to the end of the list below prior to 11:50 AM. Priority will be given to topics that are posted in advance and are relevant to the goals of the office hour. Feel free to include relevant links to JIRA or wiki pages. Contact Nyx Linden if you are unsure if your topic is relevant or appropriate.

Archived agendas can be found at the [[User:Nyx_Linden/Office_Hours_Agenda_Archive|agenda archive]].

Next meeting scheduled for: January 19, 2010.

===Agenda===

==January 19, 2010==
# http://jira.secondlife.com/browse/MISC-3309 YAY! Bear?!
# How are multi level avatar textures coming together? When we can start using them? Is there going to be other special textures available beyond invisiprim replacement? Shininess map? Bumpmaps?
# Any official information about mesh imports? When we get them? How mesh LODs are handled?
# When we get official shadow support?

User:Nyx Linden/Office Hours Agenda

2010-01-20T17:49:32Z

Vernes Veranes: /* January 19, 2010 */

==Nyx Linden's Office Hours Agenda==

Office hours are on Wednesdays at Noon in Pacific time (SL standard time) located in Borrowdale at: http://slurl.com/secondlife/Borrowdale/74/217/32

Topics are focused on avatars, content creation efficiency, content creation tools and methods, rendering issues, and many related random topics.

Please add topics for discussion / agenda items to the end of the list below prior to 11:50 AM. Priority will be given to topics that are posted in advance and are relevant to the goals of the office hour. Feel free to include relevant links to JIRA or wiki pages. Contact Nyx Linden if you are unsure if your topic is relevant or appropriate.

Archived agendas can be found at the [[User:Nyx_Linden/Office_Hours_Agenda_Archive|agenda archive]].

Next meeting scheduled for: January 19, 2010.

===Agenda===

==January 19, 2010==
# http://jira.secondlife.com/browse/MISC-3309 YAY! Bear?!
# How are multi level avatar textures coming together? When we can start using them? Is there going to be other special textures available beyond invisiprim replacement? Shininess map? Bumpmaps?
# Any official information about mesh imports? When we get them? How mesh LODs are handled?
# Idea: Improved experience through static content indication and selective permanent caching.

PRIM FLEXIBLE

2010-01-13T00:08:45Z

Vernes Veranes: softness goes from 0 to 3, not 4

<onlyinclude>{{#if:

{{#vardefine:flexible_const|{{LSL Const|PRIM_FLEXIBLE|integer|21|c=Used to {{GetSet|{{{1|}}}|get|set|/}} the prim's flexible configuration}}}}


{{#vardefine:p_flex_float_desc|ranges from 0.0 to 10.0}}
{{#vardefine:p_flex_gravity_desc|ranges from -10.0 to 10.0}}
{{#vardefine:p_force_desc|}}
{{#vardefine:p_softness_desc|ranges from 0 to 3}}

}}</onlyinclude>{{#if:

{{LSL_Function/boolean|boolean}}

}}{{LSL Constant
|name=PRIM_FLEXIBLE
|type=integer
|value=21
|desc=Used to get or set the prim's [[flexible]] configuration.
|pa={{LSL Constant/List|i_front=[ {{#var:flexible_const}}, |i_end= ]
|text=When used with [[llSetPrimitiveParams]] & [[llSetLinkPrimitiveParams]]
|toc=llSetPrimitiveParams
|i1_type=integer|i1_name=boolean
|i2_type=integer|i2_name=softness
|i3_type=float|i3_name=flex_gravity|i3_disp=gravity
|i4_type=float|i4_name=flex_float|i4_disp=friction
|i5_type=float|i5_name=flex_float|i5_disp=wind
|i6_type=float|i6_name=flex_float|i6_disp=tension
|i7_type=vector|i7_name=force
}}
|pb={{LSL Constant/List|i_front=[[llGetPrimitiveParams]]([ {{#var:flexible_const}}|i_end= ]);|
|r_front=Returns the list [ |r_end= ]
|toc=llGetPrimitiveParams
|text
|r1_type=integer|r1_name=boolean
|r2_type=integer|r2_name=softness
|r3_type=float|r3_name=flex_gravity|r3_disp=gravity
|r4_type=float|r4_name=flex_float|r4_disp=friction
|r5_type=float|r5_name=flex_float|r5_disp=wind
|r6_type=float|r6_name=flex_float|r6_disp=tension
|r7_type=vector|r7_name=force
}}
|examples
|constants=

|functions=
{{LSL DefineRow||[[llSetPrimitiveParams]]|}}
{{LSL DefineRow||[[llSetLinkPrimitiveParams]]|}}
{{LSL DefineRow||[[llGetPrimitiveParams]]|}}
|events=

|location
|cat1=Prim
|cat2
|cat3
|cat4
}}

Category talk:LSL Integer

2010-01-08T00:43:36Z

Vernes Veranes: /* Sub-classification Constants/Functions */ new section

Are these numbers correct? "values between −2,147,483,648 and +2,147,483,647" . And if they are why the difference between the figures? -- '''[[User:EddyFragment Robonaught|Eddy]]''' <sup><small>([[User talk:EddyFragment_Robonaught|talk]]|[[Special:Contributions/EddyFragment_Robonaught|contribs]])</small></sup> 17:30, 27 June 2009 (UTC)

:Aye correct as saved.

:This truth makes more visual sense in hex. A 32-bit two's complement integer is 0x0, or +0x1 thru +0x7FFFffff, or -1 thru -0x7FFFffff, or -0x80000000. In decimal, that is 0, or 1 thru 2147483647, or -1 thru -2147483647, or -2147483648. The assymetry comes from the zero: both positive integers and zero have the uppermost most bit of the 32 bits zeroed, so the list of positive values loses one element to make room for zero.

:A correspondingly counterintuitive result here is that negating -2147483648 has no effect (-2147483648 == ( 0 - -2147483648 ) == ( 2147483647 + 1 ) ). Ugly as all this is, it's less ugly than the known alternatives, such as the one's complement encoding that can have two zeroes: a positive zero and a negative zero. All that I'm saying here is the convention I remember learning years ago, I imagine LSL behaves this way at these limits, but I haven't tried to see yet ... -- [[User:Ppaatt Lynagh|Ppaatt Lynagh]] 18:10, 27 June 2009 (UTC)

::Thanx Ppaatt. I thought it might be a zero issue but didn't get as far as thinking that (of course) there would have to be (as you say) two zeros for the reach (both pos and neg) to be equal. "Positive Zero". Sounds like a good title for a science fiction novel. Cheers Ppaatt. -- '''[[User:EddyFragment Robonaught|Eddy]]''' <sup><small>([[User talk:EddyFragment_Robonaught|talk]]|[[Special:Contributions/EddyFragment_Robonaught|contribs]])</small></sup> 18:16, 27 June 2009 (UTC)

::In addition to (--2147483648 == -2147483648) so does (-1 * -2147483648). Everyone knows that 1/0 causes a fatal error in integer math but what few people know is that (-2147483648 / -1) does as well on x86 processors (modulo is equally affected). I have yet to find any mention of this on the internet (except where I have posted it), I found it by accident while exploring edge cases (it crashed the sim). In LSL we papered over the exception, any time you divide by -1 we just apply the "-" operator, and for modulo -1 we just return 0. -- '''[[User:Strife_Onizuka|Strife]]''' <sup><small>([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])</small></sup> 09:27, 29 June 2009 (UTC)

::: *insert foot in mouth* http://www.codeguru.com/cpp/sample_chapter/article.php/c11111__3/ -- '''[[User:Strife_Onizuka|Strife]]''' <sup><small>([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])</small></sup> 10:00, 29 June 2009 (UTC)

lolz (although not at the fact that you can do "Integer math". Now I have to relearn stuff *slumps*). -- '''[[User:EddyFragment Robonaught|Eddy]]''' <sup><small>([[User talk:EddyFragment_Robonaught|talk]]|[[Special:Contributions/EddyFragment_Robonaught|contribs]])</small></sup> 10:03, 29 June 2009 (UTC)

== Sub-classification Constants/Functions ==

I thought I'd take a quick peek at possible Integer-related Functions.
A sea of Constants greeted me. Is a Sub classification perhaps useful? --[[User:Vernes Veranes|Vernes]] 00:43, 8 January 2010 (UTC)

Talk:LlGetCameraPos

2009-11-08T01:31:33Z

Vernes Veranes: /* Range */

== Range ==

Are there any tests known about the behavior of this function at large distances? --[[User:Vernes Veranes|Vernes]] 01:31, 8 November 2009 (UTC)

Talk:LlGetCameraPos

2009-11-08T01:31:14Z

Vernes Veranes: Range

== Range ==

Are there any tests known about the behavior of this function at large distances?

Rotation

2009-10-11T13:38:54Z

Vernes Veranes: vPosRotatedOffset changed to vPosRotOffset

{{LSL Header|ml=*}}{{RightToc}}
==Rotation==
The LSL '''rotation''' type is one of several ways to represent an orientation in 3D. (Note that we try to write the type name in '''bold'''.)
It is a mathematical object called a {{LSLG|quaternion}}. You can think of a quaternion as four numbers, three of which represent the direction an object is facing and a fourth that represents the object's banking left or right around that direction. The main advantage of using
quaternions is that they are not susceptible to [http://en.wikipedia.org/wiki/Gimbal_Lock gimbal lock].
For the complex inner workings of quaternion mathematics, see {{LSLG|quaternion}}.
For a list of functions and events related to rotations see {{LSLG|LSL Rotation Synopsis}}.
There is also information about causing textures to rotate in {{LSLG|texture}}s.

==Other representations==
===Euler vector===
Another way to represent a 3D angle is using three numbers, <X, Y, Z>, which represent the amount which the object is rotated around each axis. This is used in the Edit window, for example, and is generally easy for people to visualize. It is easy to adjust the Rotation <x, y, z> numbers in the Edit window and see how the object behaves. Note that in the Edit window, the numbers are in degrees, that is, a right angle is 90.

In LSL, these three angles are expressed in [[radians]] instead of degrees, that is, a right angle is PI/2. (A radian is sort of a very fat degree.)
Note that these three numbers are a '''vector''' type and not a '''rotation''' type, though it can represent the same information. This is called the ''Euler'' representation of a 3D angle. In LSL the rotation around z is done first, then around y, and finally around x.

===FWD, LEFT, UP===
Another way to represent the same 3D angle is to use three vectors, showing what the front is pointing at (fwd), what the top is pointing at (up), and what the left side is pointing at (left). Actually, only two of the three are needed, because any two determines the third.

For good reasons, such as being able to easily combine rotations, the four number version, the '''rotation''', is better, though perhaps harder for a beginner to grasp. Fortunately it's very seldom necessary to do anything with the actual internal representation of ''rotations'' and there are functions for converting easily back and forth between the three LSL types, and between degrees and radians.

==Right hand rule==
In LSL all rotations are done according to the '''right hand rule'''. With your right hand, extend the first finger in the direction of the positive direction of the x-axis. Extend your second finger at right angles to your first finger, it will point along the positive y-axis, and your thumb, extended at right angles to both will point along the positive z-axis. When you're editing an object, the three colored axis arrows point in the positive direction for each axis (X: red, Y: green, Z: blue).

http://en.wikipedia.org/wiki/Right_hand_rule

Now, don't remove your right hand just yet, there is another use for it, determining the direction of a positive rotation. Make a fist with your right hand, thumb extended and pointing in the positive direction of the axis you are interested in. Your fingers curl around in the direction of positive rotation. Rotations around the X, Y, and Z axis are often referred to as Roll, Pitch, and Yaw, particularly for vehicles.

[http://en.wikipedia.org/wiki/Tait-Bryan_angles Roll Pitch Yaw]

== Combining Rotations ==
'
Suppose you have two rotations. ''r1'' is rotate 90 degrees to the left, and ''r2'' is rotate 30 degrees to the right. (Any rotations will work; these are just an example.)
You can combine ''r1'' and ''r2'' to make ''r3'' using the '''*''' operator. It doesn't really multiply them, it ''composes'' them.
<lsl>
rotation r3 = r1 * r2;
</lsl>
The result in this case is that ''r3'' means rotate 60 degrees to the left.

In other words, to combine '''rotations''', you use the '''multiply''' and '''divide''' operators. Don't try to use addition or subtraction operators on '''rotations''', as they will not do what you expect. The '''multiply''' operation applies the rotation in the positive direction, the '''divide''' operation does a negative rotation. You can also negate a rotation directly, just negate the s component, e.g. X.s = -X.s.

Unlike other types such as {{LSLG|float}}, the order in which the operations are done,
[http://en.wikipedia.org/wiki/Commutative non-commutative], is important.
The reason for this is simple: the order you do rotations in is important in RL. For example, if you had a dart with four feathers, started from rotation <0, 0, 0> with its tail on the origin, it would lie on the X axis with its point aimed in the positive X direction, its feathers along the Z and Y axes, and the axes of the dart and the axes of the world would be aligned. We're going to rotate it 45 degrees around X and 30 degrees around Y, but in different orders.

First, after rotating 45 deg around X the dart would still be on the X axis, unmoved, just turned along its long axis, so the feathers would be at 45 deg to the axes. Then rotating 30 deg around Y would move it in the XZ plane to point down 30 deg from the X axis (remember the right hand rule for rotations means a small positive rotation around Y moves the point down). The dart winds up pointing 30 deg down, in the same vertical plane it started in, but turned around its own long axis so the feathers are no longer up and down.

If you did it the other way, first rotating 30 deg in Y, the dart would rotate down in the XZ plane, but notice that it no longer is on the X axis; its X axis and the world's aren't aligned any more. Now a 45 degree rotation around the X axis would pivot the dart around its tail, the point following a 30 deg cone whose axis is along the positive world X axis, for 45 degrees up and to the right. If you were looking down the X axis, it would pivot from pointing 30 deg below the X axis, up and to the right, out of the XZ plane, to a point below the 1st quadrant in the XY plane, its feathers rotating as it went.

Clearly this is a different result from the first rotation, but the order of rotation is the only thing changed.

To do a constant rotation you need to define a '''rotation''' value which can be done by creating a {{LSLG|vector}} with the X, Y, Z angles in radians as components (called an Euler angle), then converting that to a '''rotation''' by using the {{LSLG|llEuler2Rot}} function. You can alternately create the native rotation directly: the real part is the cosine of half the angle of rotation, and the vector part is the normalized axis of rotation multiplied by the sine of half the angle of rotation. To go from a rotation to an Euler angle {{LSLG|vector}} use {{LSLG|llRot2Euler}}.

'''NOTE:''' angles in LSL are in radians, not degrees, but you can easily convert by using the built-in constants [[#RAD_TO_DEG|RAD_TO_DEG]] and [[#DEG_TO_RAD|DEG_TO_RAD]]. For a 30 degree '''rotation''' around the X axis you might use:

<div id="box"><div style="padding: 0.5em">
{| cellpadding=0 cellspacing=0
|- valign="top"
| style="white-space: nowrap" |rotation rot30X
| style="white-space: nowrap" |= [[llEuler2Rot]](<30, 0, 0> * [[DEG_TO_RAD]]);
||// convert the degrees to radians, then convert that [[vector]] into a rotation, rot30x
|- valign="top"
| style="white-space: nowrap" |[[vector]] vec30X
| style="white-space: nowrap" |= [[llRot2Euler]](rot30X );
||// convert the rotation back to a [[vector]] (the values will be in radians)
|}
</div></div>

== Differences between math's quaternions and LSL rotations ==

There are a few differences between LSL and maths that have little consequences while scripting, but that might puzzle people with prior mathematical knowledge. So we thought it would be good to list them here:

* In LSL, all quaternions are normalized (the dot product of '''R''' by '''R''' is always '''1'''), and therefore represent ways to rotate objects without changing their size. In maths, generic quaternions might be not normalized, and they represent ''affinities'', i.e. a way to rotate '''and''' change the size of objects.
* In LSL, the '''s''' term is the fourth member of the rotation: '''<x, y, z, s>'''. In maths, the '''s''' term, also called "real part", is written as the first coordinate of the quaternion: '''(s, x, y, z)'''.
* Multiplication is written in reverse order in LSL and in maths. In LSL, you would write '''R * S''', where in maths you would write '''S . R'''.

== Order of rotation for Euler Vectors ==

From the above discussion, it's clear that when dealing with rotations around more than one axis, the order they are done in is critical. In the ''Euler'' discussion above this was kind of glossed over a bit, the individual rotations around the three axis define an overall ''rotation'', but that begs the question: What axis order are the rotations done in? The answer is '''Z, Y, X''' in global coordinates. If you are trying to rotate an object around more than one axis at a time using the ''Euler'' representation, determine the correct ''Euler'' {{LSLG|vector}} using the Z, Y, X rotation order, then use the {{LSLG|llEuler2Rot}} function to get the '''rotation''' for use in combining rotations or applying the rotation to the object.

== Local vs Global (World) rotations ==

It is important to distinguish between the '''rotation''' relative to the world, and the '''rotation''' relative to the local object itself. In the editor, you can switch back and forth from one to the other. In a script, you must convert from one to the other to get the desired behavior.

'''Local''' rotations are ones done around the axes embedded in the object itself forward/back, left/right, up/down, irrespective of how the object is rotated in the world. '''Global''' rotations are ones done around the world axes, North/South, East/West, Higher/Lower. You can see the difference by rotating a prim, then edit it and change the axes settings between local and global, notice how the colored axes arrows change.

In LSL, the difference between doing a '''local''' or '''global''' rotation is the order the '''rotations''' are evaluated in the statement.

This does a '''local''' 30 degree rotation by putting the constant 30 degree '''rotation''' to the left of the object's starting '''rotation''' (myRot). It is like the first operation in the first example above, just twisting the dart 30 degrees around its own long axis.

<div id="box"><div style="padding: 0.5em">
{| cellpadding=0 cellspacing=0
|- valign="top"
| style="white-space: nowrap" |rotation localRot =
| style="white-space: nowrap" |rot30X * myRot;
||// do a local rotation by multiplying a constant rotation by a world rotation
|}
</div></div>

To do a '''global''' rotation, use the same '''rotation''' values, but in the opposite order. This is like the second operation in the second example, the dart rotating up and to the right around the world X axis. In this case, the existing rotation (myRot) is rotated 30 degrees around the global X axis.

<div id="box"><div style="padding: 0.5em">
{| cellpadding=0 cellspacing=0
|- valign="top"
| style="white-space: nowrap" |rotation globalRot
| style="white-space: nowrap" | = myRot * rot30X;
||// do a global rotation by multiplying a world rotation by a constant rotation
|}
</div></div>

== Another way to think about combining rotations ==

You may want to think about this '''local''' vs '''global''' difference by considering that '''rotations''' are done in evaluation order, that is left to right except for parenthesized expressions.

In the localRot case, what happened was that starting from <0, 0, 0>, the rot30X was done first, rotating the prim around the world X axis, but since when it's unrotated, the local and global axes are identical it has the effect of doing the rotation around the object's local X axis. Then the second '''rotation''' myRot was done which rotated the prim to its original rotation, but now with the additional X axis rotation baked in. What this looks like is that the prim rotated in place, around its own X axis, with the Y and Z rotations unchanged, a '''local''' rotation.

In the globalRot case, again starting from <0, 0, 0>, first the object is rotated to its original rotation (myRot), but now the object's axes and the world's axes are no longer aligned! So, the second '''rotation''' rot30x does exactly what it did in the local case, rotates the object 30 degrees around the world X axis, but the effect is to rotate the object through a cone around the world X axis since the object's X axis and the world's X axis aren't the same this time. What this looks like is that the prim pivoted 30 degrees around the world X axis, hence a '''global''' rotation.

'''Division''' of '''rotations''' has the effect of doing the rotation in the opposite direction, multiplying by a 330 degree '''rotation''' is the same as dividing by a 30 degree '''rotation'''.

==Using Rotations ==

You can access the individual components of a '''rotation''' '''R''' by '''R.x, R.y, R.z, & R.s''' ('''not''' R.w). The scalar part R.s is the cosine of half the angle of rotation. The vector part (R.x,R.y,R.z) is the product of the normalized axis of rotation and the sine of half the angle of rotation. You can generate an inverse '''rotation''' by negating the x,y,z members (or by making the s value negative). As an aside, you can also use a '''rotation''' just as a repository of [[float]] values, each '''rotation''' stores four of them and a [[list]] consisting of '''rotation''' is more efficient than a [[list]] consisting of [[float]]s, but there is overhead in unpacking them.

<div id="box"><div style="padding: 0.5em">
{| cellpadding=0 cellspacing=0
|- valign="top"
| style="white-space: nowrap" |rotation rot30X
| style="white-space: nowrap" |= [[llEuler2Rot]](<30, 0, 0> * [[#DEG_TO_RAD|DEG_TO_RAD]] );
||// Create a rotation constant
|- valign="top"
| style="white-space: nowrap" |rotation rotCopy
| style="white-space: nowrap" |= rot30X;
||// Just copy it into rotCopy, it copies all 4 float components
|- valign="top"
| style="white-space: nowrap" |float X
| style="white-space: nowrap" |= rotCopy.x;
||// Get out the individual components of the rotation
|- valign="top"
| style="white-space: nowrap" |float Y
| style="white-space: nowrap" |= rotCopy.y;
||
|- valign="top"
| style="white-space: nowrap" |float Z
| style="white-space: nowrap" |= rotCopy.z;
||
|- valign="top"
| style="white-space: nowrap" |float S
| style="white-space: nowrap" |= rotCopy.s;
||
|- valign="top"
| style="white-space: nowrap" |rotation anotherCopy
| style="white-space: nowrap" |= <X, Y, Z, S>;
||// Make another rotation out of the components
|}
</div></div>

There is a built in constant for a zero '''rotation''' [[#ZERO_ROTATION|ZERO_ROTATION]] which you can use directly or, if you need to invert a '''rotation R''', divide [[#ZERO_ROTATION|ZERO_ROTATION]] by '''R'''. As a reminder from above, this works by first rotating to the zero position, then because it is a divide, rotating in the opposite sense to the original '''rotation''', thereby doing the inverse rotation.
<div id="box"><div style="padding: 0.5em">
{| cellpadding=0 cellspacing=0
|- valign="top"
| style="white-space: nowrap" |rotation rot330X
| style="white-space: nowrap" |= <-rot30X.x, -rot30X.y, -rot30X.z, rot30X.s>;
||// invert a rotation - NOTE the s component isn't negated
|- valign="top"
| style="white-space: nowrap" |rotation another330X
| style="white-space: nowrap" |= [[#ZERO_ROTATION|ZERO_ROTATION]] / rot30X;
||// invert a rotation by division, same result as rot330X
|- valign="top"
| style="white-space: nowrap" |rotation yetanother330X
| style="white-space: nowrap" |= <rot30X.x, rot30X.y, rot30X.z, -rot30X.s>;
||// not literally the same but works the same.
|}
</div></div>

==Single or Root Prims vs Linked Prims vs Attachments ==

The reason for talking about single or linked prim rotations is that for things like doors on vehicles, the desired motion is to move the door relative to the vehicle, no matter what the rotation of the overall vehicle is. While possible to do this with global rotations, it would quickly grow tedious.
There are generally three coordinate systems a prim can be in: all alone, part of a {{LSLG|linkset}}, or part of an {{LSLG|attachment}}. When a prim is alone, i.e., not part of a {{LSLG|linkset}}, it acts like a root prim; when it is part of an {{LSLG|attachment}}, it acts differently and is a bit broken.

{{LSLRotGetSet}}

==Rotating Vectors ==

In LSL, rotating a [[vector]] is very useful if you want to move an object in an arc or circle when the center of rotation isn't the center of the object.

This sounds very complex, but there is much less here than meets the eye. Remember from the above discussion of rotating the [[#Combining Rotations|dart]], and replace the physical dart with a [[vector]] whose origin is the tail of the dart, and whose components in X, Y, and Z describe the position of the tip of the dart. Rotating the dart around its tail moves the tip of the dart through and arc whose center of rotation is the tail of the dart. In exactly the same way, rotating a [[vector]] which represents an offset from the center of a prim rotates the prim through the same arc. What this looks like is the object rotates around a position offset by the [[vector]] from the center of the prim.
=== Position of Object Rotated Around A Relative Point ===
<lsl>rotation vRotArc = llEuler2Rot( <30.0, 0.0, 0.0> * DEG_TO_RAD );
//-- creates a rotation constant, 30 degrees around the X axis

vector vPosOffset = <0.0, 1.0, 0.0>;
//-- creates an offset one meter in the positive Y direction

vector vPosRotOffset = vPosOffset * vRotArc;
//-- rotates the offset to get the motion caused by the rotation

vector vPosOffsetDiff = vPosOffset - vPosRotOffset;
//-- gets the local difference between the current offset and the rotated one

vector vPosRotDiff = vPosOffsetDiff * llGetRot();
//-- rotates the difference in the offsets to be relative to the global rotation.

vector vPosNew = llGetPos() + vPosRotDiff;
//-- finds the prims new position by adding the rotated offset difference

rotation vRotNew = vRotArc * llGetRot();
//-- finds rot to continue facing offset point</lsl>
:in application, the same action as:
<lsl>llSetPrimitiveParams( [PRIM_POSITION, llGetPos() + (vPosOffset - vPosOffset * vRotArc) * llGetRot(),
PRIM_ROTATION, vRotArc * llGetRot()] );</lsl>
* The above method results in the orbiting object always having the same side facing the center. An alternative that preserves the orbiters rotation is as follows
<lsl>llSetPrimitiveParams( [PRIM_POSITION, llGetPos() + (vPosOffset - vPosOffset * vRotArc) * llGetRot()];
vPosOffset = vPosOffset * vRotArc;</lsl>
'''Nota Bene:''' Doing this is a move, so don't forget about issues of moving a prim off world, below ground, more than 10 meters etc. Also to get a full orbit, you'll need to repeat the listed steps (in a [[timer]] perhaps).

=== Position of Relative Point Around Rotated Object ===
To get a point relative to the objects current facing (such as used in rezzors)
<lsl>vector vPosOffset = <0.0, 0.0, 1.0>;
//-- creates an offset one meter in the positive Z direction.

vector vPosRotOffset = vPosOffset * llGetRot();
//-- rotate the offset to be relative to objects rotation

vector vPosOffsetIsAt = llGetPos() + vPosRotOffset;
//-- get the region position of the rotated offset</lsl>
:in application, the same action as:
<lsl>llRezAtRoot( "Object", llGetPos() + vPosOffset * llGetRot(), ZERO_VECTOR, llGetRot(), 0 );</lsl>

==Useful Snippets==
<lsl>integer IsRotation(string s)
{
list split = llParseString2List(s, [" "], ["<", ">", ","]);
if(llGetListLength(split) != 9)//we must check the list length, or the next test won't work properly.
return 0;
return !((string)((rotation)s) == (string)((rotation)((string)llListInsertList(split, ["-"], 7))));
//it works by trying to flip the sign on the S element of the rotation,
//if it works or breaks the rotation then the values won't match.
//if the rotation was already broken then the sign flip will have no affect and the values will match
//we cast back to string so we can catch negative zero which allows for support of <0,0,0,0>
}//Strife Onizuka</lsl>

// Calculate a point at distance d in the direction the avatar id is facing
<lsl>vector point_in_front_of( key id, float d )
{
list pose = llGetObjectDetails( id, [ OBJECT_POS, OBJECT_ROT ] );
return ( llList2Vector( pose, 0 ) + < d, 0.0, 0.0 > * llList2Rot( pose, 1 ) );
}// Mephistopheles Thalheimer</lsl>

// Rez an object o at a distance d from the end of the z axis.
// The object is rezzed oriented to the rezzer

<lsl>rez_object_at_end( string o, float d )
{
vector s = llGetScale();

if( llGetInventoryType( o ) == INVENTORY_OBJECT )
{
llRezObject( o, llGetPos() + llRot2Up( llGetRot() ) * ( s.z / 2.0 + d ) , ZERO_VECTOR, llGetRot(), 0 );
}
}// Mephistopheles Thalheimer</lsl>

// Useful functions converted to LSL from [http://www.isner.com/tutorials/quatSpells/quaternion_spells_12.htm this page]:

// Scale a rotation:
<lsl>rotation ScaleQuat(rotation source, float ratio)
{
return llAxisAngle2Rot(llRot2Axis(source), ratio * llRot2Angle(source));
}</lsl>

// Constrain a rotation to a given plane, defined by its normal, this is very useful for vehicles that remain horizontal in turns:
<lsl>rotation ConstrainQuat2Plane(rotation source, vector normal)
{
return llAxisAngle2Rot(normal, <source.x, source.y, source.z> * normal * llRot2Angle(source));
} // Jesrad Seraph</lsl>

// Slerp (rotation combination) function from [[Slerp]]:
<lsl>rotation BlendQuats(rotation a, rotation b, float ratio)
{
return llAxisAngle2Rot(llRot2Axis(b /= a), ratio * llRot2Angle(b)) * a;
}</lsl>

== Constants ==
=== [[ZERO_ROTATION]] ===
ZERO_ROTATION = <0.0, 0.0, 0.0, 1.0>;<br/>
A rotation constant representing a Euler angle of <0.0, 0.0, 0.0>.

=== [[DEG_TO_RAD]] ===
DEG_TO_RAD = 0.01745329238f;<br/>
A float constant that when multiplied by an angle in degrees gives the angle in radians.

=== [[RAD_TO_DEG]] ===
RAD_TO_DEG = 57.29578f;<br/>
A float constant when multiplied by an angle in radians gives the angle in degrees.

[[Category:LSL_Types|Rotation]][[Category:LSL_Math]][[Category:LSL_Math/3D]][[Category:LSL Rotation]]

Simple Encryption

2009-08-16T21:32:16Z

Vernes Veranes: Encryptor code has string hex AND function hex, this does not work. adjusted.

{{LSL Header}}
Here's a function to pass a secret message from one object to another. Using XOR, this is perhaps the weakest form of encryption. I have taken steps to make it harder to break using random nonce values with the password. If someone is able to decrypt one message, it will be easy for them to decrypt any other message. I've also added version support so that you can upgrade the script later and still have compatibility with older scripts using the same protocol.

== Encryptor ==

<lsl>string ProtocolSignature = "ENC"; // your own signature
float ProtocolVersion = 0.3; // can range from 0.0 to 255.255
string Password = "P@ssw0rd"; // change this to your own password
integer communicationsChannel = PUBLIC_CHANNEL;
string Header;
string strHex = "0123456789ABCDEF";

string hex(integer value)
{
integer digit = value & 0xF;
string text = llGetSubString(strHex, digit, digit);
value = (value >> 4) & 0xfffFFFF;
integer odd = TRUE;
while(value)
{
digit = value & 0xF;
text = llGetSubString(strHex, digit, digit) + text;
odd = !odd;
value = value >> 4;
}
if(odd)
text = "0" + text;
return text;
}
string encrypt(string password, string message)
{
// get a random value
integer nonce = (integer)llFrand(0x7FFFFFFF);

// generate digest and prepend it to message
message = llMD5String(message, nonce) + message;

// generate one time pad
string oneTimePad = llMD5String(password, nonce);

// append pad until length matches or exceeds message
integer count = (llStringLength(message) - 1) / 32;
if(count)
do
oneTimePad += llMD5String(oneTimePad, nonce);
while(--count);

// return the header, nonce and encrypted message
return Header + llGetSubString("00000000" + hex(nonce), -8, -1) + llXorBase64StringsCorrect(llStringToBase64(message), llStringToBase64(oneTimePad));
}
init()
{
//build the header, it never changes.
list versions = llParseString2List((string)ProtocolVersion, ["."], []);
string minor = llList2String(versions, 1);
integer p = 0;
while(llGetSubString(minor, --p, p) == "0");
Header = ProtocolSignature + hex(llList2Integer(versions, 0)) + hex((integer)llGetSubString(minor, 0xFF000000, p));
}

default
{
state_entry()
{
init();
llSay(communicationsChannel, encrypt(Password, "Hello, Avatar!"));
llSay(communicationsChannel, encrypt(Password, "This is a very long text that I hope to be able to create a long one time pad to decrypt for it."));
}

touch_start(integer total_number)
{
llSay(communicationsChannel, encrypt(Password, "Touched."));
}
}</lsl>

== Decryptor ==
<lsl>
string ProtocolSignature = "ENC"; // your own signature
float ProtocolVersion = 0.3; // can range from 0.0 to 255.255
string Password = "P@ssw0rd"; // change this to your own password
integer communicationsChannel = PUBLIC_CHANNEL;
integer Debug = TRUE; // Set this to false for production
integer listener;

init()
{
if(listener != 0)
{
llListenRemove(listener);
listener = 0;
}
listener = llListen(communicationsChannel, "", NULL_KEY, "");
}
string error(string message)
{
if(Debug) llSay(DEBUG_CHANNEL, message);
return "";
}
string decrypt(string password, string message)
{
integer signatureLength = llStringLength(ProtocolSignature);
integer headerLength = signatureLength + 12; // version = 4, nonce = 8

// verify length of encrypted message
if(llStringLength(message) < signatureLength + 44) // digest = 32 (base64 = 44) + at least one character
return error("Too small for secret message.");

// look for protocol signature in message header
if(llSubStringIndex(message, ProtocolSignature) != 0)
return error("Unknown protocol.");

// Parse version information from header
integer index = signatureLength; // determine where to start parsing
string major = "0x" + llGetSubString(message, index, ++index);
string minor = "0x" + llGetSubString(message, ++index, ++index);
float version = (float)((string)((integer)major) + "." + (string)((integer)minor));

// verify version is supported
if(version != ProtocolVersion)
return error("Unknown version.");

// parse nonce from header
integer nonce = (integer)("0x" + llGetSubString(message, ++index, index + 7));

// remove header from message
message = llGetSubString(message, headerLength, -1);

// create one time pad from password and nonce
string oneTimePad = llMD5String(password, nonce);
// append pad until length matches or exceeds message
while(llStringLength(oneTimePad) < (llStringLength(message) / 2 * 3))
oneTimePad += llMD5String(oneTimePad, nonce);

// decrypt message
oneTimePad = llStringToBase64(oneTimePad);
message = llXorBase64StringsCorrect(message, oneTimePad);

// decode message
message = llBase64ToString(message);

// get digest
string digest = llGetSubString(message, 0, 31);

// remove digest from message
message = llGetSubString(message, 32, -1);

// verify digest is valid
if(llMD5String(message, nonce) != digest)
return error("Message digest was not valid.");

// return decrypted message
return message;
}
default
{
state_entry()
{
init();
}
on_rez(integer start_param)
{
init();
}
listen(integer channel, string name, key id, string message)
{
string message = decrypt(Password, message);
if(message != "")
llSay(0, message);
}
}
</lsl>

Note: The [[Hex]] and [[Efficient Hex]] examples were used to create the hex method.

{{LSLC|Examples|Simple Encryption}}
[[Category: LSL Encryption]]

User:Vernes Veranes

2008-12-23T14:44:57Z

Vernes Veranes: Thanks Zai

User talk:Vernes Veranes

2008-12-23T14:39:25Z

Vernes Veranes:

== Borders ==
Heyas =)<br>
It's not up to date, but I read on your profile page, that you asked where the borders of your table would be. Answer is: You didn't set any. In order to tell the table to set borders, you'd need to add a <font color="black">border="1"</font> to the initial syntax of the table. Have a look [http://www.mediawiki.org/wiki/Help:Tables#border.3D.221.22 at the related mediawiki help page] for further info =)<br>
A neat and fast work-around for simple tables is, to use [[Template:Prettytable]]. Just start your table with
<nowiki>{|style={{Prettytable}}</nowiki>
It would look like
{|style={{Prettytable}}
!heading 1
!heading 2
|-
|value 1
|value 2
|}
Greetz, [[Image:Zai_signature.png|45px]] '''[[User:Zai Lynch|Lynch]]''' <sup><small>([[User talk:Zai Lynch|talk]]|[[Special:Contributions/Zai Lynch|contribs]])</small></sup> 12:41, 23 December 2008 (UTC)
: Thanks a bunch --[[User:Vernes Veranes|Vernes]] 14:39, 23 December 2008 (UTC)

Talk:LlMD5String

2008-12-23T08:53:26Z

Vernes Veranes: Thanks!

== Catagory LSL String ? ==

How do we get this function in catagory String, and catagory Encryption?
I keep bumping into the fact I can't find it under String --[[User:Vernes Veranes|Vernes]] 20:47, 22 December 2008 (UTC)
:Fixed =)
:Categories can be defining the cat1 ... catN variables as the name of the category (without the LSL prefix). Have a look at [https://wiki.secondlife.com/w/index.php?title=LlMD5String&diff=183053&oldid=95091 the edit here].
:Can also read [[Template:LSL Function/docs]] for further info.
:Greetz, [[Image:Zai_signature.png|45px]] '''[[User:Zai Lynch|Lynch]]''' <sup><small>([[User talk:Zai Lynch|talk]]|[[Special:Contributions/Zai Lynch|contribs]])</small></sup> 21:08, 22 December 2008 (UTC)
::Great explaination! Thanks! --[[User:Vernes Veranes|Vernes]] 08:53, 23 December 2008 (UTC)

Talk:LlMD5String

2008-12-22T20:47:54Z

Vernes Veranes: Catagory LSL String ?

Category talk:LSL XML-RPC

2008-12-22T15:18:21Z

Vernes Veranes: comment added about php code

This page does not wrap due to ridiculously long line at top of php script. Can line breaks be added without breaking this script? [[User:Scalar Tardis|Scalar Tardis]] 20:21, 28 May 2008 (PDT)
: ''Strife Onizuka said: (→php: I've tried my best to make it readable and valid though I can't be sure of the later.)''
: It is still valid php. Excuses for the messy php code and for the late reply. --[[User:Vernes Veranes|Vernes]] 15:18, 22 December 2008 (UTC)

Talk:LSL Portal Translation Project

2008-12-19T13:55:23Z

Vernes Veranes: /* Rouge Translations */

== Chinese Language Variant Names ==
Aren't usual codes for Chinese zh-CN (traditional) and zh-TW (simplified)? -- Catherine Pfeffer
*Wikipedia has moved to using zh-hans and zh-hant. I don't know why but I think it may has something to do with zh-sg (which uses simplified) and zh-hk (traditional) isn't really needed as seperate variants most of the time. --[[User:Geneko Nemeth|Geneko Nemeth]] 20:35, 16 December 2007 (PST)

== Templates ==

Many of the LSL templates and subtemplates should be translated. The function template will require some finesse. If there are any questions about the templates just leave a message on my userpage. The javascript used to change the article name case can't be used to strip the language code fyi. -- [[User:Strife Onizuka|Strife Onizuka]] 12:02, 11 December 2007 (PST)

== Highly Specific Language ==

One problem we have to try and avoid is the loss of specific language when translating the articles. Some of the language used to describe how things work has been chosen for very specific reasons. They have very tight and specific means and implications. I'm worried that in the process of translation some of this will be lost.

It would be beneficial if the translators could validate against SL what they are translating. It would ensure the translation is accurate and that the English documentation is accurate too.

In essence I'm worried that the translators won't have enough understanding of the content to ensure the correct nuances are kept. Considering the edits that take place on articles this fear is well founded. <br/> --[[User:Strife Onizuka|Strife Onizuka]] 09:41, 15 December 2007 (PST)

== Common Proper Terms in Translation ==
Hey, I think it would be nice if there's a fixed translation for proper terms in Second Life like "Avatar" or "Parcel". --[[User:Geneko Nemeth|Geneko Nemeth]] 20:35, 16 December 2007 (PST)
:It's not helping that the translation in the official viewer is... well, it makes the translation of Zero Wing look good by comparison. --[[User:Geneko Nemeth|Geneko Nemeth]] 21:05, 16 December 2007 (PST)

== Example localization ==

does anyone have suggestions for localizing examples when the writer (like me) only has fluency in one of the languages a page is available in? I notice many of the /ja page examples are in english, which seems kind of silly, although I'm not sure if it's any better to only have an example in one language, but not another. My personal temptation is to example the known page, and leave a discussion note that the other pages need to be updated with localized versions.... or should I just copy the untranslated version across the available language pages as seems to have been done with many of the japanese examples?
-- [[User:Void Singer|Void Singer]] 13:44, 19 February 2008 (PST)

If you talking about only comments in scripts, it could be better translate. (But if so, You can't just copy & paste it to LSL editor. because the editor built in some client version can't handle UTF-8 correctly.) And if you want to localize these scripts in such as messaging part level, I think it's not a good idea to do. To do it, we need to re-check them all again and could be en-bugging in the process of localization. -- [[User:Nock Forager|Nock Forager]] 02:21, 20 February 2008 (PST)

:mostly concerned with updates where the user (me in this case) isn't fluent in other languages the page is available in, examples are one case, but also did some rework/input to the rotation page, that is also available in french and japanese. in the case of examples being added what does everyone think? should we propogate the addition accross all pages, and let those familiar with the language translate it, or do something similar with translation software? should we only add to the language we're fluent in? I honestly don't know, but I'm gunshy about using translation software as it may add more confusion than help. I'm personally leaning towards propogating the addition without translation, but was hoping for others thoughts. in the case of reworking sections I'm leaning towards only adding it to the page I'm fluent in, but then how do I let someone fluent in other languages know there's a change/correction that should be translated? should we just leave a note on the discussion page for the non-fluent languages? very confusing to me -- [[User:Void Singer|Void Singer]] 16:39, 7 March 2008 (PST)

== Re: Do not translate... ==

The page starts with
Do NOT translate this page. This would result in out-of-sync versions of the master list
This is not neccessarily the case. I would suggest to translate all the introductional part ('''not''' the list of course) and mark it with <nowiki><noinclude>...</noinclude></nowiki>. Then you could include the list in the translations (like it is done at [[SL Volunteer Linguist Center/German]] and [[SL Volunteer Linguist Center/German/de]] with the contributions). Or exclude the list at all like it is done in the translations of the [[Mentor Linguist Scribe Translation Project]].<br>
--[[User:Zai_Lynch|Zai Lynch]]<sup>([[User_talk:Zai_Lynch|talk]]|[[Special:Contributions/Zai_Lynch|contribs]])</sup> 07:53, 3 June 2008 (PDT)

== Rouge Translations ==

After I spend some time translating the LSL Portal Guideline page to dutch I realized there might have been some procedures I completely ignored. So here's my apology beforehand and also a request to fellow dutchmen to go over my dutch interpretation of the english version.
Trying to find my translation, I realize there are some Templates that need adjusting to make available my translation at [[https://wiki.secondlife.com/wiki/LSL_Portal_Guidelines/nl]], this is something I cannot do. --[[User:Vernes Veranes|Vernes]] 13:55, 19 December 2008 (UTC)

Talk:LSL Portal Translation Project

2008-12-19T13:50:25Z

Vernes Veranes: /* Rouge Translations */ new section

LSL Portal Translation Project

2008-12-19T13:45:14Z

Vernes Veranes:

{{LSL Header}}
__NOTOC__
Do NOT translate this page. This would result in out-of-sync versions of the master list
== Welcome to the LSL Portal Translation Project! ==
This is a community effort to provide a multi-lingual translation of the LSL Portal. Please feel free to edit and add languages to the set. Only reasonably static pages have been selected for translation. News, bugs and patches, automatically generated pages have been set aside. This way, we intend to keep the original pages and their translations as much similar as possible.

LSL Scripters can participate in this project by choosing a wiki page from the list below and translating it into the language(s) they speak fluently. This suggestion list will be updated periodically with new pages. Contributors are welcomed to list themselves and discuss language-specific topics on the proper subpage of the [[LSL_Portal_Translation_Team]] page.

== <span style="color:red;">Please notice</span> ==

To make coordination easier, I have created an inworld group named '''"LSL portal translation"'''. Please subscribe to it ('Open Enrollment' is disabled, ask group owner to join).

Subjects of discussion might be :
- transition to new language codes
- is the structure of this coordination page adequate ?
- links look ugly in the localized categories
- how to attract more contributors
- etc.

This group will also provide mutual help, for example with templates localization.

== Procedure to Create a Translation Page ==

* Choose a page from the Suggested Pages to Translate. If the page is followed by the languages list, it is ready for translation.

* If the page is not ready for translation the <nowiki>{{Multi-lang}}</nowiki> tag should be included in the main page. If you are not are not familiar with this wiki, feel free to ask for assistance.

* Click the link of the page you have chosen to translate. In the URL bar of your navigator, add a /xx language code. This is how you create the language subpage. Example: LSL_Tutorial/fr to create a french translation of LSL_Tutorial.

====Language Codes====
{| border="1" cellspacing="0"
!Code!!Language
|-
|de||German
|-
|en||English
|-
|es||Spanish
|-
|fr||French
|-
|it||Italian
|-
|ko||Korean
|-
|ja||Japanese
|-
|nl||Dutch
|-
|pl||Polish
|-
|pt||Portuguese
|-
|zh-Hans||Chinese (Simplified) 
|-
|zh-Hant||Chinese (Traditional) 
|}

* It is advised to start from a copy of the main page source and insert your translation in place of the original content to achieve the same page layout.

* Once your translation is finished, add "Done", the date, and your name to the Suggested Pages to Translate. For the date, use the international ISO format YYYY-MM-DD.

==Suggested Pages to Translate==

=== LSL Portal ===

====[[:LSL_Portal]]====
*Chinese - Done
*Dutch - Done 2008-04-14 Aidamina Hunt
*French - Done 2007-12-02 Catherine Pfeffer
*German - Started 2008-04-10 Shyan Graves
*Italian - Done 2007-12-28 NickTheDeveloper Masatada
*Japanese - Started 2007-12-05 Coffee Mills
*Korean - Started 2008-09-04 JParker Devin
*Polish - Started 2008-02-23 Sebast Forwzy
*Portuguese - Started 2008-01-28 Rui Clary
*Spanish - Done 2008-03-05 SharpEdge Aeon
----

====[[:LSL_Editing_Primer]]====
* Chinese - Started 2007-12-30 Fuser Aeon
* Dutch -
* French -
* German -
* Italian - Done 2007-12-28 NickTheDeveloper Masatada
* Japanese - Done 2007-12-30 Asuka Neely
* Korean - Started 2008-09-04 JParker Devin
* Polish -
* Portuguese - Done 2008-08-30 [[User:Agathos Frascati|Agathos Frascati]]
* Spanish - Done 2008-03-05 SharpEdge Aeon
----

====[[:LSL_Portal_Guidelines]]====
* Chinese -
* Dutch - Done 2008-12-19 Vernes Veranes
* French -
* German -
* Italian - Done 2008-01-03 NickTheDeveloper Masatada
* Japanese - Done 2007-12-30 Asuka Neely
* Korean -
* Polish -
* Portuguese - Done 2008-09-07 [[User:Agathos Frascati|Agathos Frascati]]
* Spanish - Done 2007-01-02 Ashty Kuhn
----

====[[:LSL_Portal_To-do]]====
* Chinese -
* Dutch -
* French -
* German -
* Italian -
* Japanese - Done 2007-12-30 Asuka Neely
* Korean -
* Polish -
* Portuguese -
* Spanish - Done 2008-03-05 SharpEdge Aeon

=== Developer Resources ===

====[[:LSL_Tutorial]]====
* Chinese -
* Dutch -
* French -
* German -
* Italian - Done 2007-12-29 NickTheDeveloper Masatada
* Japanese - Done 2007-12-27 Asuka Neely
* Korean -
* Polish -
* Portuguese -
* Spanish - Done 2008-01-02 Ashty Kuhn
----

====[[:Category:LSL_Teachers]]====
This is a :Category; page and doesn't need translation
----
====[[:Category:LSL_Mentors]]====
This is a :Category; page and doesn't need translation
----
====[[:Category:LSL_Examples]]====
This is a :Category; page and doesn't need translation
----
====[[:Category:LSL_Library]]====
This is a :Category; page and doesn't need translation
----
====[[:LSL_Protocol]]====
* Chinese -
* Dutch -
* French - Done 2008-03-28 Max Gabreski
* German -
* Italian - Done 2007-12-29 NickTheDeveloper Masatada
* Japanese - Done 2007-12-27 Asuka Neely
* Korean -
* Polish -
* Portuguese -
* Spanish - Done 2008-03-06 SharpEdge Aeon
----

====[[:LSL_Useful_Function_WishList]]====
* Chinese -
* Dutch -
* French -
* German -
* Italian - Done 2007-12-29 NickTheDeveloper Masatada
* Japanese - Done 2007-12-28 Asuka Neely
* Korean -
* Polish -
* Portuguese -
* Spanish - Done 2008-03-06 SharpEdge Aeon
----

====[[:LSL_Style_Guide]]====
*Chinese - Done 2007-12-29 Fuser Aeon
*Dutch -
*French - Done 2007-12-02 Jeff Kelley
*German -
*Italian -
*Japanese - Done 2007-12-25 Asuka Neely
*Korean -
*Polish -
*Portuguese -
*Spanish - Done 2008-03-06 SharpEdge Aeon
----

====[[:LSL_Script_Efficiency]]====
*Chinese - Done 2007-12-22 Fuser Aeon
*Dutch -
*French - Done 2007-12-04 Jeff Kelley
*German - Started 2008-11-23 Karsten Runningbear
*Italian - Done 2008-01-03 NickTheDeveloper Masatada
*Japanese - Done 2007-12-25 Asuka Neely
*Korean -
*Polish -
*Portuguese -
*Spanish - Done 2008-03-06 SharpEdge Aeon
----

====[[:LSL_Script_Memory]]====
*Chinese -
*Dutch -
*French - Done 2007-12-02 Jeff Kelley
*German -
*Italian -
*Japanese - Done 2007-12-26 Asuka Neely
*Korean -
*Polish -
*Portuguese -
*Spanish - Done 2008-03-06 SharpEdge Aeon
----

====[[:LSL_Write_Once_Debug_Everywhere]]====
*Chinese -
*Dutch -
*French - Done 2007-12-02 Jeff Kelley
*German -
*Italian -
*Japanese - Done 2007-12-26 Asuka Neely
*Korean -
*Polish -
*Portuguese -
*Spanish - Done 2008-03-12 SharpEdge Aeon
----

====[[:LSL_Alternate_Editors]]====
*Chinese -
*Dutch -
*French -
*German -
*Italian -
*Japanese - Done 2007-12-27 Asuka Neely
*Korean -
*Polish -
*Portuguese -
*Spanish - Started 2008-03-12 SharpEdge Aeon
-----

====[[:LSL_Test_Harness]]====
* Chinese -
* Dutch -
* French -
* German -
* Italian -
* Japanese - Done 2007-12-28 Asuka Neely
* Korean -
* Polish -
* Portuguese -
* Spanish -
----

====[[:LSL_Benchmarking_Scripts]]====
* Chinese -
* Dutch -
* French -
* German -
* Italian -
* Japanese - Done 2007-12-28 Asuka Neely
* Korean -
* Polish -
* Portuguese -
* Spanish -

=== LSL Language Reference ===
----
====[[:Category:LSL_Constants]]====
* Chinese -
* Dutch -
* French - Done 2007-12-30 Catherine Pfeffer
* German -
* Italian -
* Japanese - Done 2007-12-30 Asuka Neely
* Korean -
* Polish -
* Portuguese -
* Spanish -
----

====[[DEG_TO_RAD]]====
* Chinese -
* Dutch -
* French - Done 2007-12-30 Catherine Pfeffer
* German -
* Italian -
* Japanese -
* Korean -
* Polish -
* Portuguese -
* Spanish -
----

====[[NULL_KEY]]====
* Chinese -
* Dutch -
* French - Done 2007-12-30 Catherine Pfeffer
* German -
* Italian -
* Japanese -
* Korean -
* Polish -
* Portuguese -
* Spanish -
----

====[[RAD_TO_DEG]]====
* Chinese -
* Dutch -
* French - Done 2007-12-30 Catherine Pfeffer
* German -
* Italian -
* Japanese -
* Korean -
* Polish -
* Portuguese -
* Spanish -
----

====[[ZERO_ROTATION]]====
* Chinese -
* Dutch -
* French - Done 2007-12-30 Catherine Pfeffer
* German -
* Italian -
* Japanese -
* Korean -
* Polish -
* Portuguese -
* Spanish -
----

====[[ZERO_VECTOR]]====
* Chinese -
* Dutch -
* French - Done 2007-12-30 Catherine Pfeffer
* German -
* Italian -
* Japanese -
* Korean -
* Polish -
* Portuguese -
* Spanish -
----

====[[:Category:LSL_Events]]====
* Chinese -
* Dutch -
* French - Done 2008-01-10 Catherine Pfeffer
* German -
* Italian -
* Japanese -
* Korean -
* Polish -
* Portuguese -
* Spanish -
----

====[[state_entry]]====
* Chinese -
* Dutch -
* French - Done 2008-01-10 Alsau Spinotti
* German -
* Italian -
* Japanese -
* Korean -
* Polish -
* Portuguese -
* Spanish -
----

====[[:Category:LSL_Functions]]====
* Chinese -
* Dutch -
* French - Done 2007-12-30 Catherine Pfeffer
* German -
* Italian -
* Japanese -
* Korean -
* Polish -
* Portuguese -
* Spanish -
----

====[[llGetAnimation]]====
* Chinese -
* Dutch - Started 2008-05-22 Aidamina Hunt
* French - Done 2007-12-30 Phli Foxchase
* German -
* Italian -
* Japanese -
* Korean -
* Polish -
* Portuguese -
* Spanish -
----

====[[llGetAnimationList]]====
* Chinese -
* Dutch -
* French - Done 2008-01-09 Gally Young
* German -
* Italian -
* Japanese -
* Korean -
* Polish -
* Portuguese -
* Spanish -
----

====[[:Category:LSL_Flow_Control]]====
* Chinese -
* Dutch -
* French - Done 2007-12-30 Catherine Pfeffer
* German -
* Italian -
* Japanese - Done 2007-12-05 Coffee Mills
* Korean -
* Polish -
* Portuguese -
* Spanish -
----

====[[For]]====
*Chinese -
*Dutch -
*French - Done 2007-12-03 Olivier hildyard
*German -
*Italian -
*Japanese - Done 2007-12-05 Coffee Mills
*Korean -
*Polish -
*Portuguese -
*Spanish -
----
====[[If]]====
*Chinese -
*Dutch -
*French - Done 2008-01-08 Catherine Pfeffer
*German -
*Italian -
*Japanese - Done 2007-01-01 Asuka Neely
*Korean -
*Polish -
*Portuguese -
*Spanish -
----

====[[While]]====
*Chinese -
*Dutch -
*French - Done 2007-12-03 Forest Klaar
*German -
*Italian -
*Japanese - Done 2007-12-13 Coffee Mills
*Korean -
*Polish -
*Portuguese -
*Spanish -
----

====[[Do-while]]====
*Chinese -
*Dutch -
*French - Done 2007-12-05 Samia Bechir
*German -
*Italian -
*Japanese - Done 2007-1-1 Asuka Neely
*Korean -
*Polish -
*Portuguese -
*Spanish -
----

====[[Jump]]====
*Chinese -
*Dutch -
*French - Done 2008-01-09 Samia Bechir
*German -
*Italian -
*Japanese - Done 2007-1-1 Asuka Neely
*Korean -
*Polish -
*Portuguese -
*Spanish -
----

====[[Return]]====
*Chinese -
*Dutch -
*French - Done 2008-01-09 Samia Bechir
*German -
*Italian -
*Japanese - Done 2007-1-1 Asuka Neely
*Korean -
*Polish -
*Portuguese -
*Spanish -
----

====[[State]]====
*Chinese -
*Dutch -
*French - Done 2007-12-30 Samia Bechir
*German -
*Italian -
*Japanese - Done 2007-1-1 Asuka Neely
*Korean -
*Polish -
*Portuguese -
*Spanish -
----

====[[LSL_Operators]]====
This article is currently incomplete
*Chinese -
*Dutch -
*French -
*German -
*Italian -
*Japanese -
*Korean -
*Polish -
*Portuguese -
*Spanish -
----
====[[:Category:LSL_Types]]====
*Chinese -
*Dutch -
*French - Done 2007-12-03 Catherine Pfeffer
*German -
*Italian -
*Japanese -
*Korean -
*Polish -
*Portuguese -
*Spanish -
----
====[[Integer]]====
*Chinese -
*Dutch -
*French - Done 2007-12-02 Samia Bechir
*German -
*Italian -
*Japanese - Done 2007-12-04 Coffee Mills
*Korean -
*Polish -
*Portuguese -
*Spanish -
----
====[[Float]]====
*Chinese -
*Dutch -
*French - Done 2007-12-02 Audrey Bisani
*German -
*Italian -
*Japanese - Done 2007-12-04 Coffee Mills
*Korean -
*Polish -
*Portuguese -
*Spanish -
----
====[[String]]====
*Chinese -
*Dutch -
*French - Done 2007-12-02 Samia Bechir
*German -
*Italian -
*Japanese - Done 2008-01-02 Asuka Neely
*Korean -
*Polish -
*Portuguese -
*Spanish -
----

====[[Key]]====
*Chinese -
*Dutch -
*French - Done 2007-12-02 Catherine Pfeffer
*German -
*Italian -
*Japanese - Done 2007-12-05 Coffee Mills
*Korean -
*Polish -
*Portuguese -
*Spanish -
----
====[[List]]====
*Chinese -
*Dutch -
*French - Done 2007-12-03 Catherine Pfeffer
*German -
*Italian -
*Japanese - Done 2008-01-02 Asuka Neely
*Korean -
*Polish -
*Portuguese -
*Spanish -
----

====[[Vector]]====
*Chinese -
*Dutch -
*French - Done 2007-12-03 Ol Obscure
*German -
*Italian -
*Japanese - Done 2007-12-05 Coffee Mills
*Korean -
*Polish -
*Portuguese -
*Spanish -
----
====[[Rotation]]====
*Chinese -
*Dutch -
*French - Done 2007-12-03 Samia Bechir
*German -
*Italian -
*Japanese - Done 2008-01-08 Asuka Neely
*Korean -
*Polish -
*Portuguese -
*Spanish -
----

====[[Quaternion]]====
*Chinese -
*Dutch -
*French - Done 2007-12-03 Catherine Pfeffer
*German -
*Italian -
*Japanese -
*Korean -
*Polish -
*Portuguese -
*Spanish -
----

====[[LSL_Variables]]====
*Chinese -
*Dutch -
*French - Done 2007-12-11 Samia Bechir
*German -
*Italian -
*Japanese - Done 2007-12-05 Coffee Mills
*Korean -
*Polish -
*Portuguese -
*Spanish -
----

====[[LSL_Errors]]====
*Chinese -
*Dutch -
*French - Done 2007-12-11 Samia Bechir
*German -
*Italian -
*Japanese - Done 2007-12-05 March Korda
*Korean -
*Polish -
*Portuguese -
*Spanish -
----

===Templates===

====[[Template:LSL_Constants_Conditional]]====
*Chinese -
*Dutch -
*French - Done 2007-12-04 Catherine Pfeffer
*German -
*Italian -
*Japanese -
*Korean -
*Polish -
*Portuguese -
*Spanish -
----
====[[Template:LSL_Conditional]]====
*Chinese -
*Dutch -
*French - Done 2007-12-04 Catherine Pfeffer
*German -
*Italian -
*Japanese -
*Korean -
*Polish -
*Portuguese -
*Spanish -
----
====[[Template:LSL Event]]====
*Chinese -
*Dutch -
*French - Done 2008-01-10 Catherine Pfeffer
*German -
*Italian -
*Japanese -
*Korean -
*Polish -
*Portuguese -
*Spanish -
----
====[[Template:LSL Function]]====
*Chinese -
*Dutch - Started 2008-05-22 Aidamina Hunt
*French - Done 2007-12-30 Catherine Pfeffer
*German -
*Italian -
*Japanese -
*Korean -
*Polish -
*Portuguese -
*Spanish -
----

====[[Template:LSL_Generic]]====
*Chinese -
*Dutch -
*French - Done 2008-01-09 Catherine Pfeffer
*German -
*Italian -
*Japanese -
*Korean -
*Polish -
*Portuguese -
*Spanish -
----
====[[Template:LSLRotGetSet]]====
*Chinese -
*Dutch -
*French - Done 2007-12-05 Catherine Pfeffer
*German -
*Italian -
*Japanese -
*Korean -
*Polish -
*Portuguese -
*Spanish -
----
[[Category:Localization]]

LSL Portal Guidelines/nl

2008-12-19T13:42:32Z

Vernes Veranes: New page: {{LSL Header|ml=*}} {{RightToc}} Deze pagina is ter definitie en beschrijving van specifieke Richtlijnen omtrent het uitbreiden en aanpassen van de LSL Wiki Portal. == Over De LSL Portal...

{{LSL Header|ml=*}}
{{RightToc}}

Deze pagina is ter definitie en beschrijving van specifieke Richtlijnen omtrent het uitbreiden en aanpassen van de LSL Wiki Portal.

== Over De LSL Portal ==
<h4>Missie</h4>
:"Om accurate documentatie aan te bieden over de scripttaal van Second Life: LSL"{{Footnote|Afgeleid van de open zinnen van de [[LSL Portal]].|Afgeleid van de open zinnen van de LSL Portal.|handle=1}}

<h4>Doel</h4>
:"Om documentatie aan te bieden om scripters van alle niveaus van vaardigheden te helpen."{{Footnote|handle=1}}

== Wegwijzer ==

* [[LSL Editing Primer]] - Informatie over templates en syntax.

== Stijl ==

# [[LSL Category Style]] - Wordt gebruikt voor het categoriseren van LSL functie groepen en andere indexen.
# [[LSL Function Style]] - Wordt gebruikt voor volledige specificaties van alle LSL functies.
# [[LSL Topic Style]] - Wordt gebruikt voor onderwerpen van interesse, gerelateerd aan het gebruik van LSL (XML-RPC, quaternions, enz).
# [[LSL Constants Style]] - Wordt gebruikt voor het documenteren van constanten.

== Richtlijnen ==

* Pagina's die specifiek voor het runnen van de LSL portal of voor de categorie pagina's gebruikt worden moeten 'LSL ' als prefix hebben.
* Alle overige bestaande pagina's ter documentatie van LSL die de LSL prefix gebruiken moeten verplaatst worden uit de LSL prefix tenzij een andere regeling is afgesproken.
* Vragen dienen gesteld te worden op de talk/discussion pagina en dienen gesigneerd te worden (gebruik <code><nowiki>-- ~~~~</nowiki></code> om je commentaar te signeren).
* Voordat je een feature suggestie plaatst op de wiki, controleer eerst of deze niet al staat op [https://jira.secondlife.com/ Jira].
* Wanneer men een script plaatst en dit betreft een volledige script, dan dient deze zonder problemen te compileren tenzij dit anders vermeld is. Code segmenten dienen probleemloos te compileren wanneer deze correct is geïnstalleerd in een script (geen interne errors in de code segmenten).
* Scripts die geplaatst worden dienen een consistente stijl aan te houden; consistent spatie gebruik is hierbij belangrijk.
* Moderne webbrowsers zijn uitgevoerd met spellingscontrole-functionaliteit of kunnen hiervoor aangepast worden. Alle content dient gecontroleerd te worden op spellingfouten voordat deze geplaatst wordt.

== Footnotes ==
{{Footnotes}}

Talk:LSL Event ID

2008-12-17T22:33:03Z

Vernes Veranes: A list of actual ID's?

== A list of actual ID's? ==

I seem to have overlooked Event_ID 26, but there is no way to find it just by ID. A list would be nice. --[[User:Vernes Veranes|Vernes]] 22:33, 17 December 2008 (UTC)

Category talk:LSL Events

2008-12-17T22:03:45Z

Vernes Veranes: /* State_entry */ new section

Why all events have a code ender? should be starting with both brackets.

Not this... event(integer);

Should be this... event(integer){ }

But I am unable to correct this format in the wiki, what's the deal? -Vincent Nacon

:Sorry thats my fault, I've been meaning to fix it, it's a bug in the template. I just kept forgetting. [[User:Strife Onizuka|Strife Onizuka]]
:Fixed, the variable for that part of the title was getting double defined; the latter overwriting the former. [[User:Strife Onizuka|Strife Onizuka]] 18:17, 6 April 2007 (PDT)

== Attach under S letter ==

The [[Attach]] event is listed under '''S''' letter. I have no idea about how to fix it. Can someone fix that? (and explain here how it was done)
--[[User:CrazyTB Oh|CrazyTB Oh]] 11:37, 21 August 2007 (PDT)

:I fixed it. What I do is delete the part that says this is part of the "LSL_EVENTS" category and then put it back. That usually fixes it, and when it doesn't then I just mess around with the page and it eventually gets fixed... [[User:Xaviar Czervik|Xaviar Czervik]] 15:43, 17 September 2007 (PDT)

== Script Ban Zones ==
I have spend many hours on trying to figure out how events are handled in script ban zones. I have some text to describe it. But I am not sure where to put it, so for a start I put it here, someone might then help me put the logical place (which I have not yet figured out).

All the usual events are happening in script-banned zones, only the script does not react to them, but keep them in the event queue for later execution. This might potentially cause problems with the 64 length of the queue, though I have not tried this out.

Notice, even listen events are stored. Also notice, pending listen events are removed when moving to a new region, but not other events I have tried.

The big surprise is that scripts can be made to execute in a script ban zone - pending events to a script in an attachment are all executed when the attachment is detached. By attaching and detaching an attachment, one can therefore execute code in a no script zone, even listen events. However, this will most often not be very useful.

I have verified that, change, rezzing, attachment, touch are all registered and stored in the event queue for later execution. I have not investigated the behavior of other events in depth.

Finally, there are some restrictions regarding repetition of events I have not fully explored. For instance, it seems that only one touch event is queued even if one touches an attachment multiple times.

2008 jan 17 -[[User:Boreal Latte|Boreal Latte]]

== State_entry ==

I don't see it mentioned in this overview. --[[User:Vernes Veranes|Vernes]] 22:03, 17 December 2008 (UTC)

User:Vernes Veranes

2008-12-10T21:44:44Z

Vernes Veranes:

User:Vernes Veranes

2008-12-10T21:43:08Z

Vernes Veranes:

{{SL-hCard|name=[[User:Vernes Veranes|Vernes Veranes]]
|uuid=33345f37-bfc0-4599-ac80-ac9ca77129e2
|mode=size
|photo_x=200
|photo_y=200
|image=
|rezday=01/01/2000
|rezdayISO=2000-01-01
|account=
|partner=
|about=
|achieve=
|links=
}}
This profile is still under construction.

Pet bugs:
* {{jira|VWR-1171}} - Velocity interpolation causes weird physical behaviour client-side - {{User|Vernes Veranes}}

[https://wiki.secondlife.com/w/index.php?title=Special%3AAllpages&from=&namespace=10 Full list of existing templates]

Current project:
* Dom API specificly for xml generation, written in sls.
* <del>Trying to mimic php's implementation (using objects as arguments of function).</del>
* linkedmessage based protocol for inter script communication

Links:
[http://www.slnn.com/article/virtualcomex-laval/ I was qouted]
[http://wiki.secondlife.com/wiki/LSL_Script_Memory]

[[llMessageLinked]](integer linknum, integer num, string str, key id);

{|
|Host Script
|action
|Function script
|-
|Hello
|action
|
|-
|
|return
|Yes?
|}

Where are my borders?

LlGetLocalPos

2008-09-28T00:03:42Z

Vernes Veranes: fixed a bit of code

{{LSL_Function
|func_id=60|func_sleep=0.0|func_energy=10.0
|func=llGetLocalPos|sort=GetLocalPos
|return_type=vector
|func_footnote=If called from the root prim it returns the [[Viewer coordinate frames#Region|position in the region]] unless it is [[llGetAttached|attached]] to which it returns the position relative to the [[Viewer coordinate frames#Attachments|attach point]].
|func_desc
|return_text=that is the position relative ([[Viewer coordinate frames#Local|local]]) to the root.
|spec
|caveats
|constants
|examples=
<lsl>
default
{
touch_start( integer vIntTouched )
{
string vStrMessage = "The touched prim is ";
if (llDetectedLinkNumber( 0 ) > 1)
{
vStrMessage += (string)llVecMag( llGetLocalPos() ) + "m from ";
}
llSay( 0, vStrMessage + "the root prim" );
}
}
</lsl>
|helpers=
There is no llSetLocalPos function.
To set the position of a root prim local to itself you would have to do something like:
<lsl>
SetLocalPosition(vector local_position)
{
vector root_position = llGetPos();
vector absolute_position = root_position + local_position;
llSetPos(absolute_position);
}
</lsl>
|also_functions={{LSL DefineRow||[[llGetRootPosition]]|Gets the root prims global position}}
{{LSL DefineRow||[[llGetPos]]|Gets the prims global position}}
{{LSL DefineRow||[[llSetPos]]|Sets the prims global position}}
|also_tests
|also_events
|also_articles
|notes
|cat1=Movement
|cat2=Prim
|cat3=Object
|cat4
}}

User:Vernes Veranes

2008-09-23T12:19:15Z

Vernes Veranes:

{{SL-hCard|name=[[User:Vernes Veranes|Vernes Veranes]]
|uuid=33345f37-bfc0-4599-ac80-ac9ca77129e2
|mode=size
|photo_x=200
|photo_y=200
|image=
|rezday=01/01/2000
|rezdayISO=2000-01-01
|account=
|partner=
|about=
|achieve=
|links=
}}
This profile is still under construction.

Pet bugs:
* {{jira|VWR-1171}} - Velocity interpolation causes weird physical behaviour client-side - {{User|Vernes Veranes}}

[https://wiki.secondlife.com/w/index.php?title=Special%3AAllpages&from=&namespace=10 Full list of existing templates]

Current project:
* Dom API specificly for xml generation, written in sls.
* <del>Trying to mimic php's implementation (using objects as arguments of function).</del>
* linkedmessage based protocol for inter script communication

Links:
[http://www.slnn.com/article/virtualcomex-laval/ I was qouted]

[[llMessageLinked]](integer linknum, integer num, string str, key id);

{|
|Host Script
|action
|Function script
|-
|Hello
|action
|
|-
|
|return
|Yes?
|}

Where are my borders?

User:Vernes Veranes

2008-09-23T11:46:31Z

Vernes Veranes: just testing

{{SL-hCard|name=[[User:Vernes Veranes|Vernes Veranes]]
|uuid=33345f37-bfc0-4599-ac80-ac9ca77129e2
|mode=size
|photo_x=200
|photo_y=200
|image=
|rezday=01/01/2000
|rezdayISO=2000-01-01
|account=
|partner=
|about=
|achieve=
|links=
}}
This profile is still under construction.

Pet bugs:
* {{jira|VWR-1171}} - Velocity interpolation causes weird physical behaviour client-side - {{User|Vernes Veranes}}

[https://wiki.secondlife.com/w/index.php?title=Special%3AAllpages&from=&namespace=10 Full list of existing templates]

Current project:
* Dom API specificly for xml generation, written in sls.
* <del>Trying to mimic php's implementation (using objects as arguments of function).</del>
* linkedmessage based protocol for inter script communication

[[llMessageLinked]](integer linknum, integer num, string str, key id);

{|
|Host Script
|action
|Function script
|-
|Hello
|action
|
|-
|
|return
|Yes?
|}

Where are my borders?

User:Vernes Veranes

2008-09-23T09:35:46Z

Vernes Veranes:

User:Vernes Veranes

2008-09-23T09:32:56Z

Vernes Veranes:

User:Vernes Veranes

2008-09-22T14:06:15Z

Vernes Veranes: still alive

User:Vernes Veranes

2007-10-25T23:34:42Z

Vernes Veranes:

Talk:LlSendRemoteData

2007-10-23T20:27:02Z

Vernes Veranes:

Has this been implemented yet? This is the first version of the wiki that I've seen without a note specifically saying that it hasn't been implemented.
:The documentation so far has not been fully written yet, this is just a stub article. Please add a note that the functionality of this function has yet to be implemented (or enabled). [[User:Strife Onizuka|Strife Onizuka]] 13:50, 5 March 2007 (PST)

Returns a null_key as message_id, all signs points to "not implemented".--[[User:Vernes Veranes|Vernes Veranes]] 13:27, 23 October 2007 (PDT)

Talk:Batman Follower

2007-06-23T21:23:30Z

Vernes Veranes: Altered comment as stated by Project:Editing Guidelines

==Unneeded Removal==
The content of this page was removed, but when you look at which pages [https://wiki.secondlife.com/wiki/Special:Whatlinkshere/Batman_Follower link] to this one, you see this page was part of a range of pages that explain the different types of grieving that occours in SL.
A good procedure prior to the removal of suspected vandalism would be to check which pages link to the suspected article.

The original article broke the layout and I would like to see the following actions instead:
* Restoring this article to it's prior state
* Formatting article to preserve the layout
--[[User:Vernes Veranes|Vernes Veranes]] 09:59, 22 June 2007 (PDT)

Talk:Sculpted Prims with Wings 3D

2007-06-23T21:13:25Z

Vernes Veranes:

Welcome to the Wings 3D tutorial...

Obviously, it needs a lot more detail.

Don't talk about it. Don't discuss it. Edit it, grow it, improve it.

== Forum references ==

I'd like to point out that basic account users have no access to the SL-Forums. Any information which requires forum access will only be available to a certain group of users.

Should you wish to make the information available to everyone, extra measures need to be made.--[[User:Vernes Veranes|Vernes Veranes]] 14:13, 23 June 2007 (PDT)

Talk:Sculpted Prims with Wings 3D

2007-06-23T21:12:59Z

Vernes Veranes: Forum references

User:Vernes Veranes

2007-06-23T15:20:50Z

Vernes Veranes:

Talk:Batman Follower

2007-06-22T16:59:04Z

Vernes Veranes: Please return article to its original state

==Unneeded Removal==
[[User:Strife Onizuka|Strife Onizuka]] removed the content of this page, but when you look at which pages [https://wiki.secondlife.com/wiki/Special:Whatlinkshere/Batman_Follower link] to this one, you see this page was part of a range of pages that explain the different types of grieving that occours in SL.
Please check first before erasing whole pages.

I would suggest reformating the article, tho.
The original article consisted out of just one image and broke the layout.--[[User:Vernes Veranes|Vernes Veranes]] 09:59, 22 June 2007 (PDT)

Category:LSL XML-RPC

2007-06-22T16:24:03Z

Vernes Veranes: Added a example php script to send a message to a xmlrpc channel in SecondLife

[http://en.wikipedia.org/wiki/XMLRPC XML-RPC] is a standard for sending Procedure Calls (e.g. function calls) to Remote systems. It sends [http://en.wikipedia.org/wiki/XML XML] data over HTTP that remote system then handles.

LSL receives XML-RPC requests and passes them to the prim specified. It may not establish this connect, but it may reply and keep two-way communication with that server. These responses seem to be able to transport a largest amount of data out of Second Life (vs. [[Email]] and {{LSLGC|HTTP}} Requests).

Due to potential copyright issues the following article will be linked rather than imitated, it should get you well on your way:

[http://rpgstats.com/wiki/index.php?title=XMLRPC http://rpgstats.com/wiki/index.php?title=XMLRPC]

=== IMPORTANT IMPLEMENTATION NOTE: ===

The current implementation of XML-RPC only allows ONE request to be queued on the front-end server (xmlrpc.secondlife.com) at a time. Any additional requests to the same data channel overwrite any pending one. This has serious ramifications for the design of XML-RPC communications where the in-world object could receive requests faster than it can respond to them. In addition, the 3-second delay in [[llRemoteDataReply]] exacerbates this problem even more.

The observed issue is this: if you send multiple quick requests to an in-world object via XML-RPC, one which is scripted to perform some processing and then return a response (via llRemoteDataReply), there is a potential for earlier requests to get lost on the front end server (they still should generate [[remote_data]] events, though), and have the response meant for an earlier request end up being passed back to a later one, while the earlier requests will time out back at your external application.

As a result, if you intend to do any serious work with XML-RPC, you will have to design your external client application to manually serialize all requests to each individual RPC channel. That means you have to wait for a response from the previous request before you attempt to send the next one. If you don't care about receiving responses, then this problem is not an issue, as all requests seem to get passed on to the script, regardless of the queueing issue.

Also note that there is NO way to get around the 3-second delay for llRemoteDataReply; you cannot use the multiple-slave-comm-script trick, because XML-RPC channels are *script-specific*, NOT *object-specific*.

For more information, see these forum threads [http://forums.secondlife.com/showthread.php?t=158437 here] and [http://forums.secondlife.com/showthread.php?p=1379244 here].

==Other Resources==
* [http://www.xmlrpc.com/ XMLRPC.com]
* [http://scripts.incutio.com/xmlrpc/ Incutio's XML-RPC PHP library]

==Example==
To initialize a xmlrpc from an external server you'll need some kind of web-application.
One language to create a webapplication in is PHP.
Here is an example of how to send a xmlrpc message to your SL-script from a webserver using PHP:
<code><?php
echo '<pre>';
$channel = ""; //Fill in the channel you are using (key)
$xmldata = "<?xml version=\"1.0\"?><methodCall><methodName>llRemoteData</methodName><params><param><value><struct><member><name>Channel</name><value><string>".$channel."</string></value></member><member><name>IntValue</name><value><int>11261979</int></value></member><member><name>StringValue</name><value><string>happy birthday</string></value></member></struct></value></param></params></methodCall>";
echo sendToHost("xmlrpc.secondlife.com", "POST", "/cgi-bin/xmlrpc.cgi", $xmldata);
echo '</pre>';

function sendToHost($host,$method,$path,$data,$useragent=0)
{
$buf="";
// Supply a default method of GET if the one passed was empty
if (empty($method))
$method = 'GET';
$method = strtoupper($method);

$fp = fsockopen($host, 80, $errno, $errstr, 30);

if( !$fp )
{
$buf = "$errstr ($errno)<br />\n";
}else
{
if ($method == 'GET')
$path .= '?' . $data;
fputs($fp, "$method $path HTTP/1.1\r\n");
fputs($fp, "Host: $host\r\n");
fputs($fp, "Content-type: text/xml\r\n");
fputs($fp, "Content-length: " . strlen($data) . "\r\n");
if ($useragent)
fputs($fp, "User-Agent: MSIE\r\n");
fputs($fp, "Connection: close\r\n\r\n");
if ($method == 'POST')
fputs($fp, $data);
while (!feof($fp))
$buf .= fgets($fp,128);
fclose($fp);
}
return $buf;
}
?></code>

User:Vernes Veranes

2007-06-13T17:10:26Z

Vernes Veranes:

Talk:Sculpted Prims: Sculpt Maps and Textures

2007-06-13T17:04:20Z

Vernes Veranes: /* Layout problems */ update

; Wrong categories - ''Resolved''
: No need for an additional Teen Grid category - I just confirmed Main Grid UUIDs work on the Teen Grid. I once ran into that when using a Scripting Libary script that was written on the MG, the sounds worked. Please remove the Teen Grid category as i'm bad with HTML and in preview messed up the page '^_^. -[[User:Smiley Barry|Smiley Barry]] 11:13, 9 June 2007 (PDT)
:: Thanks! - Done. [[User:Yuu Nakamichi|Yuu Nakamichi]] 15:43, 9 June 2007 (PDT)
:::^_^ Thanks for fixing this - It's pretty obvious that when you move to the Main Grid, you keep your assets, so if UUIDs were grid-dependent you would lose 100% of the functionality O.O .-[[User:Smiley Barry|Smiley Barry]] 04:44, 10 June 2007 (PDT)

; Re-organized page
: I have made a few changes to the page's layout: *) Moved all Linden-Lab provided sculpt map and texture UUIDs into their own table, for reference and in order to separate them from the community effort. *) Consolidated the usage instructions at the top of the page.

; Licensing
: Please add your thoughts on the licensing of shared works over at the [[Project:Village_pump#Policy_Section|Village Pump]]. — [[User:Yuu Nakamichi|Yuu Nakamichi]] 02:41, 4 June 2007 (PDT)

; Rename?

: I suggest to merge this page with the similar effort at [[Sharing_sculpt_maps_and_textures]] and perhaps rename it to [[Sculpted Prims Textures|Sculpted Prims: Sculpt Maps]] or [[Sculpted Prims Textures|Sculpted Prims: Sculpt Maps and Textures]]. Objections? — [[User:Yuu Nakamichi|Yuu Nakamichi]] 16:42, 8 May 2007 (PDT)

... are these "surface normal" images the same as "sculpt textures"? The description of RGB-->XYZ suggests otherwise... --> davan camus

:I believe so, however the image is very large and should be 64x64 to reduce the complexity -- Dedric Mauriac

::I do not believe that this is a valid conversion as it doesn't use the entire image (shouldn't have black areas). -- [[User:Strife Onizuka|Strife Onizuka]] 06:04, 3 May 2007 (PDT)

:::I removed the image and added the ones from the samples provided. --[[User:Dedric Mauriac|Dedric Mauriac]] 07:48, 3 May 2007 (PDT)

Nice table *considers using that style elsewhere on the wiki* -- [[User:Strife Onizuka|Strife Onizuka]] 19:29, 9 May 2007 (PDT)
:: :P [[User:Yuu Nakamichi|Yuu Nakamichi]]

If someone could please remove the 2 "rounded cube" images (I accidentally uploaded the first rounded cube and juicer twice), and the comment now labeled "authors note" which isn't really relevant now having seen them on the preview grid. I'd try to do this myself but don't want to end up messing something up. >_< --[[User:Logan Bauer|Logan Bauer]] 15:12, 17 May 2007 (PDT)

; Wrong Ids given for Main grid sculpt textures

I changed now the ID for the sculpt maps of apple, banana, plate and stem, because they were wrong in here and give some rotation errors if put on prims with the script. I used now the UUIDs from the library. BTW where are the color textures for apple and banana? would be nice to have them, too.--[[User:Sascha Vandyke|Sascha Vandyke]] 10:08, 24 May 2007 (PDT)

== upload directory is not writeable by server ==

i will upload sculpted head with texture whenever i can upload to wiki server. see current error message in message heading. -.- ([[User:Ina Centaur|Ina Centaur]] 02:24, 1 June 2007 (PDT))

== Layout problems (Resolved)==

Resolution 1280 x 1024
The images "Klein Bottle" to "Push Pin" are pushed outside the right side of the layout forcing the webbrowser to add an horizontal scroll bar to view it all
The Images "Apple" to "Plate" at the end are pushed completely below the botom of the web-layout. The are also located in thesame horizontal position as the first images I mentioned.
Also, alot of them are identical. Please replace them with more specific images.
The rest need to be re-positioned or (if not possible) removed to preserve layout. --[[User:Vernes Veranes|Vernes Veranes]] 08:21, 3 June 2007 (PDT)
:It seems [[User:Yuu Nakamichi|Yuu Nakamichi]] fixed the layout.

User:Vernes Veranes

2007-06-03T20:30:17Z

Vernes Veranes: Changes full name to three tildes

User:Vernes Veranes

2007-06-03T20:27:03Z

Vernes Veranes: New page: {{SL-hCard|name=Vernes Veranes |uuid=33345f37-bfc0-4599-ac80-ac9ca77129e2 |mode=size |photo_x=200 |photo_y=200 |image= |rezday=01/01/2000 |rezdayISO=2000-01-01 |account= |partner= |about= ...

{{SL-hCard|name=Vernes Veranes
|uuid=33345f37-bfc0-4599-ac80-ac9ca77129e2
|mode=size
|photo_x=200
|photo_y=200
|image=
|rezday=01/01/2000
|rezdayISO=2000-01-01
|account=
|partner=
|about=
|achieve=
|links=
}}
This profile is still under construction.

Talk:Sculpted Prims: Sculpt Maps and Textures

2007-06-03T15:21:44Z

Vernes Veranes: Layout problems

; Re-organized page
: I have made a few changes to the page's layout: *) Moved all Linden-Lab provided sculpt map and texture UUIDs into their own table, for reference and in order to separate them from the community effort. *) Consolidated the usage instructions at the top of the page. [[User:Yuu Nakamichi|Yuu Nakamichi]] 03:29, 3 June 2007 (PDT)

; Rename?

: I suggest to merge this page with the similar effort at [[Sharing_sculpt_maps_and_textures]] and perhaps rename it to [[Sculpted Prims Textures|Sculpted Prims: Sculpt Maps]] or [[Sculpted Prims Textures|Sculpted Prims: Sculpt Maps and Textures]]. Objections? [[User:Yuu Nakamichi|Yuu Nakamichi]] 16:42, 8 May 2007 (PDT)

... are these "surface normal" images the same as "sculpt textures"? The description of RGB-->XYZ suggests otherwise... --> davan camus

:I believe so, however the image is very large and should be 64x64 to reduce the complexity -- Dedric Mauriac

::I do not believe that this is a valid conversion as it doesn't use the entire image (shouldn't have black areas). -- [[User:Strife Onizuka|Strife Onizuka]] 06:04, 3 May 2007 (PDT)

:::I removed the image and added the ones from the samples provided. --[[User:Dedric Mauriac|Dedric Mauriac]] 07:48, 3 May 2007 (PDT)

Nice table *considers using that style elsewhere on the wiki* -- [[User:Strife Onizuka|Strife Onizuka]] 19:29, 9 May 2007 (PDT)
:: :P [[User:Yuu Nakamichi|Yuu Nakamichi]]

If someone could please remove the 2 "rounded cube" images (I accidentally uploaded the first rounded cube and juicer twice), and the comment now labeled "authors note" which isn't really relevant now having seen them on the preview grid. I'd try to do this myself but don't want to end up messing something up. >_< --[[User:Logan Bauer|Logan Bauer]] 15:12, 17 May 2007 (PDT)

; Wrong Ids given for Main grid sculpt textures

I changed now the ID for the sculpt maps of apple, banana, plate and stem, because they were wrong in here and give some rotation errors if put on prims with the script. I used now the UUIDs from the library. BTW where are the color textures for apple and banana? would be nice to have them, too.--[[User:Sascha Vandyke|Sascha Vandyke]] 10:08, 24 May 2007 (PDT)

== upload directory is not writeable by server ==

i will upload sculpted head with texture whenever i can upload to wiki server. see current error message in message heading. -.- ([[User:Ina Centaur|Ina Centaur]] 02:24, 1 June 2007 (PDT))

== Layout problems ==

Resolution 1280 x 1024
The images "Klein Bottle" to "Push Pin" are pushed outside the right side of the layout forcing the webbrowser to add an horizontal scroll bar to view it all
The Images "Apple" to "Plate" at the end are pushed completely below the botom of the web-layout. The are also located in thesame horizontal position as the first images I mentioned.
Also, alot of them are identical. Please replace them with more specific images.
The rest need to be re-positioned or (if not possible) removed to preserve layout. --[[User:Vernes Veranes|Vernes Veranes]] 08:21, 3 June 2007 (PDT)

Project:Editing Discussion/Archive 02

2007-06-03T00:19:13Z

Vernes Veranes:

This is an open forum for people to ask questions, ala the [http://en.wikipedia.org/wiki/Wikipedia:Village_pump Wikipedia "Village pump"]. Feel free to add your comments below.

== What should this be called? ==

I used "Village pump" as a working name. If it sticks, that's fine. I thought about using a Second Life themed name (e.g. The Telehub), but then realized that there could be confusion between that page and a future [[Telehub]] page which actually describes what Telehubs are. Maybe the "Hippo Pond"? -- [[User:Rob Linden|Rob Linden]] 18:29, 13 May 2007 (PDT)

:That names sounds ok, but what should the namespace be? -- [[User:Strife Onizuka|Strife Onizuka]] 18:44, 13 May 2007 (PDT)

::I'm using the same guidelines as other wikis (like Wikipedia's village pump, at http://en.wikipedia.org/wiki/Project:Village_pump ), though I'll admit it's a little confusing in this case. One really irritating thing about MediaWiki is that it assumes that the name of the wiki ("Second Life Wiki") is a term that is appropriate to use as a namespace identifier, because it works for Wikipedia. So, we either have to shorten the name of the wiki ("SLWiki", which I think was already being used by someone else), or use "Project". I opted for the latter in configuring this wiki. -- [[User:Rob Linden|Rob Linden]] 10:55, 14 May 2007 (PDT)

== Guidelines ==

Given past experiences with the forums, some moderation will need to be done. -- [[User:Strife Onizuka|Strife Onizuka]] 18:44, 13 May 2007 (PDT)

I suggest keeping it simple. If it is the only SL Forum call it 'SL Forum'. If it is the SL People's Forum then call it that.Errol Carter

== Purpose ==

How does this 'forum' differ from the Second Life Forum? (except that this one is accessable by free-accounts)--[[User:Vernes Veranes|Vernes Veranes]] 18:14, 1 June 2007 (PDT)

:This is specifically a place to discuss the wiki itself, not Second Life generally. -- [[User:Rob Linden|Rob Linden]] 18:19, 1 June 2007 (PDT)

== Synchronisation 'mirror' wikis ==

I've noticed that the so called 'mirror' wiki's offer differend kinds and depth of information among themselves.
Is an actual 'synchronisation' wanted and/or possible? --[[User:Vernes Veranes|Vernes Veranes]] 17:19, 2 June 2007 (PDT)

Project:Editing Discussion/Archive 02

2007-06-02T01:14:50Z

Vernes Veranes:

Talk:LlCreateLink

2007-06-02T01:01:06Z

Vernes Veranes: Link failed -- pieces too far apart

== Link failed -- pieces too far apart ==

I find references to the secondlife forum about this problem.
Unfortunatly, alot of people have a free account.
Could the forum discussion about this subject be displayed in this article?
--[[User:Vernes Veranes|Vernes Veranes]] 18:01, 1 June 2007 (PDT)

Talk:Web Textures

2007-03-28T12:59:26Z

Vernes Veranes: /* Possible problem with feature */

Argent, Lets try to keep these article-like, rather than discussion-like. I integrated your comments.

On the white/black list pros and cons, instead of commenting on them, put a subpoint under them to say what would mitigate that con, or just take the con out if you think it's completely bogus. [[User:Gigs Taggart|Gigs Taggart]] 09:54, 26 January 2007 (PST)

Done -- [[User:Argent Stonecutter|Argent Stonecutter]] 12:18, 26 January 2007 (PST)

Gigs, the discussion of privacy concerns needs to be in a separate section. [[User:Argent Stonecutter|Argent Stonecutter]] 06:42, 31 January 2007 (PST)

== Making page moves ==

Please make a request to make a page move rather than making moves by cutting/pasting (just request on [[User talk:Rob Linden]] for now...we'll come up with a more streamlined process later). It's really a pain to merge histories after a cut/paste/redirect move, and much simpler to move the history/discussion and everything in one move. Thanks -- [[User:Rob Linden|Rob Linden]] 10:40, 26 January 2007 (PST)
:Turns out there is a move tab I overlooked. I'll use that from now on. [[User:Gigs Taggart|Gigs Taggart]] 11:37, 26 January 2007 (PST)

== Proxy ==

If a professional can't type in an IP address and port number, they aren't very much of a professional. [[User:Gigs Taggart|Gigs Taggart]] 16:51, 26 January 2007 (PST)

have you ever used an anonymizing proxy chain? -- [[User:Argent Stonecutter|Argent Stonecutter]] 13:38, 28 January 2007 (PST)
== Streaming Media ==
Streaming music is not specific to the "Do Nothing - Just Implement It" section. I've restored that section. Comments about the relationship between streaming media and texture bugs need to be outside any specific section. Here's my thoughts on it:

Yes, streaming media is an issue. There have been scares in the past over streaming media, and for that I've been on the side of "don't worry about it". Why?

Streaming media differs from texture bugs:
* A significant number of people do not use streaming media in SL because:
** The overhead of streaming media has an impact on performance.
** A lot of people have really bad music on their land.
* Streaming music is limited to one parcel. Texture bugs can be anywhere.
* The bandwidth costs of any large streaming-media-based collection scheme are significant.

The result is that it's a far less significant exposure: fewer people are impacted, and even for those people you can only collect data in a small number of places. -- [[User:Argent Stonecutter|Argent Stonecutter]] 13:49, 28 January 2007 (PST)

::Sorry, I undid some of your changes before I saw this. I reorganized the article some to reflect this suggestion. [[User:Gigs Taggart|Gigs Taggart]] 12:00, 29 January 2007 (PST)

== With regards to LSL Implementation ==

Implementation could be simplified thusly:
Instead of the original code:
<pre>
llSetTextureURL(integer face, string url);
llRefreshTextureURL(integer face);
</pre>
<pre>
llSetTextureURL(1, llUrlEncode("http://example.com/getpng.php?text= " + text + "&font=futura&rez=512x512");
llRefreshTextureURL(integer face);
</pre>

We can make use of llSetTexture()'s ability to be supplied with either a string OR a key.

<div style="font-size:140%"><pre>
llSetTexture("http://example.com/example.png",ALL_SIDES);
</pre></div>

Since the LSL/Mono VM first checks if the variable supplied for the texture name is in the object's contents, after checking if it's a UUID, the VM would check if it's a valid URL.

''I like that idea. This could also be applied to llRenderHTML and llRenderText in [[Programmatic Textures]] by allowing the string to be well-formatted XML or the name of a notecard in the objet's inventory'' -- [[User:Argent Stonecutter|Argent Stonecutter]] 06:31, 31 January 2007 (PST)

An alternate method, if Linden Lab were to host/cache the images so the Asset system information could be used to enable Copyright owners to stop content from being used:

<div style="font-size:140%"><pre>
llSetTexture(llExternalAsset("http://example.com/example.png"),ALL_SIDES);
</pre></div>

llExternalAsset() would take any valid URI, and return a UUID that could be used with the appropriate existing LSL function. Any header information found in the file can be applied to the Asset system, so if a web page/image/sound/animation/etc. had creator/author/producer/developer attributes attached to it, the Asset Server will store that information, so it will be displayed in the UI (as opposed to the uploader of content in the current fashion). This would also give copyright holders an avenue to pursue DMCA claims, as the hypothetical system would indicate that they are owner, making things easier except for cases whereby the less scrupulous Resident did something like run an image through the GD libraries to strip out the metadata.

The llExternalAsset() implementation would also benefit greatly from caching, for two reasons:
# You'd obviously not want a new asset to be created every time the script was restarted.
# Lots of people might use the same resource, and
## this would help lower the amount of duplicate information being stored
## this would speed up subsequent queries
### In cases where the Asset Server indicates that the external asset already exists in the system, it'll have the option of attempting to receive a HTTP 304 header from the external source, or
### If one location for the asset is bogged down, the current simulator's local asset server can make the call and supply that image to the local simulator.
###* In this instance, after the local simulator re-downloaded the texture, binary comparison would have to be executed, and if the local sim's texture is different to the other sim's textures, then the other sim's asset servers would replace the old asset with the freshly downloaded one.

[[User:SignpostMarv Martin|SignpostMarv Martin]] 07:20, 29 January 2007 (PST)
::Creating assets for every frame of dyanmic content isn't really even an option. A web cam might be streaming 5 images a second through this. You are assuming that this would be for static images. That defeats the entire point of it. They can just upload the image if it's static. This is not some "save 10L on the upload fee" gimmick, the entire point of this is scriptable dynamic content. [[User:Gigs Taggart|Gigs Taggart]] 11:54, 29 January 2007 (PST)
:::Yeah, but someone streaming a webcam would be better off using the parcel media stuff.
:::Would you be willing to pay for each asset you create with this method ? L$10, L$20, L$30 ?
:::[[User:SignpostMarv Martin|SignpostMarv Martin]] 12:43, 29 January 2007 (PST)

::Linden Labs has already ruled out any scripted generation of assets. -- [[User:Argent Stonecutter|Argent Stonecutter]] 06:32, 31 January 2007 (PST)

::I'll second Gigs' point; this isn't about saving a few cents, it is about immediacy of near-live or live content, and as such no client should be seeing cached content, otherwise we're back to working out how to get multiple residents 'see' the same display concurrently (which inho is the reason for needing web xxx on a prim) --[[User:Alison Wheels|Alison Wheels]] 03:53, 28 March 2007 (PDT)

== Possible problem with feature ==

The way a image has to be intepreted relies on header data.
This header data indicates to the viewer/interpreter info like howmuch data is being send, the pixeldepth etc.
Deliberated corrupted headers could pose new and unpredictable problems.
Also the threat of hiding executable data inside an image might create new types of threats.

I'd like it if someone with some insight on this issue would describe which implementations of this feature would pose the most risk.--[[User:Vernes Veranes|Vernes Veranes]] 05:59, 28 March 2007 (PDT)