Difference between revisions of "Scripting Certification"

From Second Life Wiki
Jump to navigation Jump to search
(added some categories)
Line 62: Line 62:
==== {{LSLGC|HTTP}} ====
==== {{LSLGC|HTTP}} ====
==== {{LSLGC|XML-RPC}} ====
==== {{LSLGC|XML-RPC}} ====
== Agent Interaction/UI ==
=== Chat Interfaces ===
=== Touch based UI ===
=== Dialog UI ===
=== Notecard Config ===
== Data Management ==
=== String Parsing ===
=== Manipulating Large Datasets ===


== Media Management ==
== Media Management ==

Revision as of 12:15, 26 April 2007

The holder of a SL Certification has demostrated compency in basic SL User Interface, SL Permissions

This certification exams consisted objective type questions such as true/false or multiple choice questions and simulated labs for examining a candidate's expertise. For this reason, it is essential that those aspiring for SL Scripting certification have sufficient hands-on experience. The majority of questions will require the writing of scripts.

The scripting certification includes:

Certification Topics

Avatar Permissions

Animation

Camera

Controls

Money

Animation

  • This should only be on the mechanics of the scripting, not on the creation of animations (that will likely be it's own certification).

Object animation

Texture animation

Particle systems

Attachments

HUD

Body

Movement

Objects

Linked Prims

Physics & Collisions

Vehicle

Detection & Sensing

Asset Management

Inventory

Asset Permissions

Setting Properties

Communications

User

Interacting with users

Chat

Dialog

Instant Message


Script

Interacting with other scripts

Chat

Link Message

Email


External

Interacting with external data stores & web content

Email

HTTP

XML-RPC

Agent Interaction/UI

Chat Interfaces

Touch based UI

Dialog UI

Notecard Config

Data Management

String Parsing

Manipulating Large Datasets

Media Management

LSL Caveats

Debugging

Test Scoring

Proposal A

This complex scoring system allows for sections to be tailored so that less important sections have less impact on the score without upsetting the balance of points.

  • Each section is scored seperately.
  • Each question will be worth some number of points.
  • Each section would have a set number of points that could count towards the total.
    • A hypothetical section may contain 20 points worth of questions only 15 would be counted.
    • This would allow for the user to get a certain number of questions wrong in a section without it effecting the score.
  • The section scores would be totaled and then a pass/fail would be determined based on some set number of points that could be missed.
    • The total section usable points may add up to something like 200 but the user would only need something like 190 to pass.