Second Life Wiki - User contributions [en]

Object rez

2012-10-17T02:06:26Z

Elendreal Halasy:

{{LSL_Event|event_id=28|event_delay|event=object_rez
|p1_type=key|p1_name=id|p1_desc=[[UUID]] of object rezzed.
|event_desc=Triggered when the object rezzes an object.
|constants
|spec
|examples=
<lsl>
//gives inventory to object when it rezzes.
string inventory;
string object;

default
{
touch_start(integer count)
{
object=llGetInventoryName(INVENTORY_OBJECT,0); //get name of the 1st object in inventory
llRezObject(object, llGetPos() + <0.0, 0.0, 0.5>, ZERO_VECTOR, ZERO_ROTATION, 0); //rez the 1st object
}
object_rez(key id)
{
inventory=llGetInventoryName(INVENTORY_OBJECT,1); //get name of the 2nd object in inventory
llGiveInventory(id,inventory); //give 2nd object to 1st object when rezzed
}
}
</lsl>
|helpers
|also_header
|also_events=
{{LSL DefineRow||[[on_rez]]|Triggered when the object the script is in is rezzed}}
|also_functions=
{{LSL DefineRow||[[llRezObject]]|Used to rez an object at the center of mass}}
{{LSL DefineRow||[[llRezAtRoot]]|Used to rez an object at the root}}
|also_articles
|also_footer
|notes
|mode
|cat1=Rez
|cat2
|cat3
|cat4
}}

Object rez

2012-10-17T02:02:16Z

Elendreal Halasy: No present issues with function at this time.

<lsl>
//gives inventory to object when it rezzes.
string inventory;
string object;

default
{
touch_start(integer count)
{
object=llGetInventoryName(INVENTORY_OBJECT,0); //get name of the 1st object in inventory
llRezObject(object, llGetPos() + <0.0, 0.0, 0.5>, ZERO_VECTOR, ZERO_ROTATION, 0); //rez the 1st object
}
object_rez(key id)
{
inventory=llGetInventoryName(INVENTORY_OBJECT,1); //get name of the 2nd object in inventory
llGiveInventory(id,inventory); //give 2nd object to 1st object when rezzed
}
}
</lsl>
|helpers
|also_header
|also_events=
{{LSL DefineRow||[[on_rez]]|Triggered when the object the script is in is rezzed}}
|also_functions=
{{LSL DefineRow||[[llRezObject]]|Used to rez an object at the center of mass}}
{{LSL DefineRow||[[llRezAtRoot]]|Used to rez an object at the root}}
|also_articles
|also_footer
|notes
|mode
|cat1=Rez
|cat2
|cat3
|cat4
}}

Object rez

2012-10-17T02:01:33Z

Elendreal Halasy: Issues resolved, second was linked to first which has since been closed.

{{LSL_Event|event_id=28|event_delay|event=object_rez
|p1_type=key|p1_name=id|p1_desc=[[UUID]] of object rezzed.
|event_desc=Triggered when the object rezzes an object.
|constants
|spec
|caveats=
* Triggers in all running scripts with an [[object_rez]] event, AND in the same '''prim''' as the script calling [[llRezObject]] or [[llRezAtRoot]].
** Does NOT trigger in linked prims.
|examples=
<lsl>
//gives inventory to object when it rezzes.
string inventory;
string object;

default
{
touch_start(integer count)
{
object=llGetInventoryName(INVENTORY_OBJECT,0); //get name of the 1st object in inventory
llRezObject(object, llGetPos() + <0.0, 0.0, 0.5>, ZERO_VECTOR, ZERO_ROTATION, 0); //rez the 1st object
}
object_rez(key id)
{
inventory=llGetInventoryName(INVENTORY_OBJECT,1); //get name of the 2nd object in inventory
llGiveInventory(id,inventory); //give 2nd object to 1st object when rezzed
}
}
</lsl>
|helpers
|also_header
|also_events=
{{LSL DefineRow||[[on_rez]]|Triggered when the object the script is in is rezzed}}
|also_functions=
{{LSL DefineRow||[[llRezObject]]|Used to rez an object at the center of mass}}
{{LSL DefineRow||[[llRezAtRoot]]|Used to rez an object at the root}}
|also_articles
|also_footer
|notes
|mode
|cat1=Rez
|cat2
|cat3
|cat4
}}

User:Elendreal Halasy

2012-10-17T01:52:34Z

Elendreal Halasy:

I currently run two sims Betelgeuse and Dangerfield. I also script, and will do so for you if you ask nicely. If you ask really nicely I may even build a web application for you that interfaces with Second Life content.

If you are interested in any of my services please contact my in Second Life. My profile can be found [https://my.secondlife.com/elendreal.halasy (here)].

User:Elendreal Halasy

2012-10-17T01:51:42Z

Elendreal Halasy: Created page with "I currently run two sims Betelgeuse and Dangerfield. If you are interested please contact my in Second Life. My Second Life profile can be found [https://my.secondlife.com/elend…"

I currently run two sims Betelgeuse and Dangerfield.

If you are interested please contact my in Second Life. My Second Life profile can be found [https://my.secondlife.com/elendreal.halasy (here)].

Get Profile Picture

2012-10-17T01:44:20Z

Elendreal Halasy: Removed my.secondlife.com edit -- Jira article from over a year ago, assumed project abandoned. Re-post notice if resumed.

{{LSL Header}}
Get Profile Picture by Valentine Foxdale

<lsl>
// Snippets and HTTPRequest bits were taken from:
//~ RANDOM PROFILE PROJECTOR v5.4.5 by Debbie Trilling ~

// Get Profile Picture by Valentine Foxdale
// optmisation by SignpostMarv Martin
// workaround for WEB-1384 by Viktoria Dovgal:
// try meta tag instead of img first, try img as backup in case meta breaks
list sides;
list deftextures;

string profile_key_prefix = "<meta name=\"imageid\" content=\"";
string profile_img_prefix = "<img alt=\"profile image\" src=\"http://secondlife.com/app/image/";
integer profile_key_prefix_length; // calculated from profile_key_prefix in state_entry()
integer profile_img_prefix_length; // calculated from profile_key_prefix in state_entry()

GetProfilePic(key id) //Run the HTTP Request then set the texture
{
//key id=llDetectedKey(0); This breaks the function, better off not used
string URL_RESIDENT = "http://world.secondlife.com/resident/";
llHTTPRequest( URL_RESIDENT + (string)id,[HTTP_METHOD,"GET"],"");
}
GetDefaultTextures() //Get the default textures from each side
{
integer i;
integer faces = llGetNumberOfSides();
for (i = 0; i < faces; i++)
{
sides+=i;
deftextures+=llGetTexture(i);
}
}
SetDefaultTextures() //Set the sides to their default textures
{
integer i;
integer faces;
faces = llGetNumberOfSides();
for (i = 0; i < faces; i++)
{
llSetTexture(llList2String(deftextures,i),i);
}
}
default
{
state_entry()
{
profile_key_prefix_length = llStringLength(profile_key_prefix);
profile_img_prefix_length = llStringLength(profile_img_prefix);
llSetText("Touch for this object to display your profile picture!",<0.8,0,1>,1);
//Note: Usage of another person's profile picture without their permission may be viewed as copyright infringement.
GetDefaultTextures();
}
touch_start(integer total_number)
{
GetProfilePic(llDetectedKey(0));
}
http_response(key req,integer stat, list met, string body)
{
integer s1 = llSubStringIndex(body, profile_key_prefix);
integer s1l = profile_key_prefix_length;
if(s1 == -1)
{ // second try
s1 = llSubStringIndex(body, profile_img_prefix);
s1l = profile_img_prefix_length;
}

if(s1 == -1)
{ // still no match?
SetDefaultTextures();
}
else
{
s1 += s1l;
key UUID=llGetSubString(body, s1, s1 + 35);
if (UUID == NULL_KEY) {
SetDefaultTextures();
}
else {
llSetTexture(UUID,ALL_SIDES);
}
}
}
}
</lsl>

SL Cert - Intermediate Scripting

2009-11-30T09:32:05Z

Elendreal Halasy: /* Prerequisites */

{{SLCert Navbox}}
[[Category:Certification]]

==Overview==

Criteria required for persons to become certified in intermediate scripting.

==Audience==

Persons who wish to demonstrate competence in intermediate LSL scripting.

==Prerequisites==

Applicant must hold basic scripting certification.

(Recommended) An application should have a basic understanding of algebraic functions.

==Criteria for testing to intermediate level==

Scripting includes a wide variety of categories. At the intermediate level the different categories are broken out separately. The different categories are given below with the associated topics. Note that there is some overlap between categories. This is because the different topics can not be easily divided and are related. Some topics may be necessary for multiple categories and are listed multiple times to avoid prerequisite clashes between categories.

=== Primitives, Objects ===

The different ways scripts can manipulate an object is included in this category. It does not include the ways to interact between objects and agents. The interaction categories are included in the detection and communications categories.

* Faces
# Each face on a prim has a number associated with it.
# The number varies by prim type and can vary depending if the prim has a "cut."
# It is not necessary to memorize all of the face numbers for every prim. It is necessary to know how to find the information and understand how the convention depends on whether or not a prim is cut.

* Changing color
# Commands for changing the color
# RGB definition of a color vector in LSL and how it is different from the editor window.
# Know how to convert back and forth between an RGB color vector in LSL and the format found in the editor window.
# Know how to identify when a color is changed using the changed event and the predefined constant CHANGED_COLOR.

* Changing alpha(transparency)
# Commands for changing the alpha level
# Difference between changing alpha level and the two different transparant textures, TEXTURE_TRANSPARENT and e97cf410-8e61-7005-ec06-629eba4cd1fb (invisiprim).
# Know how to identify when an alpha level is changed using the changed event and the predefined constant CHANGED_COLOR.

* Changing textures
# Commands for changing the textures
# Predefined constants for UUIDs of textures
# Know the difference between the constants TEXTURE_TRANSPARENT, TEXTURE_BLANK, TEXTURE_MEDIA, and TEXTURE_PLYWOOD.
# Know how to identify when a texture is changed using the changed event and the predefined constant CHANGED_TEXTURE.

* Particles
# Command to create particles
# basic limitation of particles
# basic understanding on how to turn particles on and turn.

* Link commands and options
# Commands to determine the UUID, link number, total number of prims etc. for prims within the current object.

* Text and pie menu text
# Commands to change the text over a prim.
# Commands to change the text for different options in the pie menu.

* Primitive name and description
# Commands to get the name and description of a prim.
# Commands to change the name and description of a prim.

* Dataserver events
# Basic understanding of the data server event.
# Basic understanding of the different kinds of information that can be obtained using the Dataserver event.

* Obtaining object information
# Getting agent information (llRequestAgentData)
# Getting object information (llGetObjectDetails)

* Sound
# Commands to preload sound files.
# Commands to play sounds.

Note that for many of these items there are a large number of commands asociated with the topic. For example, just to change the color of a prim the following commands can be used: llSetColor, llSetLinkColor, llGetColor, llSetPrimitiveParams, llGetPrimitiveParams, llSetLinkPrimitiveParams. It is adequate for a person to just know how to use llSetPrimitiveParams and llSetLinkPrimitiveParams to change the color of a prim, but the person should know the other commands in case they are asked to adapt another person's code.

=== Avatars and Agents ===

* Sit positions and associated functions
# Setting the position and rotation of a sit position.
# Turning off a sit position after it has been set.
# Know how to set the camera orientation for a sitting avatar.

* Permissions
# Basic understanding of the permissions system.
# Basic understanding of the different types of permissions that may be obtained.
# Know how to obtain permissions and basic understanding when it is required.

* Animations
# Know how to set a the animation of a person sitting on a prim.
# Know how to obtain permission before setting the animation.
# Know how to remove an active animation.

* Camera Controls
# Know how to obtain permission to change the camera orientation.
# Know the basic ways to change the camera. (Static positioning)

* Dataserver
# Know the commands that can be used to obtain information about an agent.
# Know how to obtain agent and avatar information via the data server event.

A person should know the basic ways to manipulate and change an avatar. The person should be able to set and clear sit positions on a prim. The person should be able to set the default camera position for an agent once their avatar is sitting on a prim. The person should know how to find the UUID and link number of an avatar when an agent sits on an object.

A person should demonstrate the basic use of the permission system. This includes the different types of permissions. Also, the person should know under what circumstances the agent is given a dialog to obtain permissions and when the dialog is not provided to the agent. The different permissions are not limited to just animations but include all permissions.

The person should demonstrate a basic understanding of how to change a camera. The person is required to be able to move a camera to look at a specific point but not necessarily calculate specific rotations for a given view. The person should be able to obtain permission to change a camera and know how to change it.

The person should be able to identify all of the options available for the data server event and find a given piece of information. The person should be able to manipulate the information and identify what the information is and any limitations. For example, a query to determine if an agent is online will only determine if the agent is online and has provided permission for the owner of the script to determine if the agent is online.

=== Inventory and Simulator Information ===

* Notecards
# Get the number of lines in a note card.
# Step through and get each line in a note card.
# Know how to stop reading a note card by testing for the EOF constant.

* Detect when the inventory has changed.
* Inventory information
# Get the name of the creator for an object.
# Inventory numbering system.
# Inventory types.
# Inventory Permissions.

* Basic use of the llRequestSimulatorData command.

A person seeking intermediate accreditation for the inventory and simulator information should be able to read the full contents of a note card and perform basic string manipulations to determine and react to the contents on a given line in the note card. The person should be able to read the full contents of the note card using both the number of lines in the card and using the EOF constant.

The person should be able to use the changed event to determine when the inventory has been changed and react accordingly.

The person should be able to get basic information about specific inventory items. The person should know how to search all items in the inventory and search all inventory items of a given type. This implies a basic understanding of how the inventory is numbered in relation to the different types.

=== Intermediate I/0 ===

* Chat commands
# Dialogs
# Limitations of chat commands
# Email

* Text and menu
# Setting text over an object
# Commands to manipulate the pie menu

* Link messages
# The link_message event.
# Sending link messages.
# Limiting link messages to specific prims within a build.

* Basic security
# Relying on arcane channels is not secure.
# Methods to insure a message is coming from an agent/object.
# Basic validation using MD5 and SHA1 hashes

In addition to the basic chat commands and listen event defined in the basic level the person should now be able to perform more advanced interactions including the use of dialogs. Also the person should have a broader understanding of the limitations of chat commands and know how to use the options to share email messages between scripts.

Also, the person should be able to change and manipulate the text over an object as well as remove the text over an object. The various commands to change the text in a pie menu should also be known.

In addition to the chat and listening events the person should also know how to use link messages to communicate between scripts within an object. The person should know all of the options to communicate to specific prims or all of the prims in an object using link messages.

Finally, the person should have a basic understanding of security issues and limitations. The person should be able to identify and check for specific agents as well as check and limit communications for ownership and group identities.

Predefined channels (DEBUG_CHANNEL and PUBLIC_CHANNEL).

=== Physics ===

* Linear and Angular Force
# Commands for Force
# Know the difference between local and global settings.
# Know the difference between linear and angular forces.
* Linear and Angular Impulse
# Commands for Impulse
# Know the difference between local and global settings.
# Know the difference between linear and angular impulse.
* Vehicles
# Know the basic commands and settings to initiate a vehicle.
# Know the basic ideas behind the different options.
# Know the impact of changing the individual parameters.

The person who wants to achieve an intermediate rating for physics should know all of the basic commands for both linear and angular force as well as momentum. The person should know the difference between the local and global settings. The person should know the difference between the the force/torque commands and the impulse commands.

The person should know the relationship between force and impulse. Both are representations of Newton's Second Law where force is the differential form and impulse is the integral form. The person should understand the relationship between force, mass, and acceleration as well as the relationship between impulse and momentum.

The very basic commands of scripting a vehicle should be known. At the intermediate level a person is not expected to be able to create a script for a vehicle but should understand the basic commands necessary for it's functionality and alter an existing vehicle script.

=== Detection ===

* Touch events.
# The three touch events.
# Functions to detect information about who has touched a prim.
# Passing touch information to other prims in a build.

* Collision events
# The three collision events.
# Functions to detect information about what/who took part in the collision.

* Land collision events
# The three land collision events.
# Functions to detect information about what/who took part in the land collision.

* Sensors
# The sensor commands.
# The two sensor related events.
# Limiting the scope of a sensor.
# Limitations of a sensor.

A person who wishes to achieve an intermediate certification in detection should know the different events in which detection is relevant. The person should know how the different detection commands are used within the different events. The person should know be able to construct scripts that make use of the events and detection routines and combine them.

Additionally a person should be able to use sensors to detect a person. The person should know the difference between a repeating and one time sensor. The person should know how to construct scripts that make use of the sensor and no_sensor events. The person should know the limitations of the commands and understand the importance and how to narrowly define a sensor.

=== Programming and Software Development ===

* More advanced use of lists.
# Adding to a list.
# Removing part of a list.
# Inserting into a list.
# Replacing part of a list.
# Finding an item in a list.
* More advanced string functions.
# Removing a substring.
# Replacing a substring.
# Inserting a substring.
# Finding a substring.
* More advanced revision systems.
# Basic understanding and use of at least on revision control system. (ex: RCS, subversion, or git)
# Be able to maintain revisions and find particular revisions using at least one revision control system.
* Workflow
# Demonstrate effective interactions with clients and remain flexible through the entire development cycle.
# Be able to establish a basic plan for the creation of a script that must accomplish multiple task.
# Be able to adapt the plan as the requirements change.
# Be able to provide effective mock-ups and trial programs for clients.

At the intermediate level the Programming and Software Development category includes greater in depth knowledge of the basic LSL commands. At this level the person should know how to use all of the flow commands and construct a wide variety of scripts that require all of the flow commands.

In addition, the person should know and understand how to use all of the list commands. A person should be able to manipulate lists. For example, a person should be able to delete and insert sublists into an existing list. The person should be able to use strided list and know how to sort and randomize a list. The person should also have a basic understanding of the memory overhead associated with a list.

The person should also know and understand all of the string manipulation routines. The person should be able to manipulate strings. For example, a person should be able to delete and insert substrings into an existing string. The person should have a basic understanding of the memory overhead associated with strings.

The person should be able to make use of at least one revision control system. The person should be able to maintain revisions and recall specific revisions. At this level a person does not need to know know how to find differences in revisions or be able to create and maintain a branch and merge the branch into an existing code base.

Finally, a person should understand how to create a broad, flexible plan to create and maintain a software project. The person should understand how the importance of creating a plan and developing an approach to a project before any coding is to begin. The person should understand the importance of flexibility and the importance of long term planning and how it relates to the code base.

SL Cert - Intermediate Scripting

2009-11-30T09:31:36Z

Elendreal Halasy: Minor change to include a recommendation that the user should have a basic understanding of algebraic functions. Especially in regards to physics.

{{SLCert Navbox}}
[[Category:Certification]]

==Overview==

Criteria required for persons to become certified in intermediate scripting.

==Audience==

Persons who wish to demonstrate competence in intermediate LSL scripting.

==Prerequisites==

Applicant must hold basic scripting certification.
(Recommended) An application should have a basic understanding of algebraic functions.

==Criteria for testing to intermediate level==

Scripting includes a wide variety of categories. At the intermediate level the different categories are broken out separately. The different categories are given below with the associated topics. Note that there is some overlap between categories. This is because the different topics can not be easily divided and are related. Some topics may be necessary for multiple categories and are listed multiple times to avoid prerequisite clashes between categories.

=== Primitives, Objects ===

The different ways scripts can manipulate an object is included in this category. It does not include the ways to interact between objects and agents. The interaction categories are included in the detection and communications categories.

* Faces
# Each face on a prim has a number associated with it.
# The number varies by prim type and can vary depending if the prim has a "cut."
# It is not necessary to memorize all of the face numbers for every prim. It is necessary to know how to find the information and understand how the convention depends on whether or not a prim is cut.

* Changing color
# Commands for changing the color
# RGB definition of a color vector in LSL and how it is different from the editor window.
# Know how to convert back and forth between an RGB color vector in LSL and the format found in the editor window.
# Know how to identify when a color is changed using the changed event and the predefined constant CHANGED_COLOR.

* Changing alpha(transparency)
# Commands for changing the alpha level
# Difference between changing alpha level and the two different transparant textures, TEXTURE_TRANSPARENT and e97cf410-8e61-7005-ec06-629eba4cd1fb (invisiprim).
# Know how to identify when an alpha level is changed using the changed event and the predefined constant CHANGED_COLOR.

* Changing textures
# Commands for changing the textures
# Predefined constants for UUIDs of textures
# Know the difference between the constants TEXTURE_TRANSPARENT, TEXTURE_BLANK, TEXTURE_MEDIA, and TEXTURE_PLYWOOD.
# Know how to identify when a texture is changed using the changed event and the predefined constant CHANGED_TEXTURE.

* Particles
# Command to create particles
# basic limitation of particles
# basic understanding on how to turn particles on and turn.

* Link commands and options
# Commands to determine the UUID, link number, total number of prims etc. for prims within the current object.

* Text and pie menu text
# Commands to change the text over a prim.
# Commands to change the text for different options in the pie menu.

* Primitive name and description
# Commands to get the name and description of a prim.
# Commands to change the name and description of a prim.

* Dataserver events
# Basic understanding of the data server event.
# Basic understanding of the different kinds of information that can be obtained using the Dataserver event.

* Obtaining object information
# Getting agent information (llRequestAgentData)
# Getting object information (llGetObjectDetails)

* Sound
# Commands to preload sound files.
# Commands to play sounds.

Note that for many of these items there are a large number of commands asociated with the topic. For example, just to change the color of a prim the following commands can be used: llSetColor, llSetLinkColor, llGetColor, llSetPrimitiveParams, llGetPrimitiveParams, llSetLinkPrimitiveParams. It is adequate for a person to just know how to use llSetPrimitiveParams and llSetLinkPrimitiveParams to change the color of a prim, but the person should know the other commands in case they are asked to adapt another person's code.

=== Avatars and Agents ===

* Sit positions and associated functions
# Setting the position and rotation of a sit position.
# Turning off a sit position after it has been set.
# Know how to set the camera orientation for a sitting avatar.

* Permissions
# Basic understanding of the permissions system.
# Basic understanding of the different types of permissions that may be obtained.
# Know how to obtain permissions and basic understanding when it is required.

* Animations
# Know how to set a the animation of a person sitting on a prim.
# Know how to obtain permission before setting the animation.
# Know how to remove an active animation.

* Camera Controls
# Know how to obtain permission to change the camera orientation.
# Know the basic ways to change the camera. (Static positioning)

* Dataserver
# Know the commands that can be used to obtain information about an agent.
# Know how to obtain agent and avatar information via the data server event.

A person should know the basic ways to manipulate and change an avatar. The person should be able to set and clear sit positions on a prim. The person should be able to set the default camera position for an agent once their avatar is sitting on a prim. The person should know how to find the UUID and link number of an avatar when an agent sits on an object.

A person should demonstrate the basic use of the permission system. This includes the different types of permissions. Also, the person should know under what circumstances the agent is given a dialog to obtain permissions and when the dialog is not provided to the agent. The different permissions are not limited to just animations but include all permissions.

The person should demonstrate a basic understanding of how to change a camera. The person is required to be able to move a camera to look at a specific point but not necessarily calculate specific rotations for a given view. The person should be able to obtain permission to change a camera and know how to change it.

The person should be able to identify all of the options available for the data server event and find a given piece of information. The person should be able to manipulate the information and identify what the information is and any limitations. For example, a query to determine if an agent is online will only determine if the agent is online and has provided permission for the owner of the script to determine if the agent is online.

=== Inventory and Simulator Information ===

* Notecards
# Get the number of lines in a note card.
# Step through and get each line in a note card.
# Know how to stop reading a note card by testing for the EOF constant.

* Detect when the inventory has changed.
* Inventory information
# Get the name of the creator for an object.
# Inventory numbering system.
# Inventory types.
# Inventory Permissions.

* Basic use of the llRequestSimulatorData command.

A person seeking intermediate accreditation for the inventory and simulator information should be able to read the full contents of a note card and perform basic string manipulations to determine and react to the contents on a given line in the note card. The person should be able to read the full contents of the note card using both the number of lines in the card and using the EOF constant.

The person should be able to use the changed event to determine when the inventory has been changed and react accordingly.

The person should be able to get basic information about specific inventory items. The person should know how to search all items in the inventory and search all inventory items of a given type. This implies a basic understanding of how the inventory is numbered in relation to the different types.

=== Intermediate I/0 ===

* Chat commands
# Dialogs
# Limitations of chat commands
# Email

* Text and menu
# Setting text over an object
# Commands to manipulate the pie menu

* Link messages
# The link_message event.
# Sending link messages.
# Limiting link messages to specific prims within a build.

* Basic security
# Relying on arcane channels is not secure.
# Methods to insure a message is coming from an agent/object.
# Basic validation using MD5 and SHA1 hashes

In addition to the basic chat commands and listen event defined in the basic level the person should now be able to perform more advanced interactions including the use of dialogs. Also the person should have a broader understanding of the limitations of chat commands and know how to use the options to share email messages between scripts.

Also, the person should be able to change and manipulate the text over an object as well as remove the text over an object. The various commands to change the text in a pie menu should also be known.

In addition to the chat and listening events the person should also know how to use link messages to communicate between scripts within an object. The person should know all of the options to communicate to specific prims or all of the prims in an object using link messages.

Finally, the person should have a basic understanding of security issues and limitations. The person should be able to identify and check for specific agents as well as check and limit communications for ownership and group identities.

Predefined channels (DEBUG_CHANNEL and PUBLIC_CHANNEL).

=== Physics ===

* Linear and Angular Force
# Commands for Force
# Know the difference between local and global settings.
# Know the difference between linear and angular forces.
* Linear and Angular Impulse
# Commands for Impulse
# Know the difference between local and global settings.
# Know the difference between linear and angular impulse.
* Vehicles
# Know the basic commands and settings to initiate a vehicle.
# Know the basic ideas behind the different options.
# Know the impact of changing the individual parameters.

The person who wants to achieve an intermediate rating for physics should know all of the basic commands for both linear and angular force as well as momentum. The person should know the difference between the local and global settings. The person should know the difference between the the force/torque commands and the impulse commands.

The person should know the relationship between force and impulse. Both are representations of Newton's Second Law where force is the differential form and impulse is the integral form. The person should understand the relationship between force, mass, and acceleration as well as the relationship between impulse and momentum.

The very basic commands of scripting a vehicle should be known. At the intermediate level a person is not expected to be able to create a script for a vehicle but should understand the basic commands necessary for it's functionality and alter an existing vehicle script.

=== Detection ===

* Touch events.
# The three touch events.
# Functions to detect information about who has touched a prim.
# Passing touch information to other prims in a build.

* Collision events
# The three collision events.
# Functions to detect information about what/who took part in the collision.

* Land collision events
# The three land collision events.
# Functions to detect information about what/who took part in the land collision.

* Sensors
# The sensor commands.
# The two sensor related events.
# Limiting the scope of a sensor.
# Limitations of a sensor.

A person who wishes to achieve an intermediate certification in detection should know the different events in which detection is relevant. The person should know how the different detection commands are used within the different events. The person should know be able to construct scripts that make use of the events and detection routines and combine them.

Additionally a person should be able to use sensors to detect a person. The person should know the difference between a repeating and one time sensor. The person should know how to construct scripts that make use of the sensor and no_sensor events. The person should know the limitations of the commands and understand the importance and how to narrowly define a sensor.

=== Programming and Software Development ===

* More advanced use of lists.
# Adding to a list.
# Removing part of a list.
# Inserting into a list.
# Replacing part of a list.
# Finding an item in a list.
* More advanced string functions.
# Removing a substring.
# Replacing a substring.
# Inserting a substring.
# Finding a substring.
* More advanced revision systems.
# Basic understanding and use of at least on revision control system. (ex: RCS, subversion, or git)
# Be able to maintain revisions and find particular revisions using at least one revision control system.
* Workflow
# Demonstrate effective interactions with clients and remain flexible through the entire development cycle.
# Be able to establish a basic plan for the creation of a script that must accomplish multiple task.
# Be able to adapt the plan as the requirements change.
# Be able to provide effective mock-ups and trial programs for clients.

At the intermediate level the Programming and Software Development category includes greater in depth knowledge of the basic LSL commands. At this level the person should know how to use all of the flow commands and construct a wide variety of scripts that require all of the flow commands.

In addition, the person should know and understand how to use all of the list commands. A person should be able to manipulate lists. For example, a person should be able to delete and insert sublists into an existing list. The person should be able to use strided list and know how to sort and randomize a list. The person should also have a basic understanding of the memory overhead associated with a list.

The person should also know and understand all of the string manipulation routines. The person should be able to manipulate strings. For example, a person should be able to delete and insert substrings into an existing string. The person should have a basic understanding of the memory overhead associated with strings.

The person should be able to make use of at least one revision control system. The person should be able to maintain revisions and recall specific revisions. At this level a person does not need to know know how to find differences in revisions or be able to create and maintain a branch and merge the branch into an existing code base.

Finally, a person should understand how to create a broad, flexible plan to create and maintain a software project. The person should understand how the importance of creating a plan and developing an approach to a project before any coding is to begin. The person should understand the importance of flexibility and the importance of long term planning and how it relates to the code base.

SL Certification

2009-11-24T00:31:34Z

Elendreal Halasy:

{{SLCert Navbox}}
[[Category:Certification]]

=SL Certification Project=

==Introduction==

In Second Life, education exists already in the form of many SL Schools. But certification does not yet exist in the form of SL Certifiers. The goal of the SL Certification Project is to create these certifiers.

SL Certification is a task-based approach to identifying those who have attained a given level of proficiency in world in a given knowledge and skills area. '''To become a SL Certification project participant, contact {{User|Orange Planer}} (Leader) or {{User|Glenn Linden}} (Linden Lab Sponsor).'''

==Action Plan==
Test
=== Phase One - Develop Skills Lists ===

# SLCERT team uses VOLUNTEER MODERATORS to maintain:
#* A single '''SCHOOLS LIST''' on the PUBLIC WIKI with links to their information locations showing what they teach
#* Multiple '''SKILLS LISTS''' on the PUBLIC WIKI of what people need to know how to do in multiple categories of SL skills
# The VOLUNTEER MODERATORS keep the lists current
# The SCHOOLS continue to:
#* Teach their classes
#* Remain responsible for their own existing certification programs for now
# RESIDENTS have a choice of where to go to learn the skills
# EVERYONE has the benefit of a shared set of SKILLS LISTS for reference:
#* Individuals have:
#** A checklist for managing their own skills education program
#* Schools have:
#** The opportunity to be known for the classes they already make available
#** The opportunity to offer new classes not yet available
#* Solution Providers have:
#** A checklist for managing their employee skills education programs or checking skills levels of their contractors

=== Phase Two - Develop Skills Tests ===
# SL CERT team uses VOLUNTEER MODERATORS to develop, test, and document:
#* Multiple '''SKILLS TESTS''' on the PUBLIC WIKI of what people need to know, and know how to do, in multiple categories of SL skills
#* BEST BLENDS of test methods including: Written (True/False; Multiple Choice), Performance (Build; Texture; Plan), and Other.

=== Phase Three - Identify Third Party Certification Companies ===
# SLCERT team identifies CANDIDATE THIRD PARTY SKILLS CERTIFICATION COMPANIES
#* Including criteria for ranking and selecting
#* Present their results and recommendations to Linden Lab Sponsor

=== Phase Four - Hire Recommended Certification Company ===

* SL Certification Developers identify and prioritize selection criteria
* Make recommendation to Linden Lab
* Target identifying recommended SL Certifier 2H09

=== Phase Five - Certification in Operation ===
* Linden Lab Sponsor reviews SL Certification Developer recommendations
* Presents plan for Executive Committee discussion, approval, budgeting
* Target 2010 to begin

== Process Guides ==

=== SL Certification Process ===
* [[SL Cert Process Document | How skills lists become skills tests]]

=== Roles Guide ===
* [[SL Certification Roles | Action roles in the SL Certification Project]]

=== Certification Guide ===
* [[SL Cert Guide to Certification Testing | How 3rd party testing companies work]]

=== Wiki Guide ===
* [http://wiki.secondlife.com/wiki/Style_Guide SL KB Style Guide]

=== Skills List Template ===
* [[SL Cert Criteria Template | A template for consistent format of skills list criteria pages.]]

== Company Lists ==

=== Education Companies / Schools ===
:Moderator: {{User|Lady Hathaway}}
* [[List of Second Life Skills Training Schools|SL Cert Schools]]

=== Testing Companies / Certifiers ===
:Moderator: {{User|Orange Planer}}
* [[3rd Party Testing Agencies | SL Cert Certifiers (Candidates)]]

== Skills Lists ==
* In PHASE ONE ACTION PLAN these lists are sorted in the order they were first created.
* In PHASE TWO ACTION PLAN a logical grouping will be added to make subjects easier to find.

=== Land Management ===
:Moderator: {{User|Starglazer Blazer}}
* [[SL Cert - Basic Land Management]]
* [[SL Cert - Intermediate Land Management]]
* [[SL Cert - Advanced Land Management]]

=== Texturing ===
:Moderator: {{User|Alice Klinger}}

* [[SL Cert - Textures Skill Set]]

=== Terraforming ===
:Moderator: {{User|Patrice Cournoyer}}

* [[SL Cert - Terraforming]]
* [[SL Cert - Intermediate Terraforming]]
* [[SL Cert - Advanced Terraforming]]

=== Scripting ===
:Moderator: {{User|Grandma Bates}}

* [[SL Cert - Basic Scripting]]
* [[SL Cert - Intermediate Scripting]]
* [[SL Cert - Advanced Scripting]]
=== Event Hosting ===
:Moderator: {{User|Linda Sautereau}}

* [[SL Cert - Basic Event Hosting]]

=== Machinima ===
:Moderator: {{User|Allison Selene}}

* [[SL Cert - Machinima Skills Set]]

=== Building ===
:Moderator: {{User|Aquarius Paravane}}

* [[SL Cert - Basic Building]]

=== Marketing ===
:Moderator: {{User|Ppmediadev Blinker}}

* [[SL Cert - Basic Marketing]]

=== SL Mentoring ===
:Moderator: {{User|Orange Planer}}

* [[SL Cert - Basic Mentoring]]
* [[SL Cert - Intermediate Mentoring]]
* [[SL Cert - Advanced Mentoring]]

== Skills Tests ==

=== Scripting ===
:Moderator: {{User|Grandma Bates}}

* [[SL Cert - Scripting Test Reviews]]

== Meetings and Notes ==
Certification discussions, hosted by {{User|Orange Planer}} (2009) and {{User|Emily Darrow}} (2008)
* [http://slurl.com/secondlife/SLDEVU/227/73/27 Location (SLDEVU ISLAND)]
* [http://www.spin-stream.com/support/forumdisplay.php?f=90 Minutes (SP COUNCIL FORUM)]

=== 4th Quarter 2008 Accomplishments ===
* Team Leader [[User:Emily Darrow|Emily Darrow]]
* Developed Action Plan
* Schools List Up on Wiki

=== First Quarter 2009 Accomplishments ===
* Team Leader {{User|Orange Planer}}
* Additional Participation Generated by Post on XStreet
* Ten Skills Lists Up on Wiki

=== Second Quarter 2009 Goals ===
* Team Leader {{User|Orange Planer}}
* Continue and Deepen Generation of Skills Lists
* Begin Generation of Skills Tests
* Identify 3rd Party testing companies to be used for certification process

== Overarching Goal ==

SL Certification is a Resident-Managed Project with Linden Lab Sponsorship and Support.

The purpose of the SL Certification Project is to allow individuals to have their Second-Life skills recognized as meeting a set criteria, at various levels of "Basic", "Intermediate," and "Advanced"

A list of certified people will then be maintained and made available to those requesting a service.

To assist residents in achieving these levels, schools will educate those interested. They will create learning content based on the certification criteria.

Once the process is complete, a list of certified individuals will then be made publically available.

== Immediate Goal ==
* Develop certification criteria for modeling and scripting
** We are looking for members of the Developer, Instructor, and Volunteer communities to work with Lindens in creating the skills list and certification tasks for those skills in Modeling and in Scripting.

==Description==
Linden Lab is supporting the development of certification for the use of key Second Life tools. We’ll begin with in-world building tools and LSL. We believe this will benefit Residents, Developers, and anyone who wishes to use Second Life by clearly identifying both key skills and the holders of those skills. This will also enable the creation of training to build the skills required for certification.
It is Linden Lab's intent to work with an external certification provider to offer certification testing and maintain a list of those Residents who have been certified.

== Linden Participants ==
* {{User|Glenn Linden}}

== [[:Category:SL Certification Participant|Resident Participants]] ==
{{:Category:SL Certification Participant}}

== Certification Mailing List ==
https://lists.secondlife.com/cgi-bin/mailman/listinfo/slcertification

== SL Certification Group ==
SL Certification Devs - request membership from {{User|Glenn Linden}} or {{User|Orange Planer}} in world. Membership is open to anyone who requests it. Meetings are announced here.

== Frequently Asked Questions ==
=== What is the value of Certification? ===
The primary value of certification is to those hiring people to create content for them in SL. Certification is one indication that someone has at least a minimum set of skills. Certification is only one of many ways to demonstrate competency. Certification also clarifies skills and helps instructors develop instruction.

Certification also provides a set of skills against which anyone in Second Life, whether they build for fun or for hire, can measure their accomplishments.

By more clearly defining skills related to Second Life tools, certification may improve the quality of construction in Second Life, and may encourage a broader range of instruction about the Second Life tools.

=== Portfolios already show if someone is competent; why do we need certification? ===
Portfolios have a valuable role in demonstrating accomplishment, both in RL and SL. In Second Life, many projects are done collaboratively. Builds can incorporate content that is bought and created, and many people can be involved. It can be hard to look at a project and understand what a particular person has contributed. Certification provides one method of demonstrating your own skill set. It should be only one of many potential ways to evaluate a candidate.

=== Is Linden Lab mandating certification? ===
You can chose to be certified if you want, or not. Linden Lab has no intent to monitor or mandate that Second Life content be created only by Residents with certification, or to mandate certification in any way. Nor will Certification (or non-certification) be tied by Linden Lab in any way to land ownership, group membership, membership level, or any other attribute of a Second Life account. While Linden Lab may provide a way for those listed in the Developer Directory to identify certification, it will not require it for the Developer Directory, Classifieds, Events, or any other Linden Lab-operated listing service.

=== Is Linden Lab mandating content of certification? ===
Linden Lab has engaged the Residents in defining the skills involved in competency, and in developing the appropriate demonstration of those skills. Linden Lab is not defining the skills nor the demonstration of them, it is simply supporting the process.

=== Will it cost money? Does Linden Lab intend to profit by Certification? ===
Linden Lab was looking to have a third party organization manage certification; we don't want the administrative hassle of doing it, nor the potential for anyone to claim that we would have influence on who gets certified. We intend to make certification as widely available as possible. We will work with Residents, Instructors and Developers to find the best way to enable certification.

=== Who will be providing the Certification service? ===
At this time, the only answer we can give is "Not Linden Lab." We will work with the Residents who participate in developing certification to find the best provider - whether a Resident, an external third party, or some other provider. Ironically, our original reason for only considering an external provider was to prevent any concern that one group of Residents might use Certification against other Residents. Linden Lab has no intent of operating the Certification service - we don't have the expertise or resources, nor do we want the inevitable accusations of bias.

=== Will certification make it harder to become competent in using Second Life tools? ===
Certification is a way to more clearly communicate skills. Without certification, everyone has their own idea of what competency is. Some classes will teach one set of skills, others another, and outcomes aren't comparable. That's why we're involving SL instructors in this project.
Learning to use SL Tools will still take the same amount of effort. Certification will help guide builders and scripters in what they ought to learn in order to achieve particular measurable standards.

=== How will information on who is certified by made available? ===
The Residents involved in developing certification will help us determine the most effective way to list who is certified.

=== Can we do certification in Second Life? ===
At least one Resident has started building a set of in-world tasks that could become part of a certification system. This seems preferable to having external tests/tasks.

== Certification Categories ==
Categories for certification will be varied, and will grow over time.
The basic principal behind the certification process is to provide as wide an array of subjects as possible, and involve residents with skills in these areas.

Currently the following categories are being developed:
* Graphic Design
* Machinima
* Client Interaction
* Building
* Land Management
* Terraforming
* Event Hosting
* Scripting
* Mentoring

By the end of February 09 we hope to have a framework of skill-sets which will then form the basis to develop learning materials.

== Previous Attempt at Categorization ==
An initial attempt at the SL Certification project began in the second quarter of 2007. Included below is an initial attempt at categorizing Modelling and Scripting skills (further works and discussion can be seen on the [[ModelingSkills|List of Modeling Skills]] and [[Scripting Certification|Scripting]] pages). The current work on skill categorization can be found in [[#Skills Lists|Skills Lists]] above.

=== [[Modeling Certification|Modeling]] ===
[[ModelingSkills|List of Modeling Skills]]
* Architecture
* Furnishings/Interior Design
* Objects
* Weapons and Vehicles
Note: Includes using scripts to animate objects and textures but no writing of scripts

=== [[Scripting Certification|Scripting]] ===
* Animation
** Note: Animation includes object animation, texture animation and particle systems
* Attachments
* Movement
* Physics & Collisions
* Detection & Sensing
* Asset Management
* Setting Properties
* Communications
* Interacting with external data stores & web content
* Media Management

Alternative Method:

* Dynamic Objects - manipulation of objects
** Subcategory: Physics and movement in 3-D space
** Subcategory: Primitive Attributes
* User interaction
** Subcategory: User input and communication
** Subcategory: Event handling
* Web interface
** HTML, XML/RPC, and any knowledge of web languages - Perl, Python, PHP, Java, etc

[[Category:Skills]]