Kitely Forums

Constance Peregrine wrote:I think that perhaps option 2 would be nice.

Once the page is open they can see the person's description, see any photos they have, and keep the browser tab up if they want to go at another time (or bookmark it). If they want to go immediately they can simply click the enter world button which works nicely when inside the grid, but can have the option of using it when not logged in too, which is a nice feature.

afaik only SL has such a feature. Thus highlighting this piece of tech, as well as the actual page tech. Giving people a taste of what they can also do.

I agree with Constance, but recommend combining this with option 4. The url for the Kitely page can be included in the notecard, as can Firestorm hops to other places of interest (beyond SW corner).

For ease of reference, here's the question and options again.

Dot Matrix wrote:What would be most useful to have happen when showcase world boards are clicked?

1. Give a landmark to the world
2. Open the Kitely website at the World's webpage
3. Open the viewer inworld teleport map
4. Give a notecard about the world, including an embedded landmark

Ilan Tochner wrote:IMO an option that doesn't always work is not viable. This means that the notecard with embedded landmark option limits our choice of worlds to those that have the landing spot located in the SW region of the world.

This issue rules out options 1, 3 and 4, unless the "SW region landing point only" criterion is implemented (which I do not want to do -- it limits the choice of worlds far too much).

Ilan Tochner wrote:I think it is important to keep teleports simple. A person clicking on a sign showing a world should be able to click just once more to initiate the teleport. Anything more complicated than that will result in many people not figuring out how to get to the desired world.

For option 2, clicking the board gives a dialog box giving the option to open the world web page, and from there the user can click a third time to enter the world. Three clicks seems to be the minimum number unless osTeleportAgent can be used.

Having the world web page to read while waiting for the world to start up might help reduce the impact of the delay in teleporting. It also avoids the inworld viewer message "Teleport failed". It is also relatively simple to implement, using a standard llLoadURL script.

A set of notecards with embedded landmarks for showcase worlds can, of course, be produced at a later date if thought desirable.

However, for now, things need to be asap (where s = soon AND simple). So it looks like option 2 is the one to go for.

Hi Dot,

There is a problem with going with option 2 in that pressing the Enter World button on a world page will only work for people who are logged into the Kitely website and are currently using the same user account to be logged into the Kitely grid.

Using a script with osTeleportAgent seems like the cleanest option. Alternatively, creating a script that reads a notecard embedded in the display and uses its contents to displays a dialog box with a description of the world and two buttons, one to close the dialog and the other to teleport into that world.