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

: ''SLCertification is a community project guided by Linden Lab (see [[SL_Certification#Frequently_Asked_Questions|FAQ]]). This project page and its contents are not endorsed, managed or supervised by Linden Lab. Linden Lab may link to this resource in the future solely as an informational service to the Second Life community.''

==Overview==

This list of requirements is part of the [[SL Certification | Second Life Certification]] project. It is an effort to create a list of specific skills required for persons to become certified in basic scripting.

==Audience==

Persons who wish to demonstrate competence in basic LSL scripting.

==Prerequisites==

Some experience and familiarity of the second life graphical user interface and controls is necessary. Also some experience of building within second life would be an advantage. Six months secondlife experience recommended.

==Criteria for testing to basic level==

In the basic skill sets a person should demonstrate a mastery of common programming tasks. The focus here is not on the use of the Linden Labs library but on basic programming and the fundamental LSL commands for the control and flow of a program. The following categories provide the basic categories.

=== Broad Overview and Most Basic Skills ===

* Rationale for scripting
* Script creation
* Commenting and Clarity
* Mono vs. LSL2
* Software Development
* Using Resources

A person should provide a basic understanding of the potential and the limitations of scripts. The person should be able to demonstrate how to create a script both within an object rezzed in world or in their inventory. The person should know the difference between mono and LSL2 and the implications when a script is created within inventory as opposed to an object's inventory. A person should demonstrate a basic understanding of the construction of consistent, structured code and consistent commenting style.

The person should demonstrate an understanding of the difference between server side lag, client side lag, and the script delays associated with different LSL library calls. The person does not need to memorize which function calls have a delay and how much the delay is, but they need to understand what a delay is and how to determine if a given function has a delay and how long the delay is.

The person should also provide a very basic understanding of practices for good software development. This includes the use and maintenance of comments and the rationale for the use of functions and subroutines. Additionally, the person should provide a rudimentary understanding of code revisioning and practices to keep and maintain local back up files.

Finally, the person should demonstrate an awareness of the various resources available to help with programming in LSL. The person should demonstrate that they know how to use the LSL Portal ([http://wiki.secondlife.com/wiki/LSL_Portal]). The person should demonstrate how to use a search engine to obtain help and information about LSL.

=== Data Types ===

* Types
* Operators
* Global vs. Local Variables
* Typecasting

A person should be able to identify the basic data types, integer, float, string, key, list, vector and rotation. The person should know the basic operations and what they mean in context. For example, division with integers is different compared to division with floats. The person should understand that some operations are overloaded and have different meanings when combined with different types. For example, if v1 and v2 are vectors then v1*v2 is the dot product, but if v1 is a vector and r is a rotation then v1*r will rotate the vector.

The person should demonstrate the concept of the "scope" of a variable. There is a difference if it is defined outside of an event or function. Also, the person should demonstrate an understanding that a global variable can be ignored if it is also defined locally.

Finally, the person should demonstrate how to "convert" one variable into another and what happens. For example, a float is truncated when cast as an integer.

==== String ====

At the basic level the person should demonstrate an understanding of the string data type. The person should know the memory costs and how it differs from LSL1 and mono. The person should know the difference between UTF-8 and UTF-16. The person should know how to define strings and use escape codes to construct non-trivial strings.

The person should know the basic operations defined for strings. This does not include the LSL library functions for the basic level, but the person should demonstrate an understanding of the assignment and comparison of strings.

==== List ====

At the basic level the person only requires minimal understanding. The person is required to know and be able to use the various library functions at the intermediate level, but at the basic level the person need only know the more basic aspects of lists.

The person should demonstrate an understanding of how to assign lists. The person should know the basic memory costs for using a list and know the basic restrictions, such as a list element cannot be a list.

The person should know how to concatenate two lists. The person should know how to clear a list. The person should be able to demonstrate a basic understanding of the idea behind a "strided" list and the importance of being able to group certain elements of a list and maintain their relative positioning within a list.

==== key ====

At the basic level the person should be able to assign a key, know the memory costs, and have a basic idea of what a key is. The person should be able to demonstrate how to assign a key and how to compare keys.

Additionally, the person should know about the predefined variables such as NULL_KEY, TEXTURE_BLANK, TEXTURE_MEDIA, TEXTURE_DEFAULT, TEXTURE_PLYWOOD, and TEXTURE_TRANSPARANT.

==== Math Functions ====

At the basic level the person should demonstrate an understanding of the difference between variables of type integer and float and the operators for each type. The person should also be able to demonstrate an understanding of the various boolean operations and how they differ from the integer operations.

===== Integer Functions =====

The person should be able to demonstrate a knowledge and an understanding of the basic operations. This includes the operations given at [http://wiki.secondlife.com/wiki/LSL_Operators]. This includes the basic operations, modulus operation, and various assignment operators.

This also includes the bit-wise operations. The person should be able to represent an integer in decimal, binary, and hexadecimal forms. Given a number in any of the forms the person should be able to demonstrate an understanding of each of the bit-wise operations and combinations of the bit-wise operations.

The person should also demonstrate an understanding of how to cast a variable from integer to other types and vice-versa. The person should know the difference between truncation and rounding (including rounding up and rounding down in consistent ways with both positive and negative floating point numbers). The person should demonstrate how to round and how to truncate using only the basic operations and casting numbers.

===== Floating Point Operations =====

In addition to the operations in the context of integers the person should also demonstrate an understanding of floating point numbers. This includes an understanding of the basic operations, but also includes the issues of rounding errors versus truncation errors in the context of floating point numbers. This also includes issues of the accumulation of errors which can lead to phenomena such as "prim drift."

=== Control Structures ===

* Loop Constructs
* Conditionals

A person should demonstrate an understanding of the different looping constructs using for, while, and do-while loops and understand when one loop construct might be favored over another in a given context. The person should also demonstrate an understanding of the "if" statement and be able to use compound and nested if statements.

The person should be able to demonstrate the ability to construct complex boolean expressions. For example, they should be able to make use of multiple boolean statements using the boolean "or," boolean "not," and boolean "and" to filter nontrivial conditions in a control structure or conditional. The person should demonstrate an understanding of the difference between integer operations such as "xor," "and," "or," and the shift operations as opposed to the similar boolean operations.

=== Events and Functions ===

* Events
* Functions
* States

A person should demonstrate the basic idea of an event and how a script might react in various circumstances. For example, the person should have a basic understanding of the three touch events and how they differ. At the basic level the broad categories of events that should be mastered include collision, touch, land collision, state entry/exit, timer, and attach events.

The person should demonstrate an understanding of the use and creation of their own functions. This includes understanding the difference between null functions and functions that return a specific data type. The person should know the difference between a user defined function and the set of functions available within the build in library.

Finally, the person should demonstrate an understanding of the use of states. They should understand the default state, how to define new states, and move between different states. The person should have a firm understanding of the control flow as a script moves between different states.

=== Rotations and Vectors ===

In the basic skill sets a person should be able to demonstrate that they understand the basic definitions. The person should also be able to demonstrate that they understand the basic idea. For example, a person should know how to calculate a dot product but also understand its relationship to the idea of a projection of one vector on to another.

==== Basic definition of position ====

* Global position
* Absolute position (within a sim)
* Local position

A person should know what position is in the context of SL. This means the person should know the difference between a global coordinate, an absolute position within a sim, and the local position within a link set. An understanding of the different contexts when you might use local versus absolute is vital to working with rotations and vectors. For example, when working within a link set a local coordinate system is used. At the same time it is not uncommon to make use of local offsets when dealing with two separate objects.

==== Basic definition of a rotation ====
* Euler
* Axis and angle
* Quaternions

A person should demonstrate that they know the definitions of a rotation. The person should know the difference between an Euler rotation and a quaternion. A person need not know the specific implementation of a quaternion but should understand a rotation in terms of an axis of rotation and an angle around that axis.

==== Changing position and rotation via the edit window ====

A person should be proficient using the edit window to manually move and rotate an object. The person should be able to move and rotate an object to a specific orientation (position and rotation). Also, the person should be able to read the position and rotation for a given object using the edit window.

==== Vectors and Operations ====

* Definition of vector in LSL
* Working with vector components (x, y, and z)
* Linear combinations of vectors
* Dot product
* Cross product
* Unit vectors

A person should know the basic mathematical vector operations. The person should know how the calculations are performed and the LSL overloaded operators. For example, given two vectors u and v, the person should know how to calculate the dot product and also know that in LSL u*v will give you the dot product. The person should know how to multiply a scalar and a vector in LSL as well as find linear combinations of vectors in LSL.

=== Basic I/0 ===

* llWhisper
* llSay
* llShout
* llRegionSay
* llOwnerSay
* llInstantMessage

A person should know the basic ways to communicate information in LSL. The person should know the limitations and advantages of each command. The person should know the predefined channels for open chat and debug messages and also know the range of possible channels. The person should know the differences between using a positive number and negative number for the channel number and the relative advantages.

At the basic level a person should know how to open a channel for listening and construct a listening event. The person should understand the importance of being able to close a listening event. For example, the person should know how to use a timer to insure that an open listener will be closed within a given time frame.

At the basic level a person should also have a rudimentary understanding of the string functions. The person should be able to make direct comparisons and also be able to manipulate substrings. Additionally a person should be able to trim spaces off of the beginning and end of a string as well as convert the case to all upper or all lower.

=== Programming and Software Development ===

The person should demonstrate basic skills in maintaining and updating a code base. The names of the scripts should indicate what they do and be consistent for a project. Backups of the codes should be maintained, and the person should be able to demonstrate that they can compare and find the difference between files.

Most importantly the person should demonstrate consistent habits in commenting a script. Scripts should include comments that indicate what they do and how the programmer accomplishes each task within a script. Every event and subroutine also includes a block of comments to indicate which tasks it is used to complete.

We do not specify which commenting style should be used, but the style should be consistent. The person should be familiar with using both the "//" and "/* ---- */" notations for creating comments. Codes that are submitted for the practicum will be evaluated for commenting as well as for function.

SL Cert - Basic Scripting

2010-08-25T10:05:29Z

Grandma Bates: /* List = */

SL Cert - Advanced Scripting

2010-08-21T21:50:52Z

Grandma Bates:

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

: ''SLCertification is a community project guided by Linden Lab (see [[SL_Certification#Frequently_Asked_Questions|FAQ]]). This project page and its contents are not endorsed, managed or supervised by Linden Lab. Linden Lab may link to this resource in the future solely as an informational service to the Second Life community.''

==Overview==

Criteria required for persons to become certified in advanced scripting.

==Audience==

Persons who wish to demonstrate competence in advanced LSL scripting.

==Prerequisites==

Applicant must hold intermediate scripting certification in the specific area.

==Criteria for testing to advanced level==

Scripting includes a wide variety of categories. At the intermediate and advanced 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.

The understanding and knowledge of any one command is similar to that required at the intermediate level. The primary difference is that at the advanced level a person must understand and know how to bring together a wide variety of different categories available to accomplish sophisticated tasks. For example, a person should know how to read a note card and interact with a person and then change a particular prim in an object based on that interaction.

=== Primitives, Objects ===

At the advanced level the person should be aware of all the different ways that a prim can be altered using LSL. This includes all of the methods listed at the intermediate level. The person should demonstrate knowledge of how to change multiple properties of any prim in a linkset in one command. The person should be able to bring together more complex calculations with respect to the various commands. For example, the person should be able to convert between RGB and HSV colors. Another example is the person should be able to construct scripts that automatically scale and position textures to achieve complex effects such as using multiple prims to display one large texture.

The person should also be able to demonstrate an understanding of issues related to lag and script delay. For example, the person should be able to predict potential problems with a particle command and how it relates to client side performance of people viewing the object.

Additionally a person should be able to combine a wide variety of other techniques to manipulate and change the prims within an object to a predetermined state. For example, the person should be able to read the contents of a notecard and interact with an agent using the dialog, chat, and instant message commands to determine how a prim should appear and then change the appearance of the particular prim. The person should also be able to use the link detection commands to determine which prim to change in an object.

The person should be able to go beyond an understanding of the commands and know how to achieve specific objectives. For example, the person should know how to use the llSitTarget command to have an avatar moved and rotated so that they will be looking at a specific location from a predefined distance. This requires that the person not only know how to use the llSitTarget command but also have a basic understanding of calculations of relative positions and rotations.

At the advanced level a person should also have a detailed understanding of what aspects of a prim are persistent properties and how to clear properties. For example, a person should know that text over an object is a property of the prim and know how to clear the text.

=== Avatars and Agents ===

At the advanced level the person should be able to use all of the different commands to obtain information about an avatar or agent. This includes obtaining information about attachments and the related attachment events. The person should be able to use these methods along with other techniques in nontrivial ways.

For example, a person should be able to detect when an object is attached and based on the attachment point move and rotate the object. (Note that this implies that an understanding of how rotations and offsets are changed in the context of attachments and can adjust scripts accordingly.) Scripts should be able to interact with the agent using dialogs and chat commands to change and adapt based on the agents responses. Such interactions may require the use of the various data server commands and react according to the information obtained through the data server event.

Additionally, the person must know how to use a single script to obtain multiple permissions from more than one avatar. For example, the person must demonstrate how to animate more than one avatar using a list of agents and maintaining that list and requesting different permissions as is necessary.

The person should be able to apply fine changes to the agents camera. For example, the person should be able to move a person's camera to a specific location and look at the position from a predefined orientation.

A person seeking certification at the advanced level in this category must have a detailed understanding of permissions and controls and know how to use them in context. The person should be able to assemble scripts that can use the control system to get input from a person through their viewer and then relinquish the control in an appropriate way. The person should be able to do this in conjunction with the permissions system to animate or move an avatar and attachments on an avatar.

=== Inventory and Simulator Information ===

At the advanced level a person should know how to use all of the basic commands. At this level is also vital that the person be able to seamlessly make use of these tools to complete complex tasks. For example, the person should be able to use the various communication techniques to determine which inventory to share with a person based on the creator of the object and a set of permissions based on groups or other limitations defined in a note card.

The person should be able to determine advanced information about the terrain at a given point and react accordingly. For example, the person should be able to make use of the ground normal at a point and have an object moved in an appropriate way based on the ground normal. Also, the person should be able to determine the ownership and restrictions on a given parcel and have the script react in appropriate ways and communicate with an agent to determine how to react.

At the advanced level a person should be able to obtain information about the ownership and settings for a given parcel. The person should be able to have the script react in appropriate ways with respect to the parcel settings. The person should be able to obtain the information for different parcels in any given relative position from the object containing the script. For example, at the advanced level the person should be able to construct a script that can map out all of the parcels and their respective properties in predetermined arc away from the object containing the script without moving the object.

=== Advanced I/0 ===

* HTTP - in
# Creating an HTTP server
# Reacting to errors in the set up
# Reacting to changes to the server
# Reacting to outside requests

* HTTP - out
# Sending communications out to other http servers
# reacting to errors
# Writing flexible scripts that can adapt to server outages and other potential failures.

* Shared Media
# Interacting with forms and outside servers.
# Interacting with forms specified data:urls and sending information back to the same script via HTTP-in.

* Communication with outside servers.
# Difference between POST and Get for HTTP forms.
# At least one scripting language for obtaining information from an in-world script.
# Demonstrate at least one way to reliably retain information from an in-world script and relay it back to another in-world script.

At the advanced level for communications a person should be able to combine the different communication techniques to complete complex operations. For example, the person should be able to combine the use of dialogs and chat commands to send information to different scripts in various prims in an object using the link message system and a single script that interacts with an agent.

In addition to combining communication routines the person should be able to communicate between different objects in world using the http-in and http-out systems. The person should demonstrate scripts that have the flexibility to handle errors in the set up of the http routines and demonstrate flexibility in handling situations impact the http system. For example, the person should be able to develop systems of scripts that can maintain communication in the presence of sim crossings and resets.

The person should be able to demonstrate that they can establish secure and trusted relationships between separate objects that communicate in world. For example, the person should be able to demonstrate efficient techniques for a child object to establish a trusted connection with the object that rezzed it. The person should also demonstrate that they can establish secure and trusted connections between different objects that are not owned by the same person. For example, they should be able to demonstrate that they can verify that an object owned by another person and in a different group is a trusted object and share information with that object in a secure manner.

Finally the person should demonstrate that they can communicate with outside servers and provide persistant data sources. The person must show basic proficiency in at least one other scripting language such as php, python, perl, or other relevant language. They should also demonstrate a basic profiency in connecting with a database and manipulating the database.

=== Physics ===

At the advanced level for physics a person should know the difference between the linear and rotational commands for force and impulse. The person should understand the impulse momentum theorem and the differential form of Newton's Second Law. The person should know how to put the rotational and linear forms of the commands together to achieve specific objectives.

For example, a person should be able to use the physics commands to move an object to a specific location and keep it in a specific orientation. The person should be able to combine different categories in order to move the object. For example, the person should be able to use a sensor or a timer to have a physical object follow an agent and maintain a specific rotation.

Finally, a person should be able to calculate the moment of inertia for simple objects and combinations of simple objects. The person should demonstrate that they know how to use this understanding when using the rotational commands for angular impulse and torque.

=== Vehicles ===

At the advanced level a person should be able to construct a vehicle. A person should be able to construct a variety of vehicles and know the differences between them. For example, the person should be able to construct a boat, car, or plane. They should be able to use the permissions system to have a person control the vehicle in nontrivial ways.

=== Detection ===

At the advanced level a person should be able to put together complex systems of scripts using a variety of detection methods. The person should be able to use these methods to interact with a person and react in non-trivial ways. For example, a person should be able to create scripts that can detect which prim a person has touched or collided with and then interact with the person using the various communication methods.

The person should also have an advanced understanding of the sensor system. For example, the person should know what happens when you try to combine different sensor types by using binary "or" and how that changes the results that a sensor will return. Also, the person should be able to use sensors along with other techniques to interact with agents in nontrivial ways. For example, a person should be able to use a sensor to detect an agent and then alter the sensor based on interaction through dialogs and chat commands, or be able to use sensors to identify and object and then use commands such as llGetObjectPrimCount or the data server commands to obtain other information.

Finally, the person should be able to identify potential server side impacts with the use of the various routines. For example, the person should be able to use detection routines that allow complicated interaction between different prims in an object using only one script and identify the server side impact of using more than one script. Also, the person should be able to identify schemes to minimize the use of sensors and avoid the use of sensors using other commands such as llGetObjectDetails and a timer as a way to avoid potential server side impacts.

=== Rotations and Vectors ===

A set of sample scripts for the advanced level rotations and vectors category can be found at http://slurl.com/secondlife/Hotspur/45/59/30 .

==== Rotations and position ====
* using llSetPrimitiveParams to move and rotate at the same time
* Rotating and moving a prim to a specified orientation
** Absolute coordinates
** Relative coordinates (in a link set)

The person should be able to move and rotate an object with a single command, llSetPrimitiveParams. The person should be able to move an object to a specified rotation and position. Moreover, the person should be able to combine multiple tasks from the intermediate section to move an object to a variety of orientations. For example, given a sequence of points in either local or absolute coordinates the person should be able to move and rotate an object to move along the points so that the objects orientation is consistent with the movement (i.e. it points along the path).

==== Smooth movements ====

===== Absolute coordinates =====
* Rotate and movement around the edge of a prim
* Rotate and move around a fixed point using a predefined axis

The person should be able to calculate and move an object so that it appears to rotate in a uniform way. The person should be able to do this around one edge of the object to make it appear to move in a uniform circular motion. For example, the person should be able to move an uncut prim like a door around an edge. The person should be able to do this around any arbitrary point. The person should also be able to rotate and move and object around any arbitrary axis as well.

===== Local coordinates (within a linkset) =====
* Rotate and movement around the edge of a prim
* Rotate and move around a fixed point using a predefined axis

This is the same as the previous tasks only in a relative coordinate system.

==== Transitions ====
* Smooth movements from one orientation (position and rotation) to another.

Given an initial and final orientation (position and rotation) the person should be able to move the object in a sequence of discrete points so that it appears to move smoothly from the initial to the final orientation.

==== Determining specific orientations ====

===== Absolute/Sim coordinates =====
* Given a point rotate an object to face the point.
* Given two points and the current position rotate an object to face perpindicular to the two points.

This is similar to the Intermediate requirements. The difference here is that the movement from one orientation to another should be done in a number of steps to appear like a smoother movement. Also, the object should point in the specified direction but should maintain some sort of orientation. For example, the person should have one face of a box point toward a given location, but an arbitrary face should be pointing in an "upward" direction.

===== Local coordinates to local =====
* Given a point rotate an object to face a local point.
* Given two points and the current position rotate an object to face perpindicular to the two points.

Similar to the previous task, but the objects should both be in the same local context.

===== Local coordinates to absolute =====
* Given a point rotate an object to face a point in absolute/sim coordinates.
* Given two points and the current position rotate an object to face perpindicular to the two points.

Same as the previous task, but in this case one object should be in a local context and the other in a global context. For example, one prim in a linkset should be moved to face an object moving in a sim's global coordinate system.

=== Programming and Software Development ===

* More advanced use of lists and data types.
# Multiple Data Types
# Using strided lists with multiple data types
# Manipulating all data types
* Advanced revision systems.
# Branching and merging revisions.
# Tagged revisions.
# Finding and using differences between revisions
* Workflow
# Demonstrate effective interactions with clients and remain flexible through the entire development cycle.
# Establishing a plan for systems of scripts and carrying it out.
# Be able to adapt the plan as the requirements change.
# Be able to establish time lines and effectively communicate them with clients.

At the advanced level a person should be familiar with all data
types. The person should know when to use a given a data type and when
it is appropriate. The person should be able to use the most advanced
features of lists and work with strided lists that contain a variety
of data types. The person should be able to use the list functions to
determine the data type for an entry in the list.

A person should be able to use the more advanced features of a
software revision system. The person should know when it is
appropriate to create a branch and know how to create a branch. The
person should know how to merge a branch back into an established
trunk. The person should also know what a tagged release is and how to
create a tagged release in the revision software that they are using.

A person should be able to create plans for creating systems of
scripts. The person should be able to demonstrate that they can
establish a time line for a project and determine a set of
intermediate steps necessary in order to complete a project. The
person should demonstrate an ability to communicate the time line and
the reasons for their decisions with a client. Finally, the person
should demonstrate an ability to adapt and change a timeline as the
client changes the requirements. As part of this aspect the person
should demonstrate that they can anticipate potential problems with a
given set of requirements and work with a client in advance to avoid
potential problems.

SL Cert - Advanced Scripting

2010-08-21T21:47:33Z

Grandma Bates:

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

: ''SLCertification is a community project guided by Linden Lab (see [[SL_Certification#Frequently_Asked_Questions|FAQ]]). This project page and its contents are not endorsed, managed or supervised by Linden Lab. Linden Lab may link to this resource in the future solely as an informational service to the Second Life community.''

==Overview==

Criteria required for persons to become certified in advanced scripting.

==Audience==

Persons who wish to demonstrate competence in advanced LSL scripting.

==Prerequisites==

Applicant must hold intermediate scripting certification in the specific area.

==Criteria for testing to advanced level==

Scripting includes a wide variety of categories. At the intermediate and advanced 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.

The understanding and knowledge of any one command is similar to that required at the intermediate level. The primary difference is that at the advanced level a person must understand and know how to bring together a wide variety of different categories available to accomplish sophisticated tasks. For example, a person should know how to read a note card and interact with a person and then change a particular prim in an object based on that interaction.

=== Primitives, Objects ===

At the advanced level the person should be aware of all the different ways that a prim can be altered using LSL. This includes all of the methods listed at the intermediate level. The person should demonstrate knowledge of how to change multiple properties of any prim in a linkset in one command. The person should be able to bring together more complex calculations with respect to the various commands. For example, the person should be able to convert between RGB and HSV colors. Another example is the person should be able to construct scripts that automatically scale and position textures to achieve complex effects such as using multiple prims to display one large texture.

The person should also be able to demonstrate an understanding of issues related to lag and script delay. For example, the person should be able to predict potential problems with a particle command and how it relates to client side performance of people viewing the object.

Additionally a person should be able to combine a wide variety of other techniques to manipulate and change the prims within an object to a predetermined state. For example, the person should be able to read the contents of a notecard and interact with an agent using the dialog, chat, and instant message commands to determine how a prim should appear and then change the appearance of the particular prim. The person should also be able to use the link detection commands to determine which prim to change in an object.

The person should be able to go beyond an understanding of the commands and know how to achieve specific objectives. For example, the person should know how to use the llSitTarget command to have an avatar moved and rotated so that they will be looking at a specific location from a predefined distance. This requires that the person not only know how to use the llSitTarget command but also have a basic understanding of calculations of relative positions and rotations.

At the advanced level a person should also have a detailed understanding of what aspects of a prim are persistent properties and how to clear properties. For example, a person should know that text over an object is a property of the prim and know how to clear the text.

=== Avatars and Agents ===

At the advanced level the person should be able to use all of the different commands to obtain information about an avatar or agent. This includes obtaining information about attachments and the related attachment events. The person should be able to use these methods along with other techniques in nontrivial ways.

For example, a person should be able to detect when an object is attached and based on the attachment point move and rotate the object. (Note that this implies that an understanding of how rotations and offsets are changed in the context of attachments and can adjust scripts accordingly.) Scripts should be able to interact with the agent using dialogs and chat commands to change and adapt based on the agents responses. Such interactions may require the use of the various data server commands and react according to the information obtained through the data server event.

Additionally, the person must know how to use a single script to obtain multiple permissions from more than one avatar. For example, the person must demonstrate how to animate more than one avatar using a list of agents and maintaining that list and requesting different permissions as is necessary.

The person should be able to apply fine changes to the agents camera. For example, the person should be able to move a person's camera to a specific location and look at the position from a predefined orientation.

A person seeking certification at the advanced level in this category must have a detailed understanding of permissions and controls and know how to use them in context. The person should be able to assemble scripts that can use the control system to get input from a person through their viewer and then relinquish the control in an appropriate way. The person should be able to do this in conjunction with the permissions system to animate or move an avatar and attachments on an avatar.

=== Inventory and Simulator Information ===

At the advanced level a person should know how to use all of the basic commands. At this level is also vital that the person be able to seamlessly make use of these tools to complete complex tasks. For example, the person should be able to use the various communication techniques to determine which inventory to share with a person based on the creator of the object and a set of permissions based on groups or other limitations defined in a note card.

The person should be able to determine advanced information about the terrain at a given point and react accordingly. For example, the person should be able to make use of the ground normal at a point and have an object moved in an appropriate way based on the ground normal. Also, the person should be able to determine the ownership and restrictions on a given parcel and have the script react in appropriate ways and communicate with an agent to determine how to react.

At the advanced level a person should be able to obtain information about the ownership and settings for a given parcel. The person should be able to have the script react in appropriate ways with respect to the parcel settings. The person should be able to obtain the information for different parcels in any given relative position from the object containing the script. For example, at the advanced level the person should be able to construct a script that can map out all of the parcels and their respective properties in predetermined arc away from the object containing the script without moving the object.

=== Advanced I/0 ===

* HTTP - in
# Creating an HTTP server
# Reacting to errors in the set up
# Reacting to changes to the server
# Reacting to outside requests

* HTTP - out
# Sending communications out to other http servers
# reacting to errors
# Writing flexible scripts that can adapt to server outages and other potential failures.

* Shared Media
# Interacting with forms and outside servers.
# Interacting with forms specified data:urls and sending information back to the same script via HTTP-in.

* Communication with outside servers.

At the advanced level for communications a person should be able to combine the different communication techniques to complete complex operations. For example, the person should be able to combine the use of dialogs and chat commands to send information to different scripts in various prims in an object using the link message system and a single script that interacts with an agent.

In addition to combining communication routines the person should be able to communicate between different objects in world using the http-in and http-out systems. The person should demonstrate scripts that have the flexibility to handle errors in the set up of the http routines and demonstrate flexibility in handling situations impact the http system. For example, the person should be able to develop systems of scripts that can maintain communication in the presence of sim crossings and resets.

The person should be able to demonstrate that they can establish secure and trusted relationships between separate objects that communicate in world. For example, the person should be able to demonstrate efficient techniques for a child object to establish a trusted connection with the object that rezzed it. The person should also demonstrate that they can establish secure and trusted connections between different objects that are not owned by the same person. For example, they should be able to demonstrate that they can verify that an object owned by another person and in a different group is a trusted object and share information with that object in a secure manner.

Finally the person should demonstrate that they can communicate with outside servers and provide persistant data sources. The person must show basic proficiency in at least one other scripting language such as php, python, perl, or other relevant language. They should also demonstrate a basic profiency in connecting with a database and manipulating the database.

=== Physics ===

At the advanced level for physics a person should know the difference between the linear and rotational commands for force and impulse. The person should understand the impulse momentum theorem and the differential form of Newton's Second Law. The person should know how to put the rotational and linear forms of the commands together to achieve specific objectives.

For example, a person should be able to use the physics commands to move an object to a specific location and keep it in a specific orientation. The person should be able to combine different categories in order to move the object. For example, the person should be able to use a sensor or a timer to have a physical object follow an agent and maintain a specific rotation.

Finally, a person should be able to calculate the moment of inertia for simple objects and combinations of simple objects. The person should demonstrate that they know how to use this understanding when using the rotational commands for angular impulse and torque.

=== Vehicles ===

At the advanced level a person should be able to construct a vehicle. A person should be able to construct a variety of vehicles and know the differences between them. For example, the person should be able to construct a boat, car, or plane. They should be able to use the permissions system to have a person control the vehicle in nontrivial ways.

=== Detection ===

At the advanced level a person should be able to put together complex systems of scripts using a variety of detection methods. The person should be able to use these methods to interact with a person and react in non-trivial ways. For example, a person should be able to create scripts that can detect which prim a person has touched or collided with and then interact with the person using the various communication methods.

The person should also have an advanced understanding of the sensor system. For example, the person should know what happens when you try to combine different sensor types by using binary "or" and how that changes the results that a sensor will return. Also, the person should be able to use sensors along with other techniques to interact with agents in nontrivial ways. For example, a person should be able to use a sensor to detect an agent and then alter the sensor based on interaction through dialogs and chat commands, or be able to use sensors to identify and object and then use commands such as llGetObjectPrimCount or the data server commands to obtain other information.

Finally, the person should be able to identify potential server side impacts with the use of the various routines. For example, the person should be able to use detection routines that allow complicated interaction between different prims in an object using only one script and identify the server side impact of using more than one script. Also, the person should be able to identify schemes to minimize the use of sensors and avoid the use of sensors using other commands such as llGetObjectDetails and a timer as a way to avoid potential server side impacts.

=== Rotations and Vectors ===

A set of sample scripts for the advanced level rotations and vectors category can be found at http://slurl.com/secondlife/Hotspur/45/59/30 .

==== Rotations and position ====
* using llSetPrimitiveParams to move and rotate at the same time
* Rotating and moving a prim to a specified orientation
** Absolute coordinates
** Relative coordinates (in a link set)

The person should be able to move and rotate an object with a single command, llSetPrimitiveParams. The person should be able to move an object to a specified rotation and position. Moreover, the person should be able to combine multiple tasks from the intermediate section to move an object to a variety of orientations. For example, given a sequence of points in either local or absolute coordinates the person should be able to move and rotate an object to move along the points so that the objects orientation is consistent with the movement (i.e. it points along the path).

==== Smooth movements ====

===== Absolute coordinates =====
* Rotate and movement around the edge of a prim
* Rotate and move around a fixed point using a predefined axis

The person should be able to calculate and move an object so that it appears to rotate in a uniform way. The person should be able to do this around one edge of the object to make it appear to move in a uniform circular motion. For example, the person should be able to move an uncut prim like a door around an edge. The person should be able to do this around any arbitrary point. The person should also be able to rotate and move and object around any arbitrary axis as well.

===== Local coordinates (within a linkset) =====
* Rotate and movement around the edge of a prim
* Rotate and move around a fixed point using a predefined axis

This is the same as the previous tasks only in a relative coordinate system.

==== Transitions ====
* Smooth movements from one orientation (position and rotation) to another.

Given an initial and final orientation (position and rotation) the person should be able to move the object in a sequence of discrete points so that it appears to move smoothly from the initial to the final orientation.

==== Determining specific orientations ====

===== Absolute/Sim coordinates =====
* Given a point rotate an object to face the point.
* Given two points and the current position rotate an object to face perpindicular to the two points.

This is similar to the Intermediate requirements. The difference here is that the movement from one orientation to another should be done in a number of steps to appear like a smoother movement. Also, the object should point in the specified direction but should maintain some sort of orientation. For example, the person should have one face of a box point toward a given location, but an arbitrary face should be pointing in an "upward" direction.

===== Local coordinates to local =====
* Given a point rotate an object to face a local point.
* Given two points and the current position rotate an object to face perpindicular to the two points.

Similar to the previous task, but the objects should both be in the same local context.

===== Local coordinates to absolute =====
* Given a point rotate an object to face a point in absolute/sim coordinates.
* Given two points and the current position rotate an object to face perpindicular to the two points.

Same as the previous task, but in this case one object should be in a local context and the other in a global context. For example, one prim in a linkset should be moved to face an object moving in a sim's global coordinate system.

=== Programming and Software Development ===

* More advanced use of lists and data types.
# Multiple Data Types
# Using strided lists with multiple data types
# Manipulating all data types
* Advanced revision systems.
# Branching and merging revisions.
# Tagged revisions.
# Finding and using differences between revisions
* Workflow
# Demonstrate effective interactions with clients and remain flexible through the entire development cycle.
# Establishing a plan for systems of scripts and carrying it out.
# Be able to adapt the plan as the requirements change.
# Be able to establish time lines and effectively communicate them with clients.

At the advanced level a person should be familiar with all data
types. The person should know when to use a given a data type and when
it is appropriate. The person should be able to use the most advanced
features of lists and work with strided lists that contain a variety
of data types. The person should be able to use the list functions to
determine the data type for an entry in the list.

A person should be able to use the more advanced features of a
software revision system. The person should know when it is
appropriate to create a branch and know how to create a branch. The
person should know how to merge a branch back into an established
trunk. The person should also know what a tagged release is and how to
create a tagged release in the revision software that they are using.

A person should be able to create plans for creating systems of
scripts. The person should be able to demonstrate that they can
establish a time line for a project and determine a set of
intermediate steps necessary in order to complete a project. The
person should demonstrate an ability to communicate the time line and
the reasons for their decisions with a client. Finally, the person
should demonstrate an ability to adapt and change a timeline as the
client changes the requirements. As part of this aspect the person
should demonstrate that they can anticipate potential problems with a
given set of requirements and work with a client in advance to avoid
potential problems.

SL Cert - Intermediate Scripting

2010-08-21T21:43:34Z

Grandma Bates:

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

: ''SLCertification is a community project guided by Linden Lab (see [[SL_Certification#Frequently_Asked_Questions|FAQ]]). This project page and its contents are not endorsed, managed or supervised by Linden Lab. Linden Lab may link to this resource in the future solely as an informational service to the Second Life community.''

==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, basic texture certification, and basic building 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 are 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 transparent 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 limitations of particles.
# Basic understanding on how to turn particles on and off.

* 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 dataserver 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 associated 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 dataserver 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 dataserver 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, Land and Simulator Information ===

* Note cards
# 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.

* Land
# Find the water level at a given position
# Find the normal to the terrain at a given position
# Find the slope to the terrain at a given position
# Find the owner of the parcel at a given position
# Use of the llGetParcelDetails command to get parcel information at a certain position.

* 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.

* Shared Media
# Basic use of the llSetPrimMediaParams command to display web pages on a prim.
# Use of data:text/html format to specify web pages.

* 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 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 its 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.

=== Rotations and Vectors ===

For the intermediate requirements a person should be able to take the ideas required for the basic requirements and implement them in LSL. More importantly the person should begin to demonstrate an ability to work with the definitions in specific contexts and solve basic problems using a script.

==== Reference Frames ====
* Global
* Sim
* Local

Similar to the basic requirements, but the person must be able to demonstrate an ability to move back and forth between global, sim, and local coordinates. For example, a script that is in a link set should be able to work with a coordinate passed to it from an object in the sim's reference frame and react accordingly.

==== Basic commands to get position information ====
* llGetPos
* llGetLocalPos
* llGetRootPosition
* llGetRegionCorner

A person must demonstrate an understanding of the basic position commands for getting information about an object's position. The person must demonstrate an understanding how the command works in different global and local contexts.

==== Basic commands to get rotation information ====
* llGetRot
* llGetLocalRot
* llGetRootRotation

A person must demonstrate an understanding of the basic rotation commands for getting information about an object's rotation. The person must demonstrate an understanding how the command works in different global and local contexts.

====Basic commands for changing position ====
* llSetPos
* llSetPrimitiveParams
* llSetPos within different reference frames.

A person must demonstrate a basic understanding of how to move an object. The person should be able to move an object to specific points. This should be done in both local, sim, and global coordinate systems. For example, a person should be able to move a prim within a link set to a specific point in the sim's coordinate system. More importantly given two separate objects the person must be able to move a prim to points in a local context defined by the two objects.

==== Basic commands for changing and working with rotations ====
* llSetRot
* llSetLocalRot
* llSetPrimitiveParams
* llAxes2Rot
* llAxisAngle2Rot
* llRotBetween
* llRot2Axis
* llRot2Angle
* How the commands work in different reference frames.
* Rotations
** Multiplication and division of rotations
** Difference between left and right multiplication

A person must demonstrate a basic understanding of how to rotate an object. The person must be able to rotate an object to specific orientations. This should be done with a variety of different commands. The person should demonstrate an ability to calculate appropriate rotations given a variety of information. For example, the person should be able to calculate the rotation necessary to achieve a given orientation using an Euler rotation as well as making use of an axis of rotation and an angle.

==== Working with vectors ====
* Finding a vector component in a given direction.
* Finding a vector perpendicular to two vectors.
* Finding a vector perpendicular to a plane.

The person should be able to perform basic vector operations in LSL. The person should be able to calculate the components of a vector in arbitrary directions. The person should be able to do this in a variety of contexts such as using a plane or multiple vectors.

=== 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.
* Work flow
# 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

2010-08-21T21:35:50Z

Grandma Bates:

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

: ''SLCertification is a community project guided by Linden Lab (see [[SL_Certification#Frequently_Asked_Questions|FAQ]]). This project page and its contents are not endorsed, managed or supervised by Linden Lab. Linden Lab may link to this resource in the future solely as an informational service to the Second Life community.''

==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, basic texture certification, and basic building 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 are 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 transparent 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 limitations of particles.
# Basic understanding on how to turn particles on and off.

* 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 dataserver 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 associated 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 dataserver 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 dataserver 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, Land and Simulator Information ===

* Note cards
# 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.

* Land
# Find the water level at a given position
# Find the normal to the terrain at a given position
# Find the slope to the terrain at a given position
# Find the owner of the parcel at a given position
# Use of the llGetParcelDetails command to get parcel information at a certain position.

* 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 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 its 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.

=== Rotations and Vectors ===

For the intermediate requirements a person should be able to take the ideas required for the basic requirements and implement them in LSL. More importantly the person should begin to demonstrate an ability to work with the definitions in specific contexts and solve basic problems using a script.

==== Reference Frames ====
* Global
* Sim
* Local

Similar to the basic requirements, but the person must be able to demonstrate an ability to move back and forth between global, sim, and local coordinates. For example, a script that is in a link set should be able to work with a coordinate passed to it from an object in the sim's reference frame and react accordingly.

==== Basic commands to get position information ====
* llGetPos
* llGetLocalPos
* llGetRootPosition
* llGetRegionCorner

A person must demonstrate an understanding of the basic position commands for getting information about an object's position. The person must demonstrate an understanding how the command works in different global and local contexts.

==== Basic commands to get rotation information ====
* llGetRot
* llGetLocalRot
* llGetRootRotation

A person must demonstrate an understanding of the basic rotation commands for getting information about an object's rotation. The person must demonstrate an understanding how the command works in different global and local contexts.

====Basic commands for changing position ====
* llSetPos
* llSetPrimitiveParams
* llSetPos within different reference frames.

A person must demonstrate a basic understanding of how to move an object. The person should be able to move an object to specific points. This should be done in both local, sim, and global coordinate systems. For example, a person should be able to move a prim within a link set to a specific point in the sim's coordinate system. More importantly given two separate objects the person must be able to move a prim to points in a local context defined by the two objects.

==== Basic commands for changing and working with rotations ====
* llSetRot
* llSetLocalRot
* llSetPrimitiveParams
* llAxes2Rot
* llAxisAngle2Rot
* llRotBetween
* llRot2Axis
* llRot2Angle
* How the commands work in different reference frames.
* Rotations
** Multiplication and division of rotations
** Difference between left and right multiplication

A person must demonstrate a basic understanding of how to rotate an object. The person must be able to rotate an object to specific orientations. This should be done with a variety of different commands. The person should demonstrate an ability to calculate appropriate rotations given a variety of information. For example, the person should be able to calculate the rotation necessary to achieve a given orientation using an Euler rotation as well as making use of an axis of rotation and an angle.

==== Working with vectors ====
* Finding a vector component in a given direction.
* Finding a vector perpendicular to two vectors.
* Finding a vector perpendicular to a plane.

The person should be able to perform basic vector operations in LSL. The person should be able to calculate the components of a vector in arbitrary directions. The person should be able to do this in a variety of contexts such as using a plane or multiple vectors.

=== 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.
* Work flow
# 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.

2009-11-27T20:47:36Z

Grandma Bates: /* Avatars and Agents */

SL Cert - Advanced Scripting

2009-11-27T20:45:12Z

Grandma Bates: /* Primitives, Objects */

SL Cert - Basic Scripting

2009-11-26T16:30:41Z

Grandma Bates: /* Control Structures */

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

==Overview==

This list of requirements is part of the [[SL Certification | Second Life Certification]] project. It is an effort to create a list of specific skills required for persons to become certified in basic scripting.

==Audience==

Persons who wish to demonstrate competence in basic LSL scripting.

==Prerequisites==

Some experience and familiarity of the second life graphical user interface and controls is necessary. Also some experience of building within second life would be an advantage. Six months secondlife experience recommended.

==Criteria for testing to basic level==

In the basic skill sets a person should demonstrate a mastery of common programming tasks. The following categories provide the basic categories.

=== Broad Overview and Most Basic Skills ===

* Rationale for scripting
* Script creation
* Commenting and Clarity
* Mono vs. LSL2
* Software Development

A person should provide a basic understanding of the potential and the limitations of scripts. The person should be able to demonstrate how to create a script both within an object rezzed in world or in their inventory. The person should know the difference between mono and LSL2 and the implications when a script is created within inventory as opposed to an object's inventory. A person should demonstrate a basic understanding of the construction of consistent, structured code and consistent commenting style.

The person should demonstrate an understanding of the difference between server side lag, client side lag, and the script delays associated with different LSL library calls. The person does not need to memorize which function calls have a delay and how much the delay is, but they need to understand what a delay is and how to determine if a given function has a delay and how long the delay is.

Finally, the person should provide a very basic understanding of practices for good software development. This includes the use and maintenance of comments and the rationale for the use of functions and subroutines. Additionally, the person should provide a rudimentary understanding of code revisioning and practices to keep and maintain local back up files.

=== Data Types ===

* Types
* Operators
* Global vs. Local Variables
* Typecasting

A person should be able to identify the basic data types, integer, float, string, key, list, vector and rotation. The person should know the basic operations and what they mean in context. For example, division with integers is different compared to division with floats. The person should understand that some operations are overloaded and have different meanings when combined with different types. For example, if v1 and v2 are vectors then v1*v2 is the dot product, but if v1 is a vector and r is a rotation then v1*r will rotate the vector.

The person should demonstrate the concept of the "scope" of a variable. There is a difference if it is defined outside of an event or function. Also, the person should demonstrate an understanding that a global variable can be ignored if it is also defined locally.

Finally, the person should demonstrate how to "convert" one variable into another and what happens. For example, a float is trunctated when cast as an integer.

=== Control Structures ===

* Loop Constructs
* Conditionals

A person should demonstrate an understanding of the different looping constructs using for, while, and do-whole loops and understand when one loop construct might be favored over another in a given context. The person should also demonstrate an understanding of the "if" statement and be able to use compound and nested if statements.

The person should be able to demonstrate the ability to construct complex boolean expressions. For example, they should be able to make use of multiple boolean statements using the boolean "or," boolean "not," and boolean "and" to filter nontrivial conditions in a control structure or conditional. The person should demonstrate an understanding of the difference between integer operations such as "xor," "and," "or," and the shift operations as opposed to the similar boolean operations.

=== Events and Functions ===

* Events
* Functions
* States

A person should demonstrate the basic idea of an event and how a script might react in various circumstances. For example, the person should have a basic understanding of the three touch events and how they differ. At the basic level the broad categories of events that should be mastered include collision, touch, land collision, state entry/exit, timer, and attach events.

The person should demonstrate an understanding of the use and creation of their own functions. This includes understanding the difference between null functions and functions that return a specific data type. The person should know the difference between a user defined function and the set of functions available within the build in library.

Finally, the person should demonstrate an understanding of the use of states. They should understand the default state, how to define new states, and move between different states. The person should have a firm understanding of the control flow as a script moves between different states.

=== Basic I/0 ===

* llWhisper
* llSay
* llShout
* llRegionSay
* llOwnerSay
* llInstantMessage

A person should know the basic ways to communicate information in LSL. The person should know the limitations and advantages of each command. The person should now the predefined channels for open chat and debug messages and also know the range of possible channels. The person should know the differences between using a positive number and negative number for the channel number and the relative advantages.

At the basic level a person should know how to open a channel for listening and construct a listening event. The person should understand the importance of being able to close a listening event. For example, the person should know how to use a timer to insure that an open listener will be closed within a given time frame.

At the basic level a person should also have a rudimentary understanding of the string functions. The person should be able to make direct comparisons and also be able to manipulate substrings. Additionally a person should be able to trim spaces off of the beginning and end of a string as well as convert the case to all upper or all lower.

SL Cert - Basic Scripting

2009-11-26T16:28:16Z

Grandma Bates: /* Broad Overview and Most Basic Skills */

SL Cert - Basic Scripting

2009-11-26T15:33:04Z

Grandma Bates: /* Basic I/0 */

SL Cert - Basic Scripting

2009-11-26T15:32:32Z

Grandma Bates: /* Control Structures */

SL Certification

2009-11-26T15:29:57Z

2009-11-26T13:26:23Z

Grandma Bates: /* Intermediate I/0 */

{{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.

==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
# 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.
# 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 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-26T13:25:40Z

Grandma Bates: /* Programming and Software Development */

{{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.

==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
# 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.
# 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 ===

* Text 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 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-26T13:03:59Z

Grandma Bates: /* Programming and Software Development */

{{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.

==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
# 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.
# 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 ===

* Text 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 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 know how to find differences in revisions and be able to make a branch and merge a branch into an existing code base.

Finally, a person should understand how to create a 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-26T12:56:12Z

Grandma Bates: /* Detection */

{{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.

==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
# 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.
# 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 ===

* Text 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 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.

SL Cert - Intermediate Scripting

2009-11-26T12:52:26Z

Grandma Bates: /* Physics */

SL Cert - Intermediate Scripting

2009-11-26T12:22:18Z

Grandma Bates:

SL Cert - Advanced Scripting

2009-11-26T11:34:56Z

Grandma Bates:

SL Certification

2009-11-26T11:32:50Z

Grandma Bates: /* Scripting */

{{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}}

== 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:
* Land Management
* Texturing
* Terraforming
* Scripting
* Event Hosting
* Machinima
* Building
* Marketing
* SL 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]]

SL Cert - Intermediate Scripting

2009-11-26T11:24:09Z

Grandma Bates: