Unfortunately, I don’t know your name, just your OpenID URL, so I’ll have to reply here instead of in-world.

Your code has two slight bugs…

1) llParcelMediaCommandList is missing the initial L on line 36 (thus the “name is not defined within scope” error).

2) site is an integer, but at the very end you’re assigning it a floating point value; use site = 1; instead.

I hope that helps!

Actually Philip promised we’d see HTML on a prim by may 2008 about a month ago already in this interview, and thank you for the script

Here’s the script:
integer site = 1;
string luna = “http://lunajubilee.blogspot.com”;
string noel = “http://ingmanndesign.com”;
string pheobe = “http://slfashionality.blogspot.com”;

default
{ // beginning of state
state_entry()
{ // stuff between this set of brackets happens when you first load the script
// or the script gets reset

llParcelMediaCommandList([
PARCEL_MEDIA_COMMAND_URL, noel,
PARCEL_MEDIA_COMMAND_TYPE, "text/html"]);

}

touch_start(integer total_number)
{
if ( site == 1.0 )

{ // bracket to start doing stuff if the site is 1.0

llParcelMediaCommandList([
PARCEL_MEDIA_COMMAND_URL, noel,
PARCEL_MEDIA_COMMAND_TYPE, "text/html"]);

site = 2;
} // bracket to end the first if statement

else if ( site == 2 ) // “else if” is what you use for the script to keep
// checking stuff in case that first if statement
// isn’t valid
{ // bracket starts the else if stuff
lParcelMediaCommandList([
PARCEL_MEDIA_COMMAND_URL, luna,
PARCEL_MEDIA_COMMAND_TYPE, "text/html"]);

site = 3;
} // end this else if stuff

else if ( site == 3)
{
lParcelMediaCommandList([
PARCEL_MEDIA_COMMAND_URL, pheobe,
PARCEL_MEDIA_COMMAND_TYPE, "text/html"]);
site = 1.0;

}
} // end of touch stuff
} // end of state

I wonder, though, what happened to Philip’s announced “no features in 2008″ policy. The upgrade to Havok 4 and to WindLight are actually viewed as “patching”/”debugging” to improve SL’s reliability (server-side on one case, client-side on the other). So although they’re new technologies, they’re not “just eye-candy” but necessary upgrades (the old code was too hard to maintain and to include new features).

HTML-on-a-prim is by all means something new… I wonder how Philip justifies that internally!