David Perry at TED, sharing perspective in the role of video games.

Mon 23 Feb 2009
Sun 15 Feb 2009
Where the Studio Wikitecture 4.0 (SW4) challenge produced an architectural space, the interactive features are the wiring and plumbing of that space. How can scripts ease the delivery of synchronous instruction in a virtual world? So, what are the fixtures and utilities of a classroom?
The Interactive Classroom was submitted to test these waters, and three features from that design were included in the final idesign installed for the University of Alabama. They are described here.
The design challenge assumed that instruction would occur as a synchronous event. So, what are the activities that can be expected? What actions are an instructor likely to take? Answering these questions in tedious detail provided interactions that might be simplified or even automated. Chronologically, a traditional lesson might involve the following:
This list simplifies a very complex process. But, for providing a starting point, any of these steps might present an opportunity to develop some type of interactivity. I took the approach that scripting could help with every step in this process, and tried to imagine an associated behavior for an object in each step. A script was then developed—in every case—to assist with or automate each event. (Everything except the “quiz”…I know a can of worms when I see one.) Several of these interactions would be field-tested along with the other aspects of the space that were being explored.

Some features were discarded; they were either developed too slowly (Wikitecture runs with deadlines, too) or implemented too poorly. Some were included in the first submission, but did not seem to offer much advantage…the three that made it worked, for me.
First, the notecard distributor…Most every SL user who gives a presentation or leads a class is likely to have a notecard giver. Some may even choose to drag notecards onto every avatar. This script is simply a time-saving device. On taking a seat, any avatar will receive a notecard if one was made available. No need to mention a notecard giver, no wondering if anyone has missed the offer. The teacher makes a notecard available by dragging the notecard onto the podium, and the notecard is deleted when the classroom is reset (touch podium, select “Reset All”).
Second, a “Raise Hand” image was assigned to a prim and linked to the podium and all of the seats. The same script that tells the podium that you have taken a seat (and so, to deliver a notecard) also communicates with the Hand Raise prim, which now serves as a button. Touching that button results in the broadcast of a signal that “Avatar X” has just touched it. The script in your seat evaluates the signal and checks to see if it was you that just touched that prim, if you are “Avatar X”. If so, your avatar’s hand goes up.
Yes, most avatars already have a hand raising gesture or animation. But, do they always have it ready when they need it? By the time I drill into my Inventory and activate the animation, I’ve often missed the next question in a presentation. And what about student gesture HUDs? Well, this new feature does not claim a spot in the client viewer, and also tracks the number of hands raised, reporting that tally into public chat if the teacher chooses to do so. Also, with many hands raised, the teacher can—with a touch and a menu-click—report the tally, reset the counter, and lower the hand of every avatar. (This is the scripted equivalent of a teacher saying “OK, twelve out of nineteen hands raised; you can put your hands down now.”)
The hand raising feature was surprising in its complexity. And, suspecting that linking prims does not provide an advantage over many objects listening to remote channels, I might develop this feature differently. As with any feature, the users will have to learn how to use it (a simple thing, here). Still, until installed and tested we cannot know the value of such interactive features.
Third, the Parcel Media Display accepts a formatted notecard containing URLs and titles to manage the display of audio files, images, web pages or video content available on the Internet. On touch, the object presents the teacher with a menu of buttons from which to choose a URL.
The globe (see other images) converts into the display, whose script then assigns each selected URL to the land parcel’s media stream. This alleviates use of the About Land panel by a teacher during a lesson, since the Second Life client does not have media presets.
I would like to see an organization such as NMC or ISTE sponsor a project that is similar to SW4. There was plenty of opportunity for educators to participate, yet few were around. Maybe if the project was hosted within the SL educational community…
There was some discussion, early in the project, about a standalone, self-serve media kiosk; a learning lab with many stations. I plan to continue developing this idea.
One comment made during an early presentation to the UofA pointed out how these interactive features represent “more to learn”. That is fair. Yet, I wonder if that individual has made a presentation in Second Life, making use of the full range of bells and whistles already embedded in the platform. Yes, to employ new, interactive features does require an additional step or two up an already-steep learning curve. However, if new approaches are not tested, we leave every repetitive, manual task in the hands of the teacher.
Rather than compare button selection in a dialog menu with the use of the About Land panel I will step back, and hope that some in the Alabama cadre will give these these tools a try, and offer their feedback.
Thu 5 Feb 2009
Studio Wikitecture 4.0 has delivered. Nearly four months after the first announcement, a virtual classroom (SLURL) has been placed on the Second Life® campus of the University of Alabama. Finishing touches continued to the last, even on the morning ofl Keystone Bouchard’s’s presentation to the university.

Occasionally, members vote on each other’s contributions. Designs with the most votes are carried forward, and new design elements are folded in. The final design emerges (hopefully) as an collection of all the best features.
Cream, rising to the top.
As essential as the Wiki-Tree was the management of the group by Jon Brouchoud. During many a chat, members became critical of the process, the designs, and even other members. I was doing some of the talking, too. Jon always seemed to field our gripes with the calm of a zen master.
Writing about it now, I am reminded of something an educator said about working with groups in SL…something about herding cats.The Wiki-tree tree has potential. It helps a group to juggle ideas. Sure, it was down at times; but was probably as reliable as SL itself. And, there are other “holodeck” styled rezzing tools in SL. However, the Wiki-tree is not meant to simply present multiple builds, one after another. You can review many designs in a short time, take a copy and riff on that design, even roll back to earlier versions. The tree also preserves the relationship among diverging strands of development (the branching of limbs reflects those relationships). Everybody adds their bits, patching together the best design possible.
This may be the closest I ever get to Granny’s quilting circle.
My own contribution focused on interactive features meant to simplify some activities (i.e., distributing handouts and URL selection). Several elements from my Interactive Classroom were included in the final design, and I will write about those in another post. First, I wanted to explore here the Wikitecture Way.
The Wikitecture project had its share of hiccups. But the Wiki-tree and the Wikitecture process are both evolving, according to Studio Wikitecture co-founder Ryan Schultz (Theory Shaw in SL). New ideas will be implemented with the 5.0 project (yet to be announced). And, finally, the the Alabama faculty will have to judge the worth of the virtual classroom design. But, there can be no question about the educational value and success of this project, because…
I learned plenty.