|
Replies:
2
-
Last Post:
Sep 24, 2007 7:27 PM
by: kaplanj
|
|
|
|
|
|
|
Uploading a cell to the server
Posted:
Sep 21, 2007 10:31 AM
|
|
|
In my pursuit of drag and drop, I am now more focused on the "drag in" part. I want to drag a file into the environment and have it appear as some sort of Cell. I believe this means I need the Wonderland Client to send some sort of message to the Server to create a Cell at a particular location. So far, the only precedent I've been able to find is the Avatar, but that's kind of a special case.
Can anyone suggest to me what kind of message I would send, or how to signal to the Server to create a cell?
Thanks!
|
|
|
|
|
|
|
Re: Uploading a cell to the server
Posted:
Sep 21, 2007 4:43 PM
in response to: bswett
|
|
|
This is something we have discussed. We want the ability for users to add cells on the client and then have them uploaded to the server for global distribution.
There are a number of steps to the final solution
WFS integration
Client side addition of cell via primitive ui
Generation of wfs files to describe cell
upload wfs description and content to server
WFS is being actively developed and we are about to start work on the first phase of the client interface to allow content to be added.
The focus at the moment is on geometry, but could be extended to other data. For example dragging a OpenOffice doc in world would create a cell running OpenOffice displaying the doc. It will take us a little while to get to that stage however.
|
|
|
|
|
|
|
|
|
Re: Uploading a cell to the server
Posted:
Sep 24, 2007 7:27 PM
in response to: paulby
|
|
|
Just to elaborate a little on Paul's reply: there are currently two cases where we dynamically add cells to the world. The avatar cell, as you mentioned and the SharedApp2DCell that gets created when you launch a native application. SharedApp2DCell, which gets created in the processNativeApplicationMessage() method of WonderlandSessionListener, is a more typical example than the Avatar.
I think a more general mechanism would be reasonably easy to implement. For example the client could send the server a CellSetup message, and the server could use that information to create a new cell and notify other clients. This would look very much like the current SharedApp2D cell creation path. The only change is that the target cell type would need to provide a method to read its initial data from a CellSetup message. Perhaps these kind of cells could implement a "UserCreatable" interface.
Both the Avatar cell and the NativeApplication cell are currently transient -- they go away when the hosting client disconnects. To make these cells permanent, you might also want to write to the WFS, but that seems like a future concern.
|
|
|
|
|
java.net RSS
