OpenSimulator:Future Release Discussion
From OpenSimulator
m (→In-World console maintenance) |
|||
| Line 18: | Line 18: | ||
== In-World console maintenance == | == In-World console maintenance == | ||
Terrain manipulations, statistics and some SIM administration related tasks are not available using the Viewer - they are only available on the command line application console where OpenSim is running. It would be nice to have this same console available in-world, using an Instant Messaging window with the simulator itself, the same way as we do with thoses old command line terminals. | Terrain manipulations, statistics and some SIM administration related tasks are not available using the Viewer - they are only available on the command line application console where OpenSim is running. It would be nice to have this same console available in-world, using an Instant Messaging window with the simulator itself, the same way as we do with thoses old command line terminals. | ||
| + | |||
| + | == Externally Scripted Objects == | ||
| + | A prim with the script contents something along the line of //external:somehost:someport. | ||
| + | Have the simulator connect to this host:port and relay data from it to the prim. | ||
| + | Example, have a simple library that maps the LSL functions to a simple binary protocol, which can be used from various programming languages, not neccessarily .NET, and have it act like a server. | ||
| + | This would allow scripts to be hosted outside the Simulator while adding security, as no code would be running on the Simulator. People could code Prim scripts using C if they wished, and the library would simply send the LSL commands to the server for relaying to the clients. If this could go straight to the client then even better. The next step after that would be for the script to be able to send Prim data aswell. | ||
| + | This also gives the possibility of using one running script on several different Simulators at once. | ||
| + | - HashBox | ||
Revision as of 13:10, 2 March 2008
A collection of ideas for additional functionality in OpenSim. Please add your thoughts - anyone may contribute.
Contents |
3D grid structure
I have always wanted to see a grid where you could have regions not only to the north, south, east west of a region but also above and below. This would enable space above for orbiting space stations and the like and depth below for underwater worlds and tunnels. - Garth FairChang
Scripting
See the list of OSL Proposals.
Payment System
OpenSim will need to support micropayment. See Money for details on how this could be achieved.
Upload of existing 3D models
OpenSim should support common standards for 3D modelling. This would allow the upload of existing 3D models and make OpenSim immediately attractive for architects and project developers and their customers (walk through models).
Free-form Avatars
OpenSim should, at some point in time, support the design and animation of free-form avatars (e.g. animals, monsters, robots).
In-World console maintenance
Terrain manipulations, statistics and some SIM administration related tasks are not available using the Viewer - they are only available on the command line application console where OpenSim is running. It would be nice to have this same console available in-world, using an Instant Messaging window with the simulator itself, the same way as we do with thoses old command line terminals.
Externally Scripted Objects
A prim with the script contents something along the line of //external:somehost:someport. Have the simulator connect to this host:port and relay data from it to the prim. Example, have a simple library that maps the LSL functions to a simple binary protocol, which can be used from various programming languages, not neccessarily .NET, and have it act like a server. This would allow scripts to be hosted outside the Simulator while adding security, as no code would be running on the Simulator. People could code Prim scripts using C if they wished, and the library would simply send the LSL commands to the server for relaying to the clients. If this could go straight to the client then even better. The next step after that would be for the script to be able to send Prim data aswell. This also gives the possibility of using one running script on several different Simulators at once. - HashBox
