Second Life Wiki - User contributions [en]

Talk:HTTP Texture

2010-02-11T18:02:21Z

Cylence Quine: /* Actual discussion */ Realized that the header insinuated that the rest was NOT discussion (when really the other bits are more important than my comment for sure)

== Roadmap ==

Where does this fit in the roadmap ([[Viewer_Roadmap|viewer]]/[[Render_Roadmap|rendering]])? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 13:12, 31 March 2009 (UTC) 
P.S. It's time to update the roadmaps.

:I see, it falls under [[Texture Pipeline Improvements]] (which also needs updating). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 13:14, 31 March 2009 (UTC)

Remember to add http texture handling for HUDs as well, which would be most welcome to many people (newsflash HUD, recent post HUD for flickr etc.) Same for media streams on HUDs... might have to get in in one go (http textures + media stuff on HUDs), as it is similar. [[User:Silver Key|Silver Key]] 11:18, 19 May 2009 (UTC)

== Issues ==
The privacy and security issues here must not be ignored. There has already been one security update to fix an remote code execution exploit you could apply to anyone, if you could find their IP address while they were online. People are already using media streams to IP-stalk users. This has to be optional, default to disabled, and be selectively enabled. You have to be able to accept textures from (for example) Flickr without letting griefer.example.com set a web-bug on you. -- [[User:Argent Stonecutter|Argent Stonecutter]] 14:11, 1 April 2009 (UTC)

== PJIRA ==

"There are still quite a bit of crashes here and there... Don't use such a build for your regular SL activities (search for bugs logged against http-texture branch in PJIRA for more info)"
:Has the http-texture entry for "Affected Version" been renamed to "Snowglobe test build"? If so, we should probably link to [http://jira.secondlife.com/secure/IssueNavigator.jspa?reset=true&&type=1&resolution=-1&version=10435&status=1&status=3&status=4&sorter/field=issuekey&sorter/order=DESC&sorter/field=updated&sorter/order=DESC&sorter/field=votes&sorter/order=DESC this search permalink]
:--[[User:Boroondas Gupte|Boroondas Gupte]] 21:06, 21 May 2009 (UTC)

== Non-technical discussion ==
Is this really so low-priority that its taken over a year or two to implement? With the way "the Web" is going, this is becoming more and more of an important feature! Does anyone have any information at all on when we might see this make into the code?

[[User:Cylence Quine|Cylence Quine]] 18:00, 11 February 2010 (UTC)

Talk:HTTP Texture

2010-02-11T18:00:21Z

Cylence Quine:

== Roadmap ==

Where does this fit in the roadmap ([[Viewer_Roadmap|viewer]]/[[Render_Roadmap|rendering]])? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 13:12, 31 March 2009 (UTC) 
P.S. It's time to update the roadmaps.

:I see, it falls under [[Texture Pipeline Improvements]] (which also needs updating). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 13:14, 31 March 2009 (UTC)

Remember to add http texture handling for HUDs as well, which would be most welcome to many people (newsflash HUD, recent post HUD for flickr etc.) Same for media streams on HUDs... might have to get in in one go (http textures + media stuff on HUDs), as it is similar. [[User:Silver Key|Silver Key]] 11:18, 19 May 2009 (UTC)

== Issues ==
The privacy and security issues here must not be ignored. There has already been one security update to fix an remote code execution exploit you could apply to anyone, if you could find their IP address while they were online. People are already using media streams to IP-stalk users. This has to be optional, default to disabled, and be selectively enabled. You have to be able to accept textures from (for example) Flickr without letting griefer.example.com set a web-bug on you. -- [[User:Argent Stonecutter|Argent Stonecutter]] 14:11, 1 April 2009 (UTC)

== PJIRA ==

"There are still quite a bit of crashes here and there... Don't use such a build for your regular SL activities (search for bugs logged against http-texture branch in PJIRA for more info)"
:Has the http-texture entry for "Affected Version" been renamed to "Snowglobe test build"? If so, we should probably link to [http://jira.secondlife.com/secure/IssueNavigator.jspa?reset=true&&type=1&resolution=-1&version=10435&status=1&status=3&status=4&sorter/field=issuekey&sorter/order=DESC&sorter/field=updated&sorter/order=DESC&sorter/field=votes&sorter/order=DESC this search permalink]
:--[[User:Boroondas Gupte|Boroondas Gupte]] 21:06, 21 May 2009 (UTC)

== Actual discussion ==
Is this really so low-priority that its taken over a year or two to implement? With the way "the Web" is going, this is becoming more and more of an important feature! Does anyone have any information at all on when we might see this make into the code?

[[User:Cylence Quine|Cylence Quine]] 18:00, 11 February 2010 (UTC)

Talk:Linden Vehicle Tutorial

2008-08-29T04:19:31Z

Cylence Quine:

Hi,

About Vertical Attractor and banking and considering a boat, it's wrong to say a boat always keeps its up-side up. If you pay attention on a boat's (a motor boat of course) behavior you will see that it depends on its size.

A small boat turns a bit like a motorcycle so that it leans into the turn while a big boat will turn more like a car so that in leans outside of the turn (slightly of course). So the VEHICLE_BANKING_EFFICIENCY value has to be negative for a big boat.

When we think about a car, a bus or a truck the behavior is the same except that we have to separate the steel frame from the wheels. the wheels, normally stay in contact with the ground while the steel frame leans outside of the turn. In that particular case, I don't know how SL manage the vehicle. Do we have to manage the steel frame by ourselves?

[[User:Colomben Bailey|Colomben Bailey]] 13:27, 14 August 2008

This is not so much a vehicle tutorial as it is a vehicle-related function tutorial. I'd really like to see 1) a complete example script in this tutorial and 2) a little detail, at all, regarding how an agent engages the vehicle and disengages from it. Otherwise, great data.

[[User:Cylence Quine|Cylence Quine]] 21:18, 28 August 2008 (PDT)

Talk:Linden Vehicle Tutorial

2008-08-29T04:18:26Z

Cylence Quine:

Hi,

About Vertical Attractor and banking and considering a boat, it's wrong to say a boat always keeps its up-side up. If you pay attention on a boat's (a motor boat of course) behavior you will see that it depends on its size.

A small boat turns a bit like a motorcycle so that it leans into the turn while a big boat will turn more like a car so that in leans outside of the turn (slightly of course). So the VEHICLE_BANKING_EFFICIENCY value has to be negative for a big boat.

When we think about a car, a bus or a truck the behavior is the same except that we have to separate the steel frame from the wheels. the wheels, normally stay in contact with the ground while the steel frame leans outside of the turn. In that particular case, I don't know how SL manage the vehicle. Do we have to manage the steel frame by ourselves?

Col.

This is not so much a vehicle tutorial as it is a vehicle-related function tutorial. I'd really like to see 1) a complete example script in this tutorial and 2) a little detail, at all, regarding how an agent engages the vehicle and disengages from it. Otherwise, great data.

[[User:Cylence Quine|Cylence Quine]] 21:18, 28 August 2008 (PDT)

User:Cylence Quine

2008-06-02T18:36:39Z

Cylence Quine: /* Ruby on Rails and LSL combined */

= Technologies =
These are a few of my favorite things.

== Ruby on Rails ==
An MVC-based Web framework for Ruby.

== LSL ==
The scripting language of Second Life. LSL is used to manipulate nearly anything in Second Life whether that manipulation be visual movement or a prim, texture/color changes or even audio.

== Ruby on Rails and LSL combined ==
Ruby on Rails is a perfect language for making an API. LSL has the ability to both talk to the Internet using HTTP calls (GET, POST, PUT and DELETE) and receive requests from the Internet by starting an XML-RPC server in a prim, making this combination great for creating web services.

Using this combination, one can have in-world prims that can interact with an Internet web site and vise versa.

User:Cylence Quine

2008-06-02T17:20:35Z

Cylence Quine: New page: = Technologies = These are a few of my favorite things. == Ruby on Rails == An MVC-based Web framework for Ruby. == LSL == The scripting language of Second Life. LSL is used to manipulat...

= Technologies =
These are a few of my favorite things.

== Ruby on Rails ==
An MVC-based Web framework for Ruby.

== LSL ==
The scripting language of Second Life. LSL is used to manipulate nearly anything in Second Life whether that manipulation be visual movement or a prim, texture/color changes or even audio.

== Ruby on Rails and LSL combined ==
Ruby on Rails is a perfect language for making an API. LSL has the ability to both talk to the Internet using HTTP calls (GET, POST, PUT, DELETE) and receive requests from the Internet by starting an XML-RPC server in a prim, making this combination great for creating web services.

Using this combination, one can have in-world prims that can interact with an Internet web site and vise versa.

LlListen

2008-06-01T23:48:25Z

Cylence Quine:

{{LSL_Function
|func=llListen
|sort=Listen
|func_id=25|func_sleep=0.0|func_energy=10.0
|return_type=integer
|return_text=that can be used to deactivate or remove the listen.
|p1_type=integer|p1_name=channel|p1_desc=any valid integer (-2147483648 through 2147483647).
|p2_type=string|p2_name=name|p2_desc=filter for specific prim or avatar name
|p3_type=key|p3_name=id|p3_desc=filter for specific prim/avatar [[UUID]].
|p4_type=string|p4_name=msg|p4_desc=filter for specific chat message
|func_desc=Sets a callback for '''msg''' on '''channel''' from '''name''' and '''id'''.
|func_footnote=If '''msg''', '''name''' or '''id''' are blank they are not used to filter incoming messages.
If '''id''' is an invalid key or a [[NULL_KEY|null key]], it is considered blank. 
|spec=For the [[listen]] [[event]] to be triggered it must first match the criteria set forth by the filters; only when all the criteria have been met is a listen event generated. First the message must have been transmitted on channel '''channel'''. If '''name''' is set then the speaker's name must match '''name''' exactly. If '''id''' is a valid, non-[[NULL_KEY|null]] key then the speaker's key must be equivalent. If '''msg''' is set then the spoken message must match '''msg''' exactly.
|also_functions={{LSL DefineRow||[[llListenRemove]]|Removes a listen}}
{{LSL DefineRow||[[llListenControl]]|Enables/Disables a listen}}
{{LSL DefineRow||[[llWhisper]]|Sends chat limited to 10 meters}}
{{LSL DefineRow||[[llSay]]|Sends chat limited to 20 meters}}
{{LSL DefineRow||[[llShout]]|Sends chat limited to 100 meters}}
{{LSL DefineRow||[[llRegionSay]]|Sends chat limited current sim}}
|also_events={{LSL DefineRow||[[listen]]|}}
|also_tests
|also_articles
|notes=Avoid channel 0 and set name or id where possible to avoid ([http://rpgstats.com/wiki/index.php?title=Lag Lag]). llListen(0,"","","") can be extremely laggy as it listens to all chat from everyone in chat range and so it should be avoided at all cost.
|constants={{LSL Constants/Chat}}
|caveats=*On [[state]] change or [[llResetScript|script reset]] all listens are removed automatically.
**A state change can be used as a shortcut to releasing listens.
*Only 65 listens can simultaneously be open in any single script.
**If this number is exceeded ''Script run-time error'' and ''Too Many Listens'' errors occur.
*Chat on negative channel numbers cannot be generated by the client except with dialog boxes.
**This makes it ideal for object2object communications.
**This may just be an artificial limitation placed on the client and not the underlying protocol.
*Once a listen is registered it's filters cannot be updated, if the listen is register to [[llGetOwner]], the listen will remain registered to the old owner upon owner change.
**[[CHANGED_OWNER|Owner change]] can be detected with the [[changed]] event.
**To work around this the old listen will need to be closed and a new one opened for the new owner.
|examples=
Trivial example to listen to any chat from the object owner and respond once. To reduce lag and avoid spamming surrounding users, it is vastly preferable to listen on channels other than 0 and to trigger the listen event by chatting on an alternative channel such as '/5 hello'.
<lsl>// says beep to owner the first time owner says something in main chat;
integer listen_handle;

default
{
state_entry()
{ // Registers the listen to the owner of the object at the moment of the call.
// This does not automatically update when the owner changes.
// Change 0 to another positive number to listen for '/5 hello' style of chat.
listen_handle = llListen(0, "", llGetOwner(), "");
}
listen( integer channel, string name, key id, string message )
{
llOwnerSay("beep");
// Stop listening until script is reset
llListenRemove(listen_handle);
}
on_rez(integer param)
{ // Triggered when the object is rezed, like after the object had been sold from a vendor
llResetScript();//By resetting the script on rez it forces the listen to re-register.
}
changed(integer mask)
{ // Triggered when the object containing this script changes owner.
if(mask & CHANGED_OWNER)
{
llResetScript();
}
}
}</lsl>
|cat1=Communications
|cat2=Chat
|cat3
|cat4
}}

Talk:LlSetPrimURL

2008-05-15T05:16:26Z

Cylence Quine: New page: Deprecated to be replaced by what? This seems like a rather important function. ~~~~

Deprecated to be replaced by what? This seems like a rather important function. [[User:Cylence Quine|Cylence Quine]] 22:16, 14 May 2008 (PDT)

Energy

2008-04-02T01:34:22Z

Cylence Quine:

{{multi-lang}}
When certain dynamic functions are called from a script running on a physical object, the object loses energy. As the object loses energy, the effectiveness of dynamic functions on the object decreases. Energy is mostly relevant for large physical objects. For objects the size of an avatar or smaller, energy effects can generally be ignored.

*What does "effectiveness" mean in this context?

Non-physical objects need not worry about energy, as main way energy is reduced is through llPushObject, llApplyImpulse, and llSetForce. Even very massive non-physical objects can run almost any script just as well as one 100x smaller.

Please describe how it works! Answer at least the following questions:
* What's the energy content of an object?
** It is a value from 0.0 to 1.0. It is not analogous to RL energy.
* Is it possible to calculate the energy consumption of an action, e.g., running a script;
** Yes, but it is involved.
* When the energy is consumed how much time does it take to build it up again?
** 200/mass units of energy per second.
* During the energy build-up can we execute all actions needing less energy than the energy available?
** Yes, but their effect will be diminished if the energy is less than 1.0.

Also
* Does the script totally stop when it runs out of energy? Or pause?
** Neither. The script is executed regardless of the energy level. Only the effect of those functions requiring energy is diminshed.
* Are events that occur during such an "energy pause" queued up so when it is restarted they are then triggered?
** No. There is no pause in the script, nor queued events.
* At what rate does energy return (so one can add pauses in scripts for energy to return)?
** 200/mass units of energy per second.
* Does an object's energy exist per-prim, or per-object (link sets)?
** Per object.
* How does Energy get treated on Avatars?
** Under normal circumstances, an avatar is not subject to energy concerns.
:: ''This isn't precisely accurate... attachments on the avatar seem to have the same energy limitations as unattached objects -- [[User:Argent Stonecutter|Argent Stonecutter]] 10:13, 4 August 2007 (PDT)''
* How is energy used in scripts related to lag?
** No direct relationship, to the extent that lag refers to things not happening in a timely manner. But energy constraints can make the movement of large physical objects erratic, which might be blamed on lag.

More (from [[User:Argent Stonecutter|Argent Stonecutter]] 07:18, 10 May 2007 (PDT))
* If Energy is on a scale of 0.0-1.0, and I use [[llShout]] which uses "10.0 Energy", where do the missing 9.0 energy units come from? Can you elaborate on just what this means?
: ''Hypothesis: if I have an object with a mass of 1.0 kg it can call llShout 20 times a second, and if it calls llShout 40 times in a second this will leave it with 0.5 Energy. Is this correct?''
* If you have 0.5 Energy, does this mean [[llShout]] would have a range of 50 meters instead of 100 meters?
** No, distance is unaffected by energy.

Template:LSL Constants/llRequestAgentData

2008-01-18T05:39:12Z

Cylence Quine:

<noinclude>{|{{Prettytable}}</noinclude>
{{!}} {{LSL Const|DATA_ONLINE|integer|1}}
{{!}} {{#var:value}}
{{!}} ([[integer]]) {{HoverText|boolean|TRUE or FALSE}}
{{!}} colspan="4" {{!}} If the requested agent is online
{{!}}-
{{!}} {{LSL Const|DATA_NAME|integer|2}}
{{!}} {{#var:value}}
{{!}} [[string]]
{{!}} colspan="4" {{!}} The requested agents name
{{!}}-
{{!}} {{LSL Const|DATA_BORN|integer|3}}
{{!}} {{#var:value}}
{{!}} [[string]]
{{!}} colspan="4" {{!}} The account creation/"born on" date as a string in an ISO 8601 format of YYYY-MM-DD.
{{!}}-
{{!}} {{LSL Const|DATA_RATING|integer|4}}
{{!}} {{#var:value}}
{{!}} [[llCSV2List]]()
{{!}} colspan="4" {{!}} Deprecated: Returns [0, 0, 0, 0, 0, 0] Use to return: [pos_behavior, neg_behavior, pos_appearance, neg_appearance, pos_building, neg_building]
{{!}}-
{{!}} rowspan="3" {{!}} {{LSL Const|DATA_PAYINFO|integer|8}}
{{!}} rowspan="3" {{!}} {{#var:value}}
{{!}} rowspan="3" {{!}} ([[integer]]) {{HoverText|mask|PAYMENT_INFO_* flags}}
! colspan="3" {{!}} Flag
! Description
{{!}}-
{{!}} colspan="2" {{!}} {{LSL Const|PAYMENT_INFO_ON_FILE|integer|hex=0x1|c=If payment info is on file.}}
{{!}} {{#var:value}}
{{!}} {{#var:comment}}
{{!}}-
{{!}} colspan="2" {{!}} {{LSL Const|PAYMENT_INFO_USED|integer|hex=0x2|c=If payment info has been used.}}
{{!}} {{#var:value}}
{{!}} {{#var:comment}}
<noinclude>|}</noinclude>