Hey, Gal.
On 7/8/07, Gal Nitzan <gal...@gm...> wrote:
> While debugging the space viewer I get an error when the SpaceClient
> is trying to load the door. The problem seems to be here:
>
> Template template = space.getTemplate(doorDocs[i].getTemplateID());
>
> As far as I remember a door is not a thing. So the template is missing unless
> of course I create a thing for a door and than I have 2 doors.
>
> Any clue to what I'm missing?
This is a quirk of the way doors were originally implemented.
Originally, the template with ID 1 was the default landscape and
template with ID 2 held the model which the client used for doors.
The default landscape is no longer used but the client still loads the
models for template 2 when rendering a door.
The client side door code needs work in terms of how the client
renders them, how they're triggered, and exactly what happens if a
door as a link URI to a space on a remote ogoglio service. Right now
they're rendered as whatever is in template 2, you have to click them
to trigger a teleport, and they only work if they're linked to a local
space and even then you can't specify where in that space you'd like
to teleport so you teleport to 0,0,0.
The main reason I haven't tackled doors in a complete manner is that
there's a bit of careful design work which needs to be done about how
to teleport avatars and limited account information to remote
services. In the mean time doors can be used for simple, local
teleports to demonstrate the basic idea.
- Trevor
|
