Second Life Wiki - User contributions [en]

Talk:Build the Viewer on Linux

2009-08-05T23:20:05Z

Corto Maltese: /* gnu/stubs-32.h : No such file or directory */ new section

I had to add "class LLUICtrlFactory;" to llui/lluictrl.h and llui/llviewborder.h to avoid a bunch of problems about that class missing --[[User:Eddy_Stryker|Eddy Stryker]]

----

== llmozlib ==

As [https://lists.secondlife.com/pipermail/sldev/2007-February/000545.html Tofu wrote (Feb 23 2007)], "you shouldn't generally need to download and build LLMozLib for a SL viewer build unless you're hacking on LLMozLib itself or porting SL to a platform which we don't supply pre-built libraries for".

Nonetheless, there's a need of instructions on
*how to '''disable''' llmozlib in [[Source_archive#2007-Feb-20|FL-1.13.3.58185]] and [[Source_archive#2007-Feb-24|FL-1.13.3.58390]] as explained at [https://lists.secondlife.com/pipermail/sldev/2007-February/thread.html#487 a thread of SLDev@lists.secondlife.com]
**Add MOZLIB=no to your Scons build command when compiling the source
'''and/or'''
*how to compile those versions '''with''' the [https://lists.secondlife.com/pipermail/sldev/2007-February/000545.html current llmozlib from ubrowser.com]
--[[User:Boroondas Gupte|Boroondas Gupte]] 06:10, 26 February 2007 (PST)
:I edited it so it's complete if you want llMozLib off, getting llMozlib compiled and working with the viewer is actually nontrivial, compiling llMozLib is just about as hard as compiling the viewer itself! [[User:Gigs Taggart|Gigs Taggart]] 08:06, 27 February 2007 (PST)
::What functionality is lost if you do not use llmozlib? [[User:Meyaden Beck|Meyaden Beck]] 20:11, 12 April 2007 (PDT)
:::You won't have any in-viewer browser windows (e.g. F1-Help) as well as no HTML login screen (you'll get the old login screen with the static picture instead). Opening pages in an external browser from within SL (e.g. links in chat/IM) won't be affected, nor will be inworld actions triggered by your external browser (e.g. SLUrl). --[[User:Boroondas Gupte|Boroondas Gupte]] 06:57, 7 May 2007 (PDT)

=== mozjs ===

A similar problem seems to be present with [[Source_archive#2007-Feb-27|beta-1.13.4.3]], only that it's '''-lmozjs''' not '''-lllmozlib''' that's failing at linktime. I can't even seem to locate the corresponding header file (expected filename 'mozjs.h') so it might well be that the problem only looks similar to the llmozlib one, but actually isn't. I'll post to the [sldev] list as soon as I have investigated this further. --[[User:Boroondas Gupte|Boroondas Gupte]] 11:22, 1 March 2007 (PST)

=== FMOD ===

This non-open-source audio library is a continuous source of irritation to open-source devotees and 64-bit devotees alike (it only comes in 32-bit), so it needs early replacement. But not replacement by another full-function audio subsystem. A much better approach is available.

Every platform has audio players available, or 20 of them, so why reinvent the wheel and bloat the client unnecessarily? Write only a software mixer to combine the various audio sources together, and present the output at an Icecast-type stream listener interface on a local socket. Then the local player of choice can connect to it just like to any Internet radio, and you're done. You can even launch the player to make it seamless.

I bet that this would make the client shrink enormously too! And the icing on the cake is that the separate player will naturally run on another core on modern multicore machines. --[[User:Morgaine Dinova|Morgaine Dinova]] 18:03, 12 October 2007 (PDT)

== Help? ==

Would it be useful to add a blurb on where people can get help compiling, specifically in Linux. Or at least an internal link to another wiki page that has a list of places to get help in each version, MAC/WIN/LIN/BSD/(however far people want to break it down, etc.).

== little helper script ==

For those of you who don't want to copy-paste from this article for every build they compile, I put a little bash script I'd liked to share in my user space: [[User:Boroondas_Gupte/unpack.sh]]. It just does a part of what's explained in this article. --[[User:Boroondas Gupte|Boroondas Gupte]] 09:59, 6 March 2007 (PST)

== Error? ==

Under the heading "fix shell scripts" there is a header file listed. can someone else confirm this should not be in that list, and if it should, why does it not have a #!/bin/sh at the top of it?

* linden/libraries/i686-linux/include/apr-1/arch/unix/apr_arch_threadproc.h

== Required Headers ==

Is there a reason that the instructions include copying header files to the source tree?

I have not attempted the install yet, that will probably be in a few days for me. However, most packages don't require the copying of header files from any standard lib into their own source directories. I am not sure if this practice is really a good one.

Will the package not compile if the headers are simply in their proper locations? If so, this is something that the developers may want to consider fixing. I would personally consider that a bug.

Normal procedure with most apps is to have the librarries propperly installed, and have the code or makefile written so that it looks in the right place. [[User:Meyaden Beck|Meyaden Beck]] 19:41, 12 April 2007 (PDT) (I forgot to sign before I think)

Autoconf is a wonderful tool. :P

:This setup is so that a fixed build of included libraries are setup for each branch and platform. The host platform can change independently of the SL build. Also, isolation of these libraries greatly reduce debug issues. There are a few patches to use the host platform's installed libraries instead. However, a few changes still need to be made for consistency. [[User:Dzonatas Sol|Dzonatas Sol]] 11:58, 12 April 2007 (PDT)

::Hmmm... I see, I think. My next question (and if I get the time I may fix this one myself), why the choice to pretty much ignore compilation of llMozlib? Stating that "Compiling it is a pain, and this is how you disable it", doesn't look good. I haven't gotten that far in my current Linux install yet. I just finished installing XFce4, but as soon as I get OpenOffice.org and Blender installed, I will likely move on to Second Life. When I do, I will go through the steps of compiling llMozlib and take notes on what I did to make it work. :-) I should probablly also make sure to include a warning that I am using an LFS build. However, the instructions the LFS site uses to build most packages should theoretically work for just about any system. ^_^[[User:Meyaden Beck|Meyaden Beck]] 19:41, 12 April 2007 (PDT)

----
Hmm. I believe older versions of this page clearly showed instractions for those who just want to compile viewer only and for those who want to build everything. I believe the older style is better.

Are there anyone who objects to such reorganization?

--[[User:Alissa Sabre|Alissa Sabre]] 22:51, 8 June 2007 (PDT)

I agree to every kind of reorganization, since this page is a bit messy. We should provide a simplified version of it, at least. I think it's a bit scary for newbies. So today I moved the 'Packaging errors' section to Common compilation problems page (we may want to give more visibility to that link); I removed the 'Fix Shell Scripts' because I think it has been fixed; I added some questions where I think we need to being more informative; It looks like you only need to add FMOD=no to the scons command, and I think we should give this information only - i'm not sure about this, so in the meantime I just made some changes to both 'Prerequisites' and 'Copy headers and libraries into the source tree' sections.

Please reverse my changes if not appropriate! I'm OK with a reorganization of this page. Pleae do a new page version for every edit, using proper comments, so revert is easier.
--[[User:Signore Iredell|Signore Iredell]] 06:42, 9 June 2007 (PDT)

----

Note that gcc-3.4 is NOT required, patches to fix compiling on gcc 4.x were among the first to be merged after the source release. I've been compiling with gcc 4.x from the beginning and it works fine. I'm not sure how to rework the article though, SConstruct is hardwired to call g++-3.4 which won't even work with Fedora's compat compiler (which is named g++34), which does not seem to be mentioned in the article either. Please merge VWR-218 ;P [[User:Seg Baphomet|Seg Baphomet]] 12:39, 13 June 2007 (PDT)

== Gentoo 64bits? ==

Hello,

Did anyone get it compile on Gentoo 64bits? [[User:Iann Alderson|Iann Alderson]] 04:19, 7 October 2007 (PDT)
* Needed packages:
** dev-libs/boost
** dev-util/scons
** media-libs/gstreamer

Ok, it compiles alright for well over an hour, which is better than I expected. ;o)

But the, I get

<pre>
cc1plus: warnings being treated as errors
/tmp/yann/usr/local/src/linden/indra/i686-linux-client-release/newview/viewer.cpp: In function 'BOOL do_elfio_glibc_backtrace()':
/tmp/yann/usr/local/src/linden/indra/i686-linux-client-release/newview/viewer.cpp:2423: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
scons: *** [/tmp/yann/usr/local/src/linden/indra/i686-linux-client-release/newview/viewer.o] Error 1
scons: building terminated because of errors.
</pre>

Does anyone know what that means? Thanks, [[User:Iann Alderson|Iann Alderson]] 11:24, 7 October 2007 (PDT)

It's been a while, but for completeness's sake: gcc lets one make the compiler very finicky, so that things that are normally just warnings are considered errors that will make the compile fail--that way you can fix more stuff at compile time, rather than leaving possible errors to barf at runtime. In this particular case, someone has a *printf() call that has a constant format string, so that the compiler can type check the corresponding arguments, and there's a %d (which is used to print int values) corresponding to a value of type size_t, which is typically unsigned, and for a 64-bit system may well be larger than int, which is likely to make printf fail to properly access any following values to be printed. --[[User:Melissa Yeuxdoux|Melissa Yeuxdoux]] 01:33, 31 December 2008 (UTC)

http://pastebin.ca/729141

== OpenAL ==
OpenAL should be listed under the "Installing the required libraries" section, right? libopenal-dev and libalut-dev -- [[User:Everclear Quandry|Everclear Quandry]] 02:58, 15 March 2009 (UTC)

== gnu/stubs-32.h : No such file or directory ==

It seemed that on Ubuntu (at least) installing the package libstdc++6 add the library libstdc++.so.6.

SL build requires a link libstdc++.so

Typing this command fix the issue:

sudo ln -s /usr/lib32/libstdc++.so.6 /usr/lib32/libstdc++.so

HTTP Post request to a PHP server

2008-07-02T21:46:42Z

Corto Maltese: /* How to use */

{{LSL Header}}

== How to use ==
Second life allow script to make requests to a web site.

The command let you send Post data to PHP.
The format of the HTTP Post is however a bit tricky.

With this library let you call a PHP page and post as many variables in your call as you want.

On top of that I introduce a little checksum/password sytem to limit potential abuse.

== How to use ==

'''The second life script'''

In the beginning of your script you must copy the xrequest function
and also choose a SECRET_NUMBER and a SECRET_STRING.
In SL you should also make sure that the script is not visible to other people than yourself (this is the default access right).

<lsl>
integer SECRET_NUMBER=123456789;
string SECRET_STRING="XD4@5#-m";

xrequest(list l)
{
integer i;
string body;
integer len=llGetListLength(l) & 0xFFFE; // make it even
for (i=0;i<len;i+=2)
{
string varname=llList2String(l,i);
string varvalue=llList2String(l,i + 1);
if (i>0) body+="&";
body+=llEscapeURL(varname)+"="+llEscapeURL(varvalue);
}
string hash=llMD5String(body+llEscapeURL(SECRET_STRING),SECRET_NUMBER);
http_request_id = llHTTPRequest(url+"?hash="+hash,[HTTP_METHOD,"POST",HTTP_MIMETYPE,"application/x-www-form-urlencoded"],body);
}
</lsl>

To make a call to the function you have to provide 2 parameters:

For example:

xrequest("http://www.yourserver.com/your_page.php",["parameter1",123,"parameter2","parameter2 value"]);

The first parameter is the address of the webpage which will process your request. I assume, you own a website which supports PHP (about any version).

The second parameter is a list containing the parameters you want to pass to the page.
They will be sent to the page as if they had been type in a WebForm.
The list can be empty [] or contain any number of 'variable name','variable value' pairs.

'''The PHP Page'''

The php page must contains the function below, if you're a PHP wiz, you also include it inside another file.

Note that the page must be modified to contain your own SECRET_NUMBER.
Your page will then use the function checkHash() to make sure the correct password was used.
If the password is wrong, the page won't run any further.

If the password is right you can then read the content of the parameters using a simple $_POST["parameter_name"]

<php>
<?php
// this function tweak slightly urlencode to make it behave exactly like llEscapeURL in Second Life.
function llEscapeURL($s)
{
$s=str_replace(
array(" ","+","-",".","_"),
array("%20","%20","%2D","%2E","%5F"),
urlencode($s));
return $s;
}

// this my main SL page XML-RPC page
function checkHash()
{
global $body;
$hash=$_GET["hash"];
$body="";
$cpt=0;
$SECRET_NUMBER=123456789;
$SECRET_STRING="XD4@5#-m";

foreach ($_POST as $name => $value) {
if ($cpt++>0) $body.="&";
if (get_magic_quotes_gpc()) {
// $name = stripslashes($name); not a good idea though
$value = stripslashes($value);
$_POST[$name]=$value;
}
$body.=llEscapeURL($name)."=".llEscapeURL($value);
}
$calcHash=md5($body.$SECRET_STRING.':'.$SECRET_NUMBER);
if ($hash!=$calcHash)
{
sleep(2); // slow down the requests
echo "result=FAIL\nMSG=Invalid request.";
die;
}
}

checkHash();
// You can use the parameters here by simply using $_POST["parameter_name"]
echo "OK";
?>
</php>

I hope it helps.
Don't hesitate to ask any question to Corto Maltese or improve this page.

{{LSLC|Library}}

HTTP Post request to a PHP server

2008-07-02T21:44:08Z

Corto Maltese: /* How to use */

{{LSL Header}}

== How to use ==
Second life allow script to make requests to a web site.

The command let you send Post data to PHP.
The format of the HTTP Post is however a bit tricky.

With this library let you call a PHP page and post as many variables in your call as you want.

On top of that I introduce a little checksum/password sytem to limit potential abuse.

== How to use ==

'''The second life script'''

In the beginning of your script you must copy the xrequest function
and also choose a SECRET_NUMBER and a SECRET_STRING.
In SL you should also make sure that the script is not visible to other people than yourself (this is the default access right).

<lsl>
integer SECRET_NUMBER=123456789;
string SECRET_STRING="XD4@5#-m";

xrequest(list l)
{
integer i;
string body;
integer len=llGetListLength(l) & 0xFFFE; // make it even
for (i=0;i<len;i+=2)
{
string varname=llList2String(l,i);
string varvalue=llList2String(l,i + 1);
if (i>0) body+="&";
body+=llEscapeURL(varname)+"="+llEscapeURL(varvalue);
}
string hash=llMD5String(body+llEscapeURL(SECRET_STRING),SECRET_NUMBER);
http_request_id = llHTTPRequest(url+"?hash="+hash,[HTTP_METHOD,"POST",HTTP_MIMETYPE,"application/x-www-form-urlencoded"],body);
}
</lsl>

To make a call to the function you have to provide 2 parameters:

For example:

xrequest("http://www.yourserver.com/your_page.php",["parameter1",123,"parameter2","parameter2 value"]);

The first parameter is the address of the webpage which will process your request. I assume, you own a website which supports PHP (about any version).

The second parameter is a list containing the parameters you want to pass to the page.
They will be sent to the page as if they had been type in a WebForm.
The list can be empty [] or contain any number of 'variable name','variable value' pairs.

'''The PHP Page'''

The php page must contains the function below, if you're a PHP wiz, you also include it inside another file.

Note that the page must be modified to contain your own SECRET_NUMBER.
Your page will then use the function checkHash() to make sure the correct password was used.
If the password is wrong, the page won't run any further.

If the password is right you can then read the content of the parameters using a simple $_POST["parameter_name"]

<php>
<?php
// this function tweak slightly urlencode to make it behave exactly like llEscapeURL in Second Life.
function llEscapeURL($s)
{
$s=str_replace(
array(" ","+","-",".","_"),
array("%20","%20","%2D","%2E","%5F"),
urlencode($s));
return $s;
}

// this my main SL page XML-RPC page
function checkHash()
{
global $body;
$hash=$_GET["hash"];
$body="";
$cpt=0;
$SECRET_NUMBER=123456789;
$SECRET_STRING="XD4@5#-m";

foreach ($_POST as $name => $value) {
if ($cpt++>0) $body.="&";
if (get_magic_quotes_gpc()) {
// $name = stripslashes($name); not a good idea though
$value = stripslashes($value);
$_POST[$_NAME]=$value;
}
$body.=llEscapeURL($name)."=".llEscapeURL($value);
}
$calcHash=md5($body.$SECRET_STRING.':'.$SECRET_NUMBER);
if ($hash!=$calcHash)
{
sleep(2); // slow down the requests
echo "result=FAIL\nMSG=Invalid request.";
die;
}
}

checkHash();
// You can use the parameters here by simply using $_POST["parameter_name"]
echo "OK";
?>
</php>

I hope it helps.
Don't hesitate to ask any question to Corto Maltese or improve this page.

{{LSLC|Library}}

Category:LSL Library

2008-07-02T21:25:22Z

Corto Maltese: /* Support Script Library */

{{Multi-lang}}{{LSL Header}}{{RightToc}}
==Script Library==

<div id="box">
<div style="padding: 0.5em 0.5em 1.5em">
Come to this page to see complex examples that show how to combine parts of LSL.

Go to the [[:Category:LSL Examples|LSL Examples]] page to see brief examples of how to use parts of LSL

Why collect complex examples here? Well, ...

There are many [[script|scripts]] that have become buried in the [http://forums.secondlife.com/forumdisplay.php?f=15 Scripting Library forum], were lost with the death of the scripting forums, or sit idle in [[inventory|inventories]] that could be useful and should be more accessible.

Other scripters may be in the same situation. This wiki is a well-suited medium for a script library. Feel free to add your scripts to the script library by creating new pages for them and linking to those pages here.

Note that there are many more scripts in the LSL Library here, but you can't get to them if you don't know they exist, because they are subpages now, instead of an automatically updated category. Good luck searching.
</div>
</div>

<div id="box">

== Rules for posting: ==
<div style="padding: 0.5em">
#Your script must be tested and working. If it's not, stick it in your user-space until it is. This is a list of working, usable scripts.
#Add a link to your script's page here. Link back to this page from your script's page. Start your page with <nowiki>{{LSL Header}}</nowiki>.
#Do not add scripts that duplicate the same functionality as an existing script or built in {{LSLGC|Functions|function}}. If yours does, explain why.
#Do not list simple scripts here. Include those among the [[:Category:LSL Examples|LSL Examples]] instead.
</div></div>

<div id="box">
==LSL Script Library==

{| {{Prettytable}}
|-
|{{Hl2}}| '''Name'''
|{{Hl2}}| '''Creator'''
|{{Hl2}}| '''Description'''
|-
||[[3D Radar]]
||[[User:Jesse Barnett|Jesse Barnett]]
||Rezzes a ball for each avatar in range. Each ball tracks it's own AV and displays distance.
|-
||[[AntiDelay Node]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Uses llMessageLinked to stop those pesky delays.
|-
||[[AO Overriding Pose Ball]]
||[[User:Jesse Barnett|Jesse Barnett]]
||No more turning your AO off and on when you sit down
|-
||[[ARCFOUR Strong Encryption Implementation]]
||[[User:Nekow42 Zarf|Nekow42 Zarf]]
||An LSL implementation of ARCFOUR, the most popular stream cipher still in use. It is licensed under a Creative Commons Attribution 3.0 license.
|-
||[[Basic Encryption Modules]]
||[[User:Beverly Larkin|Beverly Larkin]]
||Basic encryption scripts, allows you to encrypt a float and shout it to another prim on a randomly chosen channel.
|-
||[[Binary Clock v1.1|Binary Clock]]
||[[User:Fox Diller|Fox Diller]]
||A Binary Clock.

|-
||[[Builders Buddy|Builder's Buddy Tool]]
||[[User:Newfie Pendragon|Newfie Pendragon]]
||Script to easily move/rotate large builds that exceed the linkable size limit (30 meters).
|-
||[[Camera Sync]]
||[[User:Meyermagic Salome|Meyermagic Salome]] and [[User:Nomad Padar|Nomad Padar]]
||A system to synchronize the cameras of two avatars.
|-
||[[Chatbot]]
||Anonymous
||Compile and run the LSL you type on a channel, faster than you can thru the 2007-08 SL GUI.
|-
||[[Chat Logger (GPL)]]
||[[User:Nobody Fugazi|Nobody Fugazi]]
||Chat logger which requests permission from participants before recording them.
|-
||[[Chat_Relay|Chat Relay]]
||[[User:grumble Loudon|grumble Loudon]]
||A Chat relay which can be routed using a path header and won't echo.
|-
||[[Code Racer]]
||Anonymous
||Race two versions of code forever, to see which runs faster.
|-
||[[Code Sizer]]
||Anonymous
||Count the bytes compiled from source code, to measure how to write small code.
|-
||[[Color conversion scripts|Color Conversion]]
||[[User:Sally LaSalle|Sally LaSalle]]
||Convert between Red Green Blue (RGB) and Hue Saturation Value (HSV).
|-
||[[Library Combined Library|Combined Library]]
||[[User:Strife Onizuka|Strife Onizuka]]
||Library of mostly encoding and decoding functions, some more useful then others.
* String functions: Replace / Trim right / Trim left / Trim both
* Unicode conversion: UTF8 to Unicode / Unicode to UTF8
* List functions: Replace / Compare
|-
||[[Computer:jaycoonlanguage]]
||[[User:jayco121 Bing|jayco121 Bing]]
|| A language written in LSL that is meant for my computer (available at the shop).
|-
||[[Library_Chat_Relay|Conversation Relay]]
||[[User:Jippen Faddoul|Jippen Faddoul]]
||Chat relay which requests permission from participants before relaying their messages. Also includes their attachments. (ToS compliant).
|-
||[[Curtain script]]
||[[User:Zilla Larsson|Zilla Larsson]]
||A simple script to retract/stretch curtains, blinds, bedcovers and more
|-
||[[Dataserver API]]
||[[User:Revolution Perenti|Revolution Perenti]]
||Dataserver Framework for Notecards.
|-
||[[Date Library]]
||[[User:Corto Maltese|Corto Maltese]]
|| Date library, based on number of day since march 3rd 1600, can be used to calculate weekday, date differences, and date offset, and date formating.
|-
||[[Day of the Week]]
||[[User:DoteDote Edison|DoteDote Edison]]
||Function to get day of the week from [[llGetUnixTime]].
|-
||[[Deed Tools]]
||[[User:Falados Kapuskas|Falados Kapuskas]]
||Tools that allow the creator to modify Group-Owned (Deeded) Objects via chat.
|-
||[[Describe Chatter]]
||Anonymous
||Chat to see yourself as others do.
|-
||[[Dialog Control]]
||[[User:Nargus Asturias|Nargus Asturias]]
|| A (not-so) simple dialog control script. Call dialog and receive selected value via link_message(), with built-in timer and link_message() notification on time out. Supports multi-pages dialog and numeric property dialog. Button text and dialog's returned value can differ.
|-
||[[Dialog Menus Control]]
||[[User:Nargus Asturias|Nargus Asturias]]
|| An extension to Nargus Dialog Control. This menus control allow multi-level menus through SL dialog system. It can also recall last used menus. Menus are saved and pre-formatted for faster access. Though it is not the fastest, nor most memory efficient, but it should make it easier to use.
|-
||[[Dialog NumberPad|Dialog Number Pad]]
||[[User:DoteDote Edison|DoteDote Edison]]
||Use a dialog to accept positive integer input from users.
|-
||[[Efficiency Tester]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Tests the speed of a function.
|-
||[[Email-to-IM|Email2IM]]
||[[User:DoteDote Edison|DoteDote Edison]]
||Send IMs to SL friends via email (translate emails from friends into IMs).
|-
||[[Fix Small Prims|Fix_Small_Prims]]
||[[User:Emma Nowhere|Emma Nowhere]]
||Finds and adjusts the smallest prims in a linkset so that it can be scaled down further.
|-
||[[Float2Hex]]
||[[User:Strife Onizuka|Strife Onizuka]]
||Very useful for transporting [[float|floats]].
|-
||[[Follower (script)|Follower]]
||Unknown, uploaded by [[User:Slik Swindlehurst|Slik Swindlehurst]]
||Makes an object follow the nearest person. Do not use for [[grief|griefing]].
|-
||[[Geometric|Geometric Library]]
||[[User:Nexii_Malthus|Nexii Malthus]]
||A substantial amount of various geometric functions for intersection and other purposes of 3D maths.
|-
||[[GetTimestampOffset]]
||[[User:Siann_Beck|Siann Beck]]
||Returns llGetTimestamp() with an hour offset.
|-
||[[Give InvItem every n hours]]
||[[User:Criz Collins|Criz Collins]]
||Will give an inventory item on touch only every n hours, even if somebody touches the object more than once.
|-
||[[Google Charts]]
||[[User:Dedric Mauriac|Dedric Mauriac]]
||Create links to display raw data as a chart image.
|-
||[[Group Privacy]]
||[[User:Chance Unknown|Chance Unknown]]
||Security device to insure members of a group can have a private area. Deactivates when nobody present.
|-
||[[Hello Avatar]]
||Linden Lab
||SL's default script.
|-
||[[High Altitude Rezzer|High Altitude Rezzer]]
||[[User:Jesse Barnett|Jesse Barnett]]
||Vehicle that goes straight up and then rezzes objects up to 4,096 meters.
|-
||[[Holodeck]]
||[[User:Revolution Perenti|Revolution Perenti]]
||Home Rezzing System (Open Source).
|-
||[[Intra-Region Update Server]]
||[[User:Emma_Nowhere|Emma Nowhere]]
||Centrally update objects such as Freeview screens or teleport pads within a region that are configured by notecards or contain modifiable objects or media assets.
|-
||[[Interpolation|Interpolation Library]]
||[[User:Nexii_Malthus|Nexii Malthus]]
||A small set of interpolation functions.
|-
||[[Inventory Menu]]
||[[User:Revolution Perenti|Revolution Perenti]]
||Inventory Based Menu System.
|-
||[[iTunes RPC Email|iTunes RPC]]
||[[User:Fox Diller|Fox Diller]]
||iTunes RPC via LSL [[llEmail]] and [[llRemoteDataReply]].
|-
||[[Key Pad Door|Keypad Door]]
||[[User:Tdub Dowler|Tdub Dowler]]
|| Door and keypad with changeable code. Follow instructions carefully!
|-
||[[LSL_languageAPI]]
||[[User:Gypsy paz|Gypsy Paz]]
||Multi-lingual API from notecard based language files
|-
||[[Last Sound System]]
||[[User:Babbage Linden|Babbage Linden]]
||An LSL Last.fm client.
|-
||[[Mandelbrot Explorer]]
||[[User:Babbage Linden|Babbage Linden]]
||An interactive fractal explorer.
|-
||[[Merge Sort]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Implements a Merge Sort in LSL, however this code is 300(ish) times slower than [[llListSort]]. Don't use this in a script!
|-
||[[Minesweeper]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||A simple minesweeper game.
|-
||[[Multirezzer|Multirezzer (on collision)]]
||[[User:Beet Streeter|Beet Streeter]]
||Spawns up to 10 objects when the object containing the script collides with a user.
|-
||[[Object to Data v1.2|Object to Data]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Turns an object into text (and back). Allows people to transfer objects through notecards.
|-
||[[ParseString2List]]
||[[User:Strife Onizuka|Strife Onizuka]]
||Same as [[llParseString2List]] and [[llParseStringKeepNulls]], but not limited to 8 spacers or separators. Thus substitute a call to the [[llParseString2List]] and [[llParseStringKeepNulls]] functions by a call to [[Parse_String_To_List|ParseString2List]] whenever you have more than 8 separators or more than 8 spacers.
|-
||[[Pathfinder]]
||[[User:Babbage Linden|Babbage Linden]]
||A potential field based pathfinding library.
|-
||[[Phantom Maker]]
||[[User:Xaviar_Czervik|Xaviar Czervik]]
||An object that turns avatars into phantoms, without having to remain sitting.
|-
||[[Prefix Calculator]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
|| A calculator that evaluates expressions in prefix notation.
<code>+ 3 4 = 5. * + 1 2 + 3 4 = 14.</code>
|-
||[[Pseudo-random Number Generator]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Generates a Pseudo-random number between -0x7FFFFFFF and 0x7FFFFFFF
|-
||[[Random AV Profile Projector]]
||[[User:Debbie Trilling|Debbie Trilling]]
||Randomly selects an AV from a crowd & then projects their profile picture as a 'holographic' image
|-
||[[Say Region Frames Per Second|Region Frames Per Second]]
||[[User:Heymeriou Mystakidou|Heymariou Mystakidou]]
|| Says the region name and frames per second out loud on command.
|-
||[[Script Override Functions]]
||[[User:Revolution Perenti|Revolution Perenti]]
||bypass default strings, integer etc in chat channel.
|-
||[[Self Upgrading Script Enhanced]]
||[[User:Cron Stardust|Cron Stardust]]
||Keeps only latest version of the script on prim (even with multiple adds of the same script!)
|-
||[[SHA1|SHA1 Hash]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Preforms a SHA1 Hash on an input text. Similar to MD5 only (slightly) more secure.
|-
||[[SLateIt]]
||[[User:Babbage Linden|Babbage Linden]]
||An augmented virtual reality HUD.
|-
||[[SLetanque]]
||[[User:Babbage Linden|Babbage Linden]]
||An LSL petanque game.
|-
||[[SL Mail V1.2]]
||[[User:Flennan Roffo|Flennan Roffo]]
||Second Life mail client V1.2 (released sept'07). Send and receive mail from within Second Life from and to any address. With Address Book function and many chat commands. V1.3 is upcoming soon!
|-
||[[SL_NTPoHTTP_v1.1_client|SL NTPoHTTP client]]
|[[User:SignpostMarv Martin|SignpostMarv Martin]]
||Second Life Needs Time Parsing over Hyper Text Transfer Protocol
Emulates the function of [[llGetWallclock]] for any timezone by using SLOpenID's SLNTPoHTTP service. Also supports ISO 8601 and RFC 2822 timestamps. Script is dependent upon an external service operated by the author!
|-
||[[Spiral Staircase Generator]]
|[[User:Meyermagic Salome|Meyermagic Salome]]
||Generates nice looking spiral staircases without much hassle.
|-
||[[String Compare]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Compares two strings and reliably returns either 1, -1, or 0 if they are the same.
|-
||[[Teleport HUD]]
||[[User:Jesse Barnett|Jesse Barnett]]
||WORKS TO 4096 METERS!! Very user friendly teleport HUD. Add destinations by touching "Add" & naming destination in chat. Automatically gets sim name and coordinates. Will only display the destinations in the sim you are currently in. Demonstrates more advanced list manipulation and stride functions.
|-
||[[Texture Menu Management|Texture Management]]
||[[User:Revolution Perenti|Revolution Perenti]]
||Dialog Menu based Texture Selection.
|-
||[[Tic Tac Toe]]
||[[User:CG Linden|CG Linden]]
||Step by step demo on how to implement a larger scripting project
|-
||[[TightList]]
||[[User:Strife Onizuka|Revolution Perenti]]
||Tight List is a family of functions for encoding lists as strings and then decoding them back into lists.

There are two flavors: TightList and TightListType. TightListType preserves types and uses a 6 char header, while TightList uses a 1 char header that doesn't preserve type.
|-
||[[Timer Module]]
||[[User:Isabelle Aquitaine|Isabelle Aquitaine]]
||Manage multiple timers via linked messages.
|-
||[[Unix2DateTime]]
|[[User:Flennan Roffo|Flennan Roffo]]
||Conversion from Unix time (llGetUnixTime()) to date and time string and vice versa.
|-
||[[Under Age Boot]]
|[[User:Chance Unknown|Chance Unknown]]
||Security device example to teleport home accounts below a minimum age limit; can be useful in combating free griefer accounts.
|-
||[[Visitor Logger (Web/Basic) ]]
|[[User:Buddy Sprocket|Buddy Sprocket]]
||A very basic visitor logger - log visitors in SL to a text file on your web-site.
|-
||[[Vote Simple]]
|[[User:JB_Kraft|JB Kraft]]
||Simple vote collector. One avi, one vote.
|-
||[[WarpPos]]
|[[User:Keknehv Psaltery|Keknehv Psaltery]]
||Non-physical movement without the 10m limit.
|-
||[[XTEA Strong Encryption Implementation]]
||[[User:Morse Dillon|Morse Dillon]]
||An LSL implementation of XTEA (eXtended Tiny Encryption Algorithm). This is the first known public release of a 'real' strong encryption implementation in LSL and is released under the GNU General Public License (GPL).
|-
||[[XyText 1.5|XyText]]
||[[User:Xylor Baysklef|Xylor Baysklef]]
|| Display text (up to 10 characters) on a prim. Use as many prims as desired.
|-
||[[XyyyyzText|XyyyyzText]]
||[[User:Criz Collins|Criz Collins]]
|| Display text (up to 10 characters) on a prim. Displays different text for each line instead of one single text, that will be broken into the next lines. Watch here for what that means: http://screencast.com/t/1wMLujLcEO
|-
||[[XyzzyText|XyzzyText]]
||[[User:Thraxis Epsilon|Thraxis Epsilon]] and [[User:Gigs Taggart|Gigs Taggart]]
|| Display text (up to 10 characters) on a prim. Way more efficient than XyText.
|-
||[[Zero Lag Poseball]]
||[[User:Jippen Faddoul|Jippen Faddoul]]
||A simple poseball with no lag
|}

</div>
<div id="box">

==Support Script Library==
These are scripts in other languages, intended to be run on other systems that support scripts written in LSL

{| {{Prettytable}}
|-
|{{Hl2}}| '''Name'''
|{{Hl2}}| '''Creator'''
|{{Hl2}}| '''Description'''
|-
||[[HTTP Post request to a PHP server]]
||[[User:Corto Maltese|Corto Maltese]]
|| This small library allows you to make simple POST requests to your website. The libraries allow you to get your request through the variable $_POST on the server. It also include a basic security mechanism aimed to stop hacking. Comprises of LSL client script and PHP server script.
|-
|| Silo
|| [[User:Zero_Linden|Zero Linden]]
|| General purpose data store in PHP. Use this to persist arbitrary data from LSL via [[llHTTPRequest]]. See:
* [http://www.notabene-sl.com/misc/silo-README.txt README] file
* [http://www.notabene-sl.com/misc/silo.tgz silo.tgz] tarball
* forum post [http://forums.secondlife.com/showthread.php?t=119570 Announcement].
|-
|| [[User:SignpostMarv Martin/PHP/llXorBase64StringsCorrect|llXorBase64StringsCorrect]]
|| [[User:SignpostMarv Martin|SignpostMarv Martin]]
|| An implementation of [[llXorBase64StringsCorrect]] in PHP- should be useful if you're using llXorBase64StringsCorrect to do cryptography work in LSL2 and posting it out to the web via [[llHTTPRequest]].
|-
|| [[User:SignpostMarv Martin/PHP/lsl fu.php|lsl_fu.php]]
|| [[User:SignpostMarv Martin|SignpostMarv Martin]]
|| A basic OOP'd PHP Class containing VeloxSeverine's $_POST fixer and Marv's own eccentric ideas for "fixing" things.
|}
</div>

<div id="box">

== See Also ==
<div style="padding: 0.5em">
'''Articles'''
*[[:Category:LSL Examples| Examples]]

</div></div>

LSL Library/fr

2008-07-02T21:21:13Z

Corto Maltese: /* Bibliothèque de scripts compatibles avec le LSL */

{{LSL Header/fr}}{{RightToc}}
== Bibliothèque de scripts ==

<div id="box">
<div style="padding: 0.5em 0.5em 1.5em">
Cette page permet de consulter des exemples complexes d‘application du LSL

Consultez la page des [[:Category:LSL Examples/fr|exemples]] si vous recherchez des exemples simples d’application du LSL.

Beaucoup de [[script/fr|scripts]] ont été perdus au fil du temps que ce soit dans un forum [http://forums.secondlife.com/forumdisplay.php?f=15 Scripting Library forum] ou au fond d’un [[inventory/fr|inventaire]] alors qu’ils auraient pu être beaucoup plus utiles s’ils avaient été diffusés plus largement.

Le wiki est un outil adapté à la création d’une bibliothèque de scripts. N’hésitez pas à créer des pages pour ajouter vos propres scripts et à insérer votre lien ici.

Il existe bien plus d’exemples de scripts que ceux référencés ici, mais ils sont moins facilement accessibles car non référencés.

Bonne chance dans vos recherches !

</div>
</div>

<div id="box">

== Règles à respecter pour poster: ==
<div style="padding: 0.5em">
#Votre script doit être testé (et fonctionner) avant d’être posté. Si ce n’est pas le cas, placez le dans votre espace personnel jusqu’a ce qu’il soit prêt. Cette liste ne propose que des scripts opérationnels.
#Ajoutez un lien ci-dessous et renvoyez un lien de cette page depuis votre page. Débutez votre page avec la balise <nowiki>{{LSL Header}}</nowiki>.
#N’ajoutez pas un script qui dupliquerait la fonctionnalité d’un script existant dans cette bibliothèque ou dans la fiche d’une {{LSLGC|Functions|fonction}}. Si vous souhaitez le faire malgré tout, expliquez pourquoi.
#N’ajoutez pas de script « simple » dans cette page, mais utilisez plutôt la catégorie [[:Category:LSL Examples/fr|Exemples en LSL]].
</div></div>

<div id="box">
==Bibliothèque de Scripts ==

{| {{Prettytable/fr}}
|-
|{{Hl2}}| '''Nom'''
|{{Hl2}}| '''Créateur'''
|{{Hl2}}| '''Description'''
|-
||[[3D Radar]]
||[[User:Jesse Barnett|Jesse Barnett]]
||Rezz une balle pour chaque avatar à proximité. Chaque balle espionnera son avatar et affichera sa distance.
|-
||[[AntiDelay Node]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Utilisation de llMessageLinked pour réduire l’impact du délai appliqué à certaines fonctions.
|-
||[[AO Overriding Pose Ball]]
||[[User:Jesse Barnett|Jesse Barnett]]
||Plus besoin d’éteindre votre AO pour vous asseoir.
|-
||[[Basic Encryption Modules]]
||[[User:Beverly Larkin|Beverly Larkin]]
||Script basique de cryptage d’un float capable d’envoyer la donnée sur un canal choisi aléatoirement
|-
||[[Binary Clock v1.1|Binary Clock]]
||[[User:Fox Diller|Fox Diller]]
||Une horloge binaire.
|-
||[[Builders Buddy|Builder's Buddy Tool]]
||[[User:Newfie Pendragon|Newfie Pendragon]]
||Script pour facilement déplacer/tourner de grands bâtiments dépassant la limite de taille des objets liables (30 mètres)
|-
||[[Camera Sync]]
||[[User:Meyermagic Salome|Meyermagic Salome]] and [[User:Nomad Padar|Nomad Padar]]
||Un script pour synchroniser les caméras de deux avatars.
|-
||[[Chatbot]]
||Anonymous
||Compile et lance le LSL tapé dans le chat (plus rapide que l’interface du 2007-08).
|-
||[[Chat Logger (GPL)]]
||[[User:Nobody Fugazi|Nobody Fugazi]]
||Un enregistreur de chat qui demande la permission des participants avant de les enregistrer.
|-
||[[Chat_Relay|Chat Relay]]
||[[User:grumble Loudon|grumble Loudon]]
||Un système de relais de chat avec en-tête
|-
||[[Code Racer]]
||Anonymous
||Fait tourner éternellement deux versions d’un code afin de déterminer laquelle est la plus rapide.
|-
||[[Code Sizer]]
||Anonymous
||Compte le nombre de bytes compilés à partir d’un code source afin de mesurer l e codage optimal.
|-
||[[Color conversion scripts|Color Conversion]]
||[[User:Sally LaSalle|Sally LaSalle]]
||Effectue la conversion entre les codes « rouge, vert, bleu » (RVB /RGB) et le code « Hue Saturation Value » (HSV).
|-
||[[Library Combined Library|Combined Library]]
||[[User:Strife Onizuka|Strife Onizuka]]
||Un bibliothèque de fonctions de codage et de décodage:
* Analyse de string : Remplacement / suppression droite / suppression gauche / suppression des deux cotés
* Conversion Unicode: UTF8 => Unicode / Unicode to UTF8
* Analyse de lists : Remplacement / Comparaison
|-
||[[Computer:jaycoonlanguage]]
||[[User:jayco121 Bing|jayco121 Bing]]
||Un langage écrit an LSL adapté à mon ordinateur (disponible au magasin).
|-
||[[Library_Chat_Relay|Conversation Relay]]
||[[User:Jippen Faddoul|Jippen Faddoul]]
||Un système de relais de chat qui demande le droit au participant de transmettre leur message et leur pièce jointe (conforme à la ToS).
|-
||[[Dataserver API]]
||[[User:Revolution Perenti|Revolution Perenti]]
||Outil de gestion de notes pour configurer un script.
|-
||[[Date Library]]
||[[User:Corto Maltese|Corto Maltese]]
||Fonction de gestion des dates basée sur le nombre de jours depuis le 3 mars 1600. Ce script peut être utilisé pour calculer le numéro de semaine, les différences entre dates, le décalage et le format des dates.
|-
||[[Day of the Week]]
||[[User:DoteDote Edison|DoteDote Edison]]
||Fonction permettant d’obtenir le jour de la semaine à partir de [[llGetUnixTime/fr|llGetUnixTime]].
|-
||[[Describe Chatter]]
||Anonymous
||Chat pour se voir comme les autres nous voient
|-
||[[Dialog Control]]
||[[User:Nargus Asturias|Nargus Asturias]]
|| Un script de gestion de boîtes de dialogues. Il permet d’ouvrir des boîtes de dialogue et d’en transmettre les valeurs au travers de link_message() avec timer intégré. Ce script est capable de gérer les boîtes de dialogue réparties en plusieurs pages, il est également capable d’assurer une codification entre la valeur visible dans la boîte et la donnée renvoyée par le script.
|-
||[[Dialog Menus Control]]
||[[User:Nargus Asturias|Nargus Asturias]]
|| Une extension du script de gestion des boîtes de dialogue de Nargus. Il ajoute une gestion de menus et de sous menus, ainsi que des options de navigation inter menus. Les menus sont enregistrés et pré formatés afin d’y avoir accès plus rapidement (ce n’est pas la méthode la plus rapide, mais elle devrait rendre le script plus efficace)
|-
||[[Dialog NumberPad|Dialog Number Pad]]
||[[User:DoteDote Edison|DoteDote Edison]]
||Utilise une boîte de dialogue pour la saisie d’integer par un utilisateur.
|-
||[[Efficiency Tester]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Teste la vitesse d’exécution d’une fonction.
|-
||[[Email-to-IM|Email2IM]]
||[[User:DoteDote Edison|DoteDote Edison]]
||Envoie des IM à des amis SL via e-mail. (Transforme des emails en IM)
|-
||[[Fix Small Prims|Fix_Small_Prims]]
||[[User:Emma Nowhere|Emma Nowhere]]
||Trouve est ajuste la plus petite prim d’un objet de façon à ce qu’il puisse être réduit davantage.
|-
||[[Float2Hex]]
||[[User:Strife Onizuka|Strife Onizuka]]
||Très utile pour transférer des [[float/fr|floats]].
|-
||[[Follower (script)|Follower]]
||Unknown, uploaded by [[User:Slik Swindlehurst|Slik Swindlehurst]]
||Fait en sorte qu’un objet suive la personne la plus proche. A ne pas utiliser pour gêner/embêter.
|-
||[[Google Charts]]
||[[User:Dedric Mauriac|Dedric Mauriac]]
||Crée des liens pour afficher des données brutes dans un diagramme.
|-
||[[Group Privacy]]
||[[User:Chance Unknown|Chance Unknown]]
||Système de sécurité destiné à garantir aux membres d’un groupe une zone privée. Désactivé quand personne n’est présent.
|-
||[[Hello Avatar]]
||Linden Lab
||Le script par défaut de Linden Lab.
|-
||[[High Altitude Rezzer|High Altitude Rezzer]]
||[[User:Jesse Barnett|Jesse Barnett]]
||Véhicule s’élevant à la verticale et rezzant des objets jusqu'à 4,096 mètres.
|-
||[[Holodeck]]
||[[User:Revolution Perenti|Revolution Perenti]]
|Application du concept de l’Holodeck (cf. Open Source).
|-
||[[Intra-Region Update Server]]
||[[User:Emma_Nowhere|Emma Nowhere]]
||Mise à jour centralisée d’objets configurés par notes (ou contenant des objets modifiables et présents dans la même région.)
|-
||[[Inventory Menu]]
||[[User:Revolution Perenti|Revolution Perenti]]
||Gestion de l’inventaire par menus.
|-
||[[iTunes RPC Email|iTunes RPC]]
||[[User:Fox Diller|Fox Diller]]
||Utilisation de iTunes RPC avec les [[llEmail/fr|llEmail]] et la fonction [[llRemoteDataReply/fr|llRemoteDataReply]].
|-
||[[Key Pad Door|Keypad Door]]
||[[User:Tdub Dowler|Tdub Dowler]]
||Porte codée de couleur paramétrable. Suivez les consignes attentivement.
|-
||[[Last Sound System]]
||[[User:Babbage Linden|Babbage Linden]]
||Un client radio FM pour SL.
|-
||[[Merge Sort]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Implémentation d’un tri par fusion dans LSL, Ce code est 300x plus lent que [[llListSort/fr|llListSort]]. Ne l’utilisez pas dans un script!
|-
||[[Minesweeper]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Implémentation d’un démineur dans SL.
|-
||[[Multirezzer|Multirezzer (on collision)]]
||[[User:Beet Streeter|Beet Streeter]]
||Rez jusqu'à 10 objets lorsque l’objet entre en collision avec l’utilisateur.
|-
||[[Object to Data v1.1|Object to Data]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Transforme un objet en texte, permet le transfert d’objets sous forme de notes.
|-
||[[ParseString2List]]
||[[User:Strife Onizuka|Strife Onizuka]]
||Identique à [[llParseString2List/fr|llParseString2List]] et [[llParseStringKeepNulls/fr|llParseStringKeepNulls]], mais n’est pas limité à 8 séparateurs ou espaces Il peut se substituer à [[llParseString2List/fr|llParseString2List]] et [[llParseStringKeepNulls/fr|llParseStringKeepNulls]] en appellant [[Parse_String_To_List|ParseString2List]].
|-
||[[Pathfinder]]
||[[User:Babbage Linden|Babbage Linden]]
||Un script qui propose des fonctions de calcul de chemins.
|-
||[[Prefix Calculator]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
|| Un calculateur qui travaille en notation « préfixée ».
<code>+ 3 4 = 5. * + 1 2 + 3 4 = 14.</code>
|-
||[[Pseudo-random Number Generator]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Génère un nombre pseudo aléatoire entre -0x7FFFFFFF et 0x7FFFFFFF
|-
||[[Random AV Profile Projector]]
||[[User:Debbie Trilling|Debbie Trilling]]
||Sélectionne de manière aléatoire un avatar dans une foule et projette l’image de son profil sur une image holographique.
|-
||[[Say Region Frames Per Second|Region Frames Per Second]]
||[[User:Heymeriou Mystakidou|Heymariou Mystakidou]]
||Renvoie le nom d’une région ainsi que le nombre de frames/secondes.
|-
||[[Script Override Functions]]
||[[User:Revolution Perenti|Revolution Perenti]]
||Remplace les canaux par défaut de SL.
|-
||[[Self Upgrading Script Enhanced]]
||[[User:Cron Stardust|Cron Stardust]]
||Ne garde que la dernière version du script dans une prim. (Fonctionne également avec des doublons du script !)
|-
||[[SHA1|SHA1 Hash]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Applique sur un texte un cryptage de type SHA1. Similaire au MD5 mais un (petit) peu plus sécurisé.
|-
||[[SLateIt]]
||[[User:Babbage Linden|Babbage Linden]]
||Un Hud optimisé pour la réalité virtuelle.
|-
||[[SLetanque]]
||[[User:Babbage Linden|Babbage Linden]]
||Un jeu de pétanque en LSL
|-
||[[SL Mail V1.2]]
||[[User:Flennan Roffo|Flennan Roffo]]
||Un client mail en LSL V1.2 (sept'07). Envoie et reçoit des mails depuis Second Life depuis et vers n’importe quelle adresse. Avec un carnet d’adresse et plusieurs fonctions depuis le chat. V1.3 bientôt disponible !
|-
||[[SL_NTPoHTTP_v1.1_client|SL NTPoHTTP client]]
|[[User:SignpostMarv Martin|SignpostMarv Martin]]
||Second Life Needs Time Parsing over Hyper Text Transfer Protocol
Simule la fonction [[llGetWallclock]] pour n'importe quel fuseau horaire en se basant sur le service SLNTPoHTTP de SLOpenID. Supporte aussi les "timestamps" ISO 8601 et RFC 2822. Le script utilise d'un service externe mis en place par son auteur!
|-
||[[String Compare]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Compare deux strings et renvoie 1, -1, or 0 en fonction du résultat.
|-
||[[Teleport HUD]]
||[[User:Jesse Barnett|Jesse Barnett]]
||Un Hud très utile de gestion de la téléportation. Ajoute une destination en cliquant sur « Add » et en nommant la destination dans le chat. Récupère automatiquement le nom de la sim et les coordonnées.
N’affichera la destination que dans la sim où vous êtes. Illustre une manipulation avancée des listes.
|-
||[[Texture Menu Management|Texture Management]]
||[[User:Revolution Perenti|Revolution Perenti]]
||Boîte de dialogue pour gérer des textures.
|-
||[[Tic Tac Toe]]
||[[User:CG Linden|CG Linden]]
||Une démo pas à pas de comment développer un projet de script plus important.
|-
||[[TightList]]
||[[User:Strife Onizuka|Revolution Perenti]]
||Ce script permet d’encoder et de décoder des lists en string.
Il y a deux options : TightList et TightListType. TightListType conserve le type et utilise 6 caractères en en-tête, TightList utilise un seul caractère en en-tête mais ne conserve pas le type.
|-
||[[Timer Module]]
||[[User:Isabelle Aquitaine|Isabelle Aquitaine]]
||Permet de gérer plusieurs timers au travers de messages liés.
|-
||[[Unix2DateTime]]
|[[User:Flennan Roffo|Flennan Roffo]]
||Conversion du temps Unix (llGetUnixTime()) en string ( date/heure) et vice versa.
|-
||[[Under Age Boot]]
|[[User:Chance Unknown|Chance Unknown]]
||Système de sécurité qui permet de téléporter des avatars jusqu'à leur maison s’ils sont en dessous d’un âge limite (utile pour lutter contre les abus)
|-
||[[WarpPos]]
|[[User:Keknehv Psaltery|Keknehv Psaltery]]
||Un script qui permet de dépasser la limite théorique de 10m des déplacements non physiques (téléportation)
|-
||[[XTEA Strong Encryption Implementation]]
||[[User:Morse Dillon|Morse Dillon]]
||Implémentation en LSL de XTEA (eXtended Tiny Encryption Algorithm). Il s’agit de la première mise à disposition du public d’un algorithme de cryptage assurant un haut niveau de sécurité. Ce script est proposé sous GNU General Public License (GPL).
|-
||[[XyText 1.5|XyText]]
||[[User:Xylor Baysklef|Xylor Baysklef]]
||Affiche un texte (jusqu’à 10 caractères) sur une prim.
|-
||[[XyzzyText|XyzzyText]]
||[[User:Thraxis Epsilon|Thraxis Epsilon]] and [[User:Gigs Taggart|Gigs Taggart]]
|| Affiche un texte (jusqu’à 10 caractères). Plus efficace que XyText.
|-
||[[Zero Lag Poseball]]
||[[User:Jippen Faddoul|Jippen Faddoul]]
||Une poseball sans lag.
|}

</div>
<div id="box">

==Bibliothèque de scripts compatibles avec le LSL ==
Vous trouverez ici des scripts écrits dans d’autres langages et à lancer sur d’autres systèmes mais qui supportent des scripts en LSL.
{| {{Prettytable/fr}}
|-
|{{Hl2}}| '''Nom'''
|{{Hl2}}| '''Créateur'''
|{{Hl2}}| '''Description'''
|-
||[[HTTP Post request to a PHP server]]
||[[User:Corto Maltese|Corto Maltese]]
||Cette bibliothèque permet de faire des requêtes vers votre site web en utilisant les variable php $_POST (un simple controle est egalement fait pour eviter les requetes illicites). Client : script LSL // Serveur : script PHP.
|-
|| Silo
|| [[User:Zero_Linden|Zero Linden]]
|| A pour principal objectif de stocker des données en PHP. Transfert réalisé au travers de [[llHTTPRequest/fr|llHTTPRequest]]. Voyez également :
* [http://www.notabene-sl.com/misc/silo-README.txt README] file
* [http://www.notabene-sl.com/misc/silo.tgz silo.tgz] tarball
* forum [http://forums.secondlife.com/showthread.php?t=119570 Announcement].
|-
|| [[User:SignpostMarv Martin/PHP/llXorBase64StringsCorrect|llXorBase64StringsCorrect]]
|| [[User:SignpostMarv Martin|SignpostMarv Martin]]
||Une implémentation de [[llXorBase64StringsCorrect/fr|llXorBase64StringsCorrect]] en PHP – Peut être utile en cas d’utilisation de llXorBase64StringsCorrect pour crypter vos données en LSL2 et pour les poster sur le web via [[llHTTPRequest]].
|-
|| [[User:SignpostMarv Martin/PHP/lsl fu.php|lsl_fu.php]]
|| [[User:SignpostMarv Martin|SignpostMarv Martin]]
|| A basic OOP'd PHP Class containing VeloxSeverine's $_POST fixer and Marv's own eccentric ideas for "fixing" things.
|}
</div>

<div id="box">

== A voir également==
<div style="padding: 0.5em">
'''Articles'''
*[[:Category:LSL Examples/fr|Exemples]]

</div></div>

Talk:Secure HTTP Post

2008-07-02T21:17:17Z

Corto Maltese: Talk:Secure HTTP Post moved to Talk:HTTP Post request to a PHP server: Some people wrote a much better encryption page. this library is still valid to implement a simple PHP POST though

#REDIRECT [[Talk:HTTP Post request to a PHP server]]

Talk:HTTP Post request to a PHP server

2008-07-02T21:17:17Z

{{Talk}}
Is it possible to provide known input values and intercept the hash as it is passed to the web server thereby determining the secret key? Is providing the hash as part of the URL the best strategy?
[[User:Hackshaven Harford]]

Transmitting the hash is perfectly safe however the method for calculating the hash will lead to the eventual brute forcing of SECRET_NUMBER. Since this script is open source and only uses a 32bit secret, an attack only needs to intercept one message. At the point in the PHP script where the hash is checked the attacker would systematically try every single MD5 nonce, until one of them worked. A year or so ago I was doing some consulting for a guy who was developing a similar system. Using an open source MD5 implementation written in C that I tweaked, I was able to try every nonce in less then 24 hours on a 600MHz Pentium 3. Imagine how fast it would run if it were multi-threaded on a modern multi-core system, now imagine a small cluster of modern computers. If you don't mind it taking several months you can also do this in LSL. If you want to make sure you don't get communication injections '''don't use this script'''. -- [[User:Strife Onizuka|Strife Onizuka]] 09:17, 25 April 2007 (PDT)

Strife makes a great point, 32bits is not enough. Strife, I'd like to know what you think is the correct way given the tools we've got. In the meantime, I think you can afford a significant amount of extra protection by using a longer passphrase in place of the 32bit nonce.
string XREQUEST_PASSPHRASE = "nVBh)cCBy7l6ieihewF3Y__QZZ";
string hash=llMD5String(body + XREQUEST_PASSPHRASE,0);
If you make some guesstimates about how long (z) it takes to brute force (x) bits on a cluster of cost (y), you can then measure your paranoia precisely and create a passphrase to suit.
Any objections to this implementation? It's still not great, but what else have we got?
--[[User:Nite Zelmanov|Nite Zelmanov]] 20:37, 27 September 2007 (PDT)

For general paranoia purposes you should use the nonce and a prefixed string; waste not, want not. Regardless how you affix the secret, it is my belief that the secret shouldn't be a string or an integer but an algorithm. A black box that can be fed a secret & the day/time and spit out a reproducible response. You then use the result of that alg as your secret for your hash. When someone cracks the secret used to hash a single message it won't be the same secret used on other messages, or at least not many; hopefully by the time they have cracked the temporal secret it will have expired. An attacker would have to brute force multiple temporal secrets to even start trying to figure out how the black box worked. By combining time with your secret in a non-obvious way you can protect your secret from direct brute forcing. There are other ways... If you know every message is going to be received, you can increment your secret (as a result of passing it through the black box). You want to prefix your (temporary) secret and not postfix it to the data you are hashing. MD5 uses 64 byte blocks, you build the final hash one block at a time. If the secret is postfixed the cracker can cache the temporary value up to the last complete block; in effect they only have to brute force the hash on one block instead of the complete message. By prefixing the secret the caching optimization can't be used. -- [[User:Strife Onizuka|Strife Onizuka]] 22:03, 27 September 2007 (PDT)

A simple black box:
<pre>
//I prefer an MD5 because it shakes up the bits.
string BlackBox(string secret, integer nonce)//changes every minute
{
return llMD5String(llGetSubString(llGetTimestamp(),0,15) + secret, nonce);
}

string Hash(string data, string secret, integer nonce)
{
return llMD5String(llMD5String(llGetSubString(llGetTimestamp(),0,15) + secret, nonce ^ 0x7e9b23f1) + data, nonce);
}

string Hash2(string data, string secret, integer nonce, integer offset)
{//for the main hash, the nonce is a moving target.
//In essence this function allows for the use of 3 secrets: secret, nonce and offset.
return llMD5String(data, (integer)("0x" + llGetSubString(llMD5String(llGetSubString(llGetTimestamp(),0,15) + secret, nonce),offset,(offset + 7)%32)));
}
</pre>
[[User:Strife Onizuka|Strife Onizuka]]

== dual Key PGP? ==

Could this be written to use dual key (public/private) encryption? Or would that require a full implementation of PGP for LSL?

For example: an lsl wrapper could be written/added for GnuPG, assuming it is installed on Linden's servers. Then the object could be given the public key of the web resource it is accessing, and only the web server (also using GnuPG) could decrypt using its private key.

An encryted return could be achieved by having every member UID have a public and private key (public key published as part of a Linden web service, private key only known to the server -- not even the user would know it), and the web server would encrypt the message using the user's public key, and the object would access another wrapper function using the user's UID, the function accessing the user's private key and returning the decrypted message.

Any thoughts?
-- [[User:Caelgarr Oconnell|Caelgarr Oconnell]]

== PGP Brute force ==

This library did offer 2 things:
(1) HTTP Post
(2) MD5 CRC

1 - For the HTTP Post to work, you have to format the posted data in a certain way.
With this technique you can send a List of variable to a server.
And the server can collect the data using its normal Post variables.
The result s technique

if (i>0) body+="&";
body+=llEscapeURL(varname)+"="+llEscapeURL(varvalue);

2 - The MD5 Crc, controls that the request is correct.
This makes a checksum of the entire request and make sure that it was received properly.
As you said, this not the most secure algorithm.
The checksum number is 32 bits.
So if you work brute force on it (assuming you know the host name, the URL, and the variables names),
every request is stopping the script for 2 seconds.
It would take 70 years on average to find the right checksum.
You could obviously run simultaneous requests to an extent but this will still take a substantial amount of time to crack.

However the security is not really all in the checksum.
As far as I know the request is not done on the client machine.
The web request is done from Linden server to your own or hosted website.
In order to crack the request you would need to guess the Host name, the URL of the HTTP post, and the magic number.

This said, I take your point about the fact that you could still crack it.
So, I will add a SECURE_STRING parameter to make the SECURE_NUMBER harder to guess when the posted variable is empty.
I think with this amendment it then become secure enough for most users.

-- [[User:Corto Maltese|Corto Maltese]]

Secure HTTP Post

2008-07-02T21:17:16Z

Corto Maltese: Secure HTTP Post moved to HTTP Post request to a PHP server: Some people wrote a much better encryption page. this library is still valid to implement a simple PHP POST though

#REDIRECT [[HTTP Post request to a PHP server]]

HTTP Post request to a PHP server

2008-07-02T21:17:16Z

Corto Maltese: Secure HTTP Post moved to HTTP Post request to a PHP server: Some people wrote a much better encryption page. this library is still valid to implement a simple PHP POST though

{{LSL Header}}

== How to use ==
Second life allow script to make requests to a web site.

The command let you send Post data to PHP.
The format of the HTTP Post is however a bit tricky.

With this library let you call a PHP page and post as many variables in your call as you want.

On top of that I introduce a little checksum/password sytem to limit potential abuse.

== How to use ==

'''The second life script'''

In the beginning of your script you must copy the xrequest function
and also choose a SECRET_NUMBER and a SECRET_STRING.
In SL you should also make sure that the script is not visible to other people than yourself (this is the default access right).

<lsl>
integer SECRET_NUMBER=123456789;
string SECRET_STRING="XD4@5#-m";

xrequest(list l)
{
integer i;
string body;
integer len=llGetListLength(l) & 0xFFFE; // make it even
for (i=0;i<len;i+=2)
{
string varname=llList2String(l,i);
string varvalue=llList2String(l,i + 1);
if (i>0) body+="&";
body+=llEscapeURL(varname)+"="+llEscapeURL(varvalue);
}
string hash=llMD5String(body+llEscapeURL(SECRET_STRING),SECRET_NUMBER);
http_request_id = llHTTPRequest(url+"?hash="+hash,[HTTP_METHOD,"POST",HTTP_MIMETYPE,"application/x-www-form-urlencoded"],body);
}
</lsl>

To make a call to the function you have to provide 2 parameters:

For example:

xrequest("http://www.yourserver.com/your_page.php",["parameter1",123,"parameter2","parameter2 value"]);

The first parameter is the address of the webpage which will process your request. I assume, you own a website which supports PHP (about any version).

The second parameter is a list containing the parameters you want to pass to the page.
They will be sent to the page as if they had been type in a WebForm.
The list can be empty [] or contain any number of 'variable name','variable value' pairs.

'''The PHP Page'''

The php page must contains the function below, if you're a PHP wiz, you also include it inside another file.

Note that the page must be modified to contain your own SECRET_NUMBER.
Your page will then use the function checkHash() to make sure the correct password was used.
If the password is wrong, the page won't run any further.

If the password is right you can then read the content of the parameters using a simple $_POST["parameter_name"]

<php>
<?php
// this function tweak slightly urlencode to make it behave exactly like llEscapeURL in Second Life.
function llEscapeURL($s)
{
$s=str_replace(
array(" ","+","-",".","_"),
array("%20","%20","%2D","%2E","%5F"),
urlencode($s));
return $s;
}

// this my main SL page XML-RPC page
function checkHash()
{
global $body;
$hash=$_GET["hash"];
$body="";
$cpt=0;
$SECRET_NUMBER=123456789;
$SECRET_STRING="XD4@5#-m";

foreach ($_POST as $name => $value) {
if ($cpt++>0) $body.="&";
$body.=llEscapeURL($name)."=".llEscapeURL($value);
}
$calcHash=md5($body.$SECRET_STRING.':'.$SECRET_NUMBER);
if ($hash!=$calcHash)
{
sleep(2); // slow down the requests
echo "result=FAIL\nMSG=Invalid request.";
die;
}
}

checkHash();
// You can use the parameters here by simply using $_POST["parameter_name"]
echo "OK";
?>
</php>

I hope it helps.
Don't hesitate to ask any question to Corto Maltese or improve this page.

{{LSLC|Library}}

HTTP Post request to a PHP server

2008-07-02T21:15:22Z

Corto Maltese:

{{LSL Header}}

== How to use ==
Second life allow script to make requests to a web site.

The command let you send Post data to PHP.
The format of the HTTP Post is however a bit tricky.

With this library let you call a PHP page and post as many variables in your call as you want.

On top of that I introduce a little checksum/password sytem to limit potential abuse.

== How to use ==

'''The second life script'''

In the beginning of your script you must copy the xrequest function
and also choose a SECRET_NUMBER and a SECRET_STRING.
In SL you should also make sure that the script is not visible to other people than yourself (this is the default access right).

<lsl>
integer SECRET_NUMBER=123456789;
string SECRET_STRING="XD4@5#-m";

xrequest(list l)
{
integer i;
string body;
integer len=llGetListLength(l) & 0xFFFE; // make it even
for (i=0;i<len;i+=2)
{
string varname=llList2String(l,i);
string varvalue=llList2String(l,i + 1);
if (i>0) body+="&";
body+=llEscapeURL(varname)+"="+llEscapeURL(varvalue);
}
string hash=llMD5String(body+llEscapeURL(SECRET_STRING),SECRET_NUMBER);
http_request_id = llHTTPRequest(url+"?hash="+hash,[HTTP_METHOD,"POST",HTTP_MIMETYPE,"application/x-www-form-urlencoded"],body);
}
</lsl>

To make a call to the function you have to provide 2 parameters:

For example:

xrequest("http://www.yourserver.com/your_page.php",["parameter1",123,"parameter2","parameter2 value"]);

The first parameter is the address of the webpage which will process your request. I assume, you own a website which supports PHP (about any version).

The second parameter is a list containing the parameters you want to pass to the page.
They will be sent to the page as if they had been type in a WebForm.
The list can be empty [] or contain any number of 'variable name','variable value' pairs.

'''The PHP Page'''

The php page must contains the function below, if you're a PHP wiz, you also include it inside another file.

Note that the page must be modified to contain your own SECRET_NUMBER.
Your page will then use the function checkHash() to make sure the correct password was used.
If the password is wrong, the page won't run any further.

If the password is right you can then read the content of the parameters using a simple $_POST["parameter_name"]

<php>
<?php
// this function tweak slightly urlencode to make it behave exactly like llEscapeURL in Second Life.
function llEscapeURL($s)
{
$s=str_replace(
array(" ","+","-",".","_"),
array("%20","%20","%2D","%2E","%5F"),
urlencode($s));
return $s;
}

// this my main SL page XML-RPC page
function checkHash()
{
global $body;
$hash=$_GET["hash"];
$body="";
$cpt=0;
$SECRET_NUMBER=123456789;
$SECRET_STRING="XD4@5#-m";

foreach ($_POST as $name => $value) {
if ($cpt++>0) $body.="&";
$body.=llEscapeURL($name)."=".llEscapeURL($value);
}
$calcHash=md5($body.$SECRET_STRING.':'.$SECRET_NUMBER);
if ($hash!=$calcHash)
{
sleep(2); // slow down the requests
echo "result=FAIL\nMSG=Invalid request.";
die;
}
}

checkHash();
// You can use the parameters here by simply using $_POST["parameter_name"]
echo "OK";
?>
</php>

I hope it helps.
Don't hesitate to ask any question to Corto Maltese or improve this page.

{{LSLC|Library}}

HTTP Post request to a PHP server

2008-07-02T21:09:45Z

2007-12-03T23:04:16Z

Corto Maltese:

{{LSL Header}}

Second life allow script to make requests to a web site.
This now works quite well but scripters need to be careful of potential attacks.

In any scenario, it is safe to check that the request comes from one of your scripts only.

So I made a little function called xrequest, this function will make a request to a PHP page using your own secure SECRET_NUMBER password.
The PHP script can check that the password is right before processing the request.

This is simple and uses a good algorithm present in both LSL and PHP.

== How to use ==

'''The second life script'''

In the beginning of your script you must copy the xrequest function
and also choose a SECRET_NUMBER.
In SL you should also make sure that the script is not visible to other people than yourself (this is the default access right).

<pre>
integer SECRET_NUMBER=123456789;

xrequest(string url, list l)
{
integer i;
integer len=llGetListLength(l) & 0xFFFE; // makes the list count even
string body;

for (i=0;i<len;i+=2)
{
string varname=llList2String(l,i);
string varvalue=llList2String(l,i + 1);
if (i>0) body+="&";
body+=llEscapeURL(varname)+"="+llEscapeURL(varvalue);
}
string hash=llMD5String(body,SECRET_NUMBER);
http_request_id = llHTTPRequest(url+"?hash="+hash,[HTTP_METHOD,"POST",HTTP_MIMETYPE,"application/x-www-form-urlencoded"],body);
}
</pre>

To make a call to the function you have to provide 2 parameters:

For example:

xrequest("http://www.yourserver.com/your_page.php",["parameter1",123,"parameter2","parameter2 value"]);

The first parameter is the address of the webpage which will process your request. I assume, you own a website which supports PHP (about any version).

The second parameter is a list containing the parameters you want to pass to the page.
They will be sent to the page as if they had been type in a WebForm.
The list can be empty [] or contain any number of 'variable name','variable value' pairs.

'''The PHP Page'''

The php page must contains the function below, if you're a PHP wiz, you also include it inside another file.

Note that the page must be modified to contain your own SECRET_NUMBER.
Your page will then use the function checkHash() to make sure the correct password was used.
If the password is wrong, the page won't run any further.

If the password is right you can then read the content of the parameters using a simple $_POST["parameter_name"]

<pre>
<?php
// this function tweak slightly urlencode to make it behave exactly like llEscapeURL in Second Life.
function llEscapeURL($s)
{
return str_replace(
array("+","-",".","_"),
array("%20","%2D","%2E","%5F"),
urlencode($s));
}

// this my main SL page XML-RPC page
function checkHash()
{
global $body;
$hash=$_GET["hash"];
$body="";
$cpt=0;
$SECRET_NUMBER=123456789;
foreach ($_POST as $name => $value) {
if ($cpt++>0) $body.="&";
$body.=llEscapeURL($name)."=".llEscapeURL($value);
}
$calcHash=md5($body.':'.$SECRET_NUMBER);
if ($hash!=$calcHash)
{
sleep(2); // slow down the requests
echo "result=FAIL\nMSG=Invalid hash"; + $body="";
die;
}
}

checkHash();
// You can use the parameters here by simply using $_POST["parameter_name"]
echo "OK";
?>
</pre>

I hope it helps.
Don't hesitate to ask any question to Corto Maltese or improve this page.

{{LSLC|Library}}

SLEGO

2007-04-15T15:48:48Z

Corto Maltese:

SLEGO Competion in May

Comment un objet peut répondre a des commandes du clavier

2007-04-08T17:57:11Z

Corto Maltese:

Question de Map McMillan

Sur certaine places, la plupart du temps, les balls sont cachées par un truc du genre « /1 hidden » et visibles avec « /2 shown »

Est il possible de :

1/ choisir un canal personnalisé ? pas « 1 »… mais « /moi » ou » /map » ou « /1map » ou "/n'importe quel autre mot ou chiffre"

La reponse est oui. Pour detected /map il faut ecouter le cannal 0

2/ de faire pareil avec tt les prims? pas uniquement les balls mais aussi des trucs genre les meubles dans 1 maison ?

Oui, tous les prims dans SL sont egaux, pas besoin d'etre une boule.

3/ sinon comment faire pour que les dits « home furnitures » ne soient pas utilisables par le 1er voyageur de passage ?

Voir llGetOwner() plus bas.

----
Je vais répondre a toutes ces questions mais plutot de répondre point par point je vais expliquer les mécanismes sous jacents.

== Les cannaux de chat ==

Second Life a un systeme de chat assez puissant; Il y a 4294967296 canaux numérotés de -2147483648 a +2147483647.
En general quand on parle on utilise le canal 0.
Par exemple quand on tape 'Hello' ca utilise le canal 0 et ca produit le meme effet que de taper /0 Hello.
Avec le clavier on peut aussi envoyer un message dans un cannal différent.
Par exemple '/123 Hello' envoie le message Hello dans le cannal 123.
Pour peu qu'un script ecoute ce cannal, il peut repondre a cette commande.

== Mais comment est-ce qu'un script peut ecouter un cannal?==

La commande principale est llListen, llListen ecoute un cannal, une personne ou toutes, et un message ou tous.
La syntaxe est
llListen(integer cannal,string nom,key id, string message);
Souvent on utilise comme ca:
llListen(123,"","","");
La ca ecoute tout sur le cannal 123.

Notez que l'on peut ecouter le cannal de chat normal.
llListen(0,"","","");

Quand un message est détecté, le sim lance l'event listen dans votre script

listen(integer channel, string name, key id, string msg)

Channel est le channel recu.
Name et id, c'est la personne ou l'objet qui a envoyé le message.
Msg c'est le contenu du message.

== Example ==

Voici un exemple un peu plus complet:
Ce script ecoute le cannal 5, mais uniquement le proprietaire du prim.
Les commandes sont '/5 rouge', '/5 vert', et '/5 bleu'. Je vous laisse deviner ce que ca fait.

default
{
state_entry()
{
string name=""; // j'ecoute tous les noms
key id=llGetOwner(); // mais uniquement mon proprio
string msg=""; // j'ecoute tous les messages
llListen(5,name,id,msg);
}

changed(integer st)
{
// ca c'est pour relancer le listen
// quand l'objet change de proprietaire
if (st & CHANGED_OWNER)
llResetScript();
}

listen(integer channel, string name, key id, string msg)
{
// cette ligne n'est pas réellement nescessaire ici
// comme on ecoute qu'une personne et qu'un cannal
if (id==llGetOwner() && channel==5)
{
if (msg=="rouge") llSetColor(<1,0,0>, ALL_SIDES);
if (msg=="vert") llSetColor(<0,1,0>, ALL_SIDES);
if (msg=="bleu") llSetColor(<0,0,1>, ALL_SIDES);
}
}
}

== Détails interessants ==
1 - Les cannaux de SL ne son't pas sécurisés

Particulierement tout cannal entre 0 et 100, est probablement utilisé par d'autres scripts. Si vous faites un frigo qui s'ouvre et se ferme sur commande c'est surement pas tres grave mais soyez vigilant que ce que vous tapez ou faites taper sur un cannal peut etre écouté par quelqu'un d'autre.

2 - Les commandes llListen se ferment quand vous changez le 'state' d'un script

Je sais pas si beaucoup de gens utilisent les scripts 'state'. Si oui, il faut savoir que toutes les commandes listen sont fermées automatiquement quand vous changez de state, ou que le script est reset.
Dans l'exemple plus haut, le reset a pour effet de fermer le listen pour le proprietaire precedent et reouvre pour le nouveau proprietaire.

3 - Les commandes llSay sont lentes et pas garanties
Envoyer des messages d'un objet a l'autre en utilisant llSay et llListen est la seule facon pour transmettre des messages sur de longues distances.
Ce qu'il faut savoir neanmoins c'est que llSay produit un délai dans le script et aussi le listen event peut prendre beaucoup de temps a traiter la commande.
Quand le listen event prends du temps les commandes sont empilés et traitées une par une plus tard. Néanmoins quand la pile atteinds 30 ou 40, les messages sont perdus.
Ca arrive beaucoup au jeu de Tringo, le tableau mets du temps a raffraichir les scores et parfois certains scores sont perdus de cette facons.

4 - Un script ne s'entends pas

Je peux me tromper mais je crois qu'un script ne peut pas entendre un message qui provient du meme prim.
Si dans un script vous ecrivez llSay(5,"Rouge"); et que dans le meme script ou autre script du meme prim vous écriver llListen(5,"","",""); les message ne sont pas transmis.
Il y de meilleurs techniques (plus rapides et sécurisées) pour envoyer des messages de scripts en script; voir ((llMessageLinked)).

5 - Une commande listen peut consommer beaucoup de ressources

Gardez a l'esprit que votre code listen va etre exécuté pour toutes les lignes tapées dans ce cannal.
Si vous avez beaucoup d'objets qui ecoutent un cannal bruyant comme le cannal 0, vous pouvez assez ralentir le sim significativement.
Aussi si vous ecoutez de tres nombreux cannaux (qui n'a pas écrit un Channel Scanner), le simulateur n'aime pas beaucoup ca. A bon entendeur salut.

Comment un objet peut répondre a des commandes du clavier

2007-04-08T13:04:30Z

Corto Maltese: /* Mais comment est-ce qu'un script peut ecouter un cannal? */

Question de Map McMillan

Sur certaine places, la plupart du temps, les balls sont cachées par un truc du genre « /1 hidden » et visibles avec « /2 shown »

Est il possible de :

1/ choisir un canal personnalisé ? pas « 1 »… mais « /moi » ou » /map » ou « /1map » ou "/n'importe quel autre mot ou chiffre"
2/ de faire pareil avec tt les prims? pas uniquement les balls mais aussi des trucs genre les meubles dans 1 maison ?
3/ sinon comment faire pour que lesdits « home furnitures » ne soient pas utilisables par le 1er voyageur de passage ?

----
Je vais répondre a toutes ces questions mais plutot de répondre point par point je vais expliquer les mécanismes sous jacents.

== Les cannaux de chat ==

Second Life a un systeme de chat assez puissant; Il y a 4294967296 canaux numérotés de -2147483648 a +2147483647.
En general quand on parle on utilise le canal 0.
Par exemple quand on tape 'Hello' ca utilise le canal 0 et ca produit le meme effet que de taper /0 Hello.
Avec le clavier on peut aussi envoyer un message dans un cannal différent.
Par exemple '/123 Hello' envoie le message Hello dans le cannal 123.
Pour peu qu'un script ecoute ce cannal, il peut repondre a cette commande.

== Mais comment est-ce qu'un script peut ecouter un cannal?==

La commande principale est llListen, llListen ecoute un cannal, une personne ou toutes, et un message ou tous.
La syntaxe est
llListen(integer cannal,string nom,key id, string message);
Souvent on utilise comme ca:
llListen(123,"","","");
La ca ecoute tout sur le cannal 123.

Notez que l'on peut ecouter le cannal de chat normal.
llListen(0,"","","");

Quand un message est détecté, le sim lance l'event listen dans votre script

listen(integer channel, string name, key id, string msg)

Channel est le channel recu.
Name et id, c'est la personne ou l'objet qui a envoyé le message.
Msg c'est le contenu du message.

== Example ==

Voici un exemple un peu plus complet:
Ce script ecoute le cannal 5, mais uniquement le proprietaire du prim.
Les commandes sont '/5 rouge', '/5 vert', et '/5 bleu'. Je vous laisse deviner ce que ca fait.

default
{
state_entry()
{
string name=""; // j'ecoute tous les noms
key id=llGetOwner(); // mais uniquement mon proprio
string msg=""; // j'ecoute tous les messages
llListen(5,name,id,msg);
}

changed(integer st)
{
// ca c'est pour relancer le listen
// quand l'objet change de proprietaire
if (st & CHANGED_OWNER)
llResetScript();
}

listen(integer channel, string name, key id, string msg)
{
// cette ligne n'est pas réellement nescessaire ici
// comme on ecoute qu'une personne et qu'un cannal
if (id==llGetOwner() && channel==5)
{
if (msg=="rouge") llSetColor(<1,0,0>, ALL_SIDES);
if (msg=="vert") llSetColor(<0,1,0>, ALL_SIDES);
if (msg=="bleu") llSetColor(<0,0,1>, ALL_SIDES);
}
}
}

== Détails interessants ==
1 - Les cannaux de SL ne son't pas sécurisés

Particulierement tout cannal entre 0 et 100, est probablement utilisé par d'autres scripts. Si vous faites un frigo qui s'ouvre et se ferme sur commande c'est surement pas tres grave mais soyez vigilant que ce que vous tapez ou faites taper sur un cannal peut etre écouté par quelqu'un d'autre.

2 - Les commandes llListen se ferment quand vous changez le 'state' d'un script

Je sais pas si beaucoup de gens utilisent les scripts 'state'. Si oui, il faut savoir que toutes les commandes listen sont fermées automatiquement quand vous changez de state, ou que le script est reset.
Dans l'exemple plus haut, le reset a pour effet de fermer le listen pour le proprietaire precedent et reouvre pour le nouveau proprietaire.

3 - Les commandes llSay sont lentes et pas garanties
Envoyer des messages d'un objet a l'autre en utilisant llSay et llListen est la seule facon pour transmettre des messages sur de longues distances.
Ce qu'il faut savoir neanmoins c'est que llSay produit un délai dans le script et aussi le listen event peut prendre beaucoup de temps a traiter la commande.
Quand le listen event prends du temps les commandes sont empilés et traitées une par une plus tard. Néanmoins quand la pile atteinds 30 ou 40, les messages sont perdus.
Ca arrive beaucoup au jeu de Tringo, le tableau mets du temps a raffraichir les scores et parfois certains scores sont perdus de cette facons.

4 - Un script ne s'entends pas

Je peux me tromper mais je crois qu'un script ne peut pas entendre un message qui provient du meme prim.
Si dans un script vous ecrivez llSay(5,"Rouge"); et que dans le meme script ou autre script du meme prim vous écriver llListen(5,"","",""); les message ne sont pas transmis.
Il y de meilleurs techniques (plus rapides et sécurisées) pour envoyer des messages de scripts en script; voir ((llMessageLinked)).

5 - Une commande listen peut consommer beaucoup de ressources

Gardez a l'esprit que votre code listen va etre exécuté pour toutes les lignes tapées dans ce cannal.
Si vous avez beaucoup d'objets qui ecoutent un cannal bruyant comme le cannal 0, vous pouvez assez ralentir le sim significativement.
Aussi si vous ecoutez de tres nombreux cannaux (qui n'a pas écrit un Channel Scanner), le simulateur n'aime pas beaucoup ca. A bon entendeur salut.

Comment un objet peut répondre a des commandes du clavier

2007-04-08T12:59:56Z

Corto Maltese:

Question de Map McMillan

Sur certaine places, la plupart du temps, les balls sont cachées par un truc du genre « /1 hidden » et visibles avec « /2 shown »

Est il possible de :

1/ choisir un canal personnalisé ? pas « 1 »… mais « /moi » ou » /map » ou « /1map » ou "/n'importe quel autre mot ou chiffre"
2/ de faire pareil avec tt les prims? pas uniquement les balls mais aussi des trucs genre les meubles dans 1 maison ?
3/ sinon comment faire pour que lesdits « home furnitures » ne soient pas utilisables par le 1er voyageur de passage ?

----
Je vais répondre a toutes ces questions mais plutot de répondre point par point je vais expliquer les mécanismes sous jacents.

== Les cannaux de chat ==

Second Life a un systeme de chat assez puissant; Il y a 4294967296 canaux numérotés de -2147483648 a +2147483647.
En general quand on parle on utilise le canal 0.
Par exemple quand on tape 'Hello' ca utilise le canal 0 et ca produit le meme effet que de taper /0 Hello.
Avec le clavier on peut aussi envoyer un message dans un cannal différent.
Par exemple '/123 Hello' envoie le message Hello dans le cannal 123.
Pour peu qu'un script ecoute ce cannal, il peut repondre a cette commande.

== Mais comment est-ce qu'un script peut ecouter un cannal?==

La commande principale est llListen, llListen ecoute un cannal, une personne ou toutes, et un message ou tous.
La syntaxe est
llListen(integer cannal,string nom,key id, string message);
Souvent on utilise comme ca:
llListen(123,"","","");
La ca ecoute tout sur le cannal 123.

Notez que l'on peut ecouter le cannal de chat normal.
llListen(0,"","","");

Voici un exemple un peu plus complet:
Ce script ecoute le cannal 5, mais uniquement le proprietaire du prim.
Les commandes sont '/5 rouge', '/5 vert', et '/5 bleu'. Je vous laisse deviner ce que ca fait.

default
{
state_entry()
{
string name=""; // j'ecoute tous les noms
key id=llGetOwner(); // mais uniquement mon proprio
string msg=""; // j'ecoute tous les messages
llListen(5,name,id,msg);
}

changed(integer st)
{
// ca c'est pour relancer le listen
// quand l'objet change de proprietaire
if (st & CHANGED_OWNER)
llResetScript();
}

listen(integer channel, string name, key id, string msg)
{
// cette ligne n'est pas réellement nescessaire ici
// comme on ecoute qu'une personne et qu'un cannal
if (id==llGetOwner() && channel==5)
{
if (msg=="rouge") llSetColor(<1,0,0>, ALL_SIDES);
if (msg=="vert") llSetColor(<0,1,0>, ALL_SIDES);
if (msg=="bleu") llSetColor(<0,0,1>, ALL_SIDES);
}
}
}

== Détails interessants ==
1 - Les cannaux de SL ne son't pas sécurisés

Particulierement tout cannal entre 0 et 100, est probablement utilisé par d'autres scripts. Si vous faites un frigo qui s'ouvre et se ferme sur commande c'est surement pas tres grave mais soyez vigilant que ce que vous tapez ou faites taper sur un cannal peut etre écouté par quelqu'un d'autre.

2 - Les commandes llListen se ferment quand vous changez le 'state' d'un script

Je sais pas si beaucoup de gens utilisent les scripts 'state'. Si oui, il faut savoir que toutes les commandes listen sont fermées automatiquement quand vous changez de state, ou que le script est reset.
Dans l'exemple plus haut, le reset a pour effet de fermer le listen pour le proprietaire precedent et reouvre pour le nouveau proprietaire.

3 - Les commandes llSay sont lentes et pas garanties
Envoyer des messages d'un objet a l'autre en utilisant llSay et llListen est la seule facon pour transmettre des messages sur de longues distances.
Ce qu'il faut savoir neanmoins c'est que llSay produit un délai dans le script et aussi le listen event peut prendre beaucoup de temps a traiter la commande.
Quand le listen event prends du temps les commandes sont empilés et traitées une par une plus tard. Néanmoins quand la pile atteinds 30 ou 40, les messages sont perdus.
Ca arrive beaucoup au jeu de Tringo, le tableau mets du temps a raffraichir les scores et parfois certains scores sont perdus de cette facons.

4 - Un script ne s'entends pas

Je peux me tromper mais je crois qu'un script ne peut pas entendre un message qui provient du meme prim.
Si dans un script vous ecrivez llSay(5,"Rouge"); et que dans le meme script ou autre script du meme prim vous écriver llListen(5,"","",""); les message ne sont pas transmis.
Il y de meilleurs techniques (plus rapides et sécurisées) pour envoyer des messages de scripts en script; voir ((llMessageLinked)).

5 - Une commande listen peut consommer beaucoup de ressources

Gardez a l'esprit que votre code listen va etre exécuté pour toutes les lignes tapées dans ce cannal.
Si vous avez beaucoup d'objets qui ecoutent un cannal bruyant comme le cannal 0, vous pouvez assez ralentir le sim significativement.
Aussi si vous ecoutez de tres nombreux cannaux (qui n'a pas écrit un Channel Scanner), le simulateur n'aime pas beaucoup ca. A bon entendeur salut.

2007-01-28T14:14:22Z

Corto Maltese:

These two function are directly translated from Gary Katch web site : [[http://alcor.concordia.ca/~gpkatch/]].
I however had to make some modifications.

1 - I translated from C, to LSL. This was easy, is merely replacing int by integer.

2 - I had to make the functions 32 compatible. The original function uses 64 bits integers but Second Life supports only 32 bits

When the line " y = (10000*g + 14780)/3652425 " was run it was going over the 32 bits.
I solved this issue by applying and offset of 1600 years. So rather than working with the number of days since March 1st 0001, the functions origin is March 1st 1600.
According to my test the functions work at least from 1600 to 2181.

----
The function gday fiven integer y, m, d, calculate day number g.

<pre>
integer gday(integer yy, integer mm, integer dd)
{
// convert date to day number
integer m = (mm + 9)%12; // mar=0, feb=11
integer y = yy - 1600 - m/10; // if Jan/Feb, year--
return y*365 + y/4 - y/100 + y/400 + (m*306 + 5)/10 + (dd - 1);
}
</pre>

<pre>
list sdate(integer d)
{
// convert day number to y,m,d format
integer y = (10000*d + 14780)/3652425;
integer ddd = d - (y*365 + y/4 - y/100 + y/400);
if (ddd < 0) {
y--;
ddd = d - (y*365 + y/4 - y/100 + y/400);
}
integer mi = (52 + 100*ddd)/3060;
integer dd = ddd - (mi*306 + 5)/10 + 1;
string nth;
integer ddn = dd % 10;
if (dd>=10 && dd<=20) nth="th";
else if (ddn==1) nth="st";
else if (ddn==2) nth="nd";
else if (ddn==3) nth="rd";
else nth="th";
return [
1600 + y + (mi + 2)/12,
(mi + 2)%12 + 1,
dd,
nth];
}
</pre>
Today
<pre>
integer today()
{
string DateUTC = llGetDate();
integer year = (integer)llGetSubString(DateUTC, 0, 3);
integer month = (integer)llGetSubString(DateUTC, 5, 6);
integer day = (integer)llGetSubString(DateUTC, 8, 9);
return gday(year,month,day);
}
</pre>
Date differences.
The difference in days between two dates:
<pre>
return gday(y2,m2,d2) - gday(y1,m1,d1);
</pre>

Day offsets.
The date n days from y,m,d:
<pre>
sdate(gday(y,m,d) + n)
</pre>
Date legality.
To check if a date is on the calendar:
<pre>
integer isLegal(integer yy, integer mm, integer dd)
{
list dt=sdate(gday(yy,mm,dd));
return
llList2Integer(dt,0)==yy
&& llList2Integer(dt,1)==mm
&& llList2Integer(dt,2)==dd;
}
</pre>
Those functions are straight forward formatting function.
They can be adapted for the different languages and date format.
<pre>
list weekDays=["Sun","Mon","Tue","Wed","Thu","Fri","Sat"];

string weekDay(integer g)
{
return llList2String(weekDays,(g + 3) % 7);
}

list months=["","January","February","March",
"April","May","June",
"July","August","September",
"October","November","December"];

string fullDate(integer g)
{
list dt = sdate(g);
return weekDay(g)
+ " "
+ llList2String(months,llList2Integer(dt,1))
+ " "
+ (string) llList2Integer(dt,2)
+ llList2String(dt,3)
+ " "
+ (string) llList2Integer(dt,0);
}
</pre>

User:Corto Maltese

2007-01-28T12:20:40Z

Corto Maltese:

Hi,
My name in SL is Corto Maltese.
In SL am mainly a scripter and I like to design games.

I post here my own scripts, scripts I update to suit my own use, or answer to question I am asked.

[[Corto Maltese's Date and Time Library]]