Difference between revisions of "User:Morgaine Dinova"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
Goals | = Goals = | ||
== System goals == | |||
In order of importance: | |||
* Scalability for events (Philip acknowledged the need for it publicly 3 years ago). | |||
* Scalability along the other 3 dimensions. | * Scalability along the other 3 dimensions. | ||
* Interop with 3rd party worlds and grids. | * Interop with 3rd party worlds and grids. | ||
== Client goals == | |||
In no particular order: | |||
* Improve portability across compilers and platforms. | * Improve portability across compilers and platforms. | ||
* Remove dependencies on specific versions of required libraries. | * Remove dependencies on specific versions of required libraries. | ||
* Add an event API for use in scripting language bindings. | * Add an event API for use in scripting language bindings. | ||
* Refactor access to required libraries to allow alternative choices. | * Refactor access to required libraries to allow alternative choices. | ||
* Refactor subsystems to allow alternative choices (see below). | * Refactor subsystems to allow alternative choices (see below). | ||
* Decouple the viewing from the presence handling, allow N:1 (multiple views per presence). | * Decouple the viewing from the presence handling, allow N:1 (multiple views per presence). | ||
* Replace refactored 2D GUI by decoupled alternative [footprint reduction]. | * Replace refactored 2D GUI by decoupled alternative [footprint reduction]. | ||
* Replace refactored audio system by decoupled alternative [footprint reduction]. | * Replace refactored audio system by decoupled alternative [footprint reduction]. | ||
* Make the refactored 3D navigation/camera event-driven [for scripting, machinima]. | * Make the refactored 3D navigation/camera event-driven [for scripting, machinima]. | ||
* Attach QA/test modules for test-driven development and system regression testing. | |||
Among the many other benefits, physical refactoring gives us the opportunity to harness multiple cores. | Among the many other benefits, physical refactoring gives us the opportunity to harness multiple cores. | ||
Occasionally I just despair and decide to rewrite the whole thing from scratch. Tomorrow, that is. ;-) | Occasionally I just despair and decide to rewrite the whole thing from scratch. Tomorrow, that is. ;-) | ||
== Personal goals == | |||
* Fun. :-) | * Fun. :-) | ||
Enough to keep me busy for a while ... | |||
= Materials = | |||
== References == | |||
= Drafts and collaborative work = | |||
== Multi-Process Client == | |||
[[Multi-Process Client -- draft]] | |||
Revision as of 01:52, 7 November 2007
Goals
System goals
In order of importance:
- Scalability for events (Philip acknowledged the need for it publicly 3 years ago).
- Scalability along the other 3 dimensions.
- Interop with 3rd party worlds and grids.
Client goals
In no particular order:
- Improve portability across compilers and platforms.
- Remove dependencies on specific versions of required libraries.
- Add an event API for use in scripting language bindings.
- Refactor access to required libraries to allow alternative choices.
- Refactor subsystems to allow alternative choices (see below).
- Decouple the viewing from the presence handling, allow N:1 (multiple views per presence).
- Replace refactored 2D GUI by decoupled alternative [footprint reduction].
- Replace refactored audio system by decoupled alternative [footprint reduction].
- Make the refactored 3D navigation/camera event-driven [for scripting, machinima].
- Attach QA/test modules for test-driven development and system regression testing.
Among the many other benefits, physical refactoring gives us the opportunity to harness multiple cores.
Occasionally I just despair and decide to rewrite the whole thing from scratch. Tomorrow, that is. ;-)
Personal goals
- Fun. :-)
Enough to keep me busy for a while ...