Difference between revisions of "User talk:Burhop Piccard/Geometry Based Architecture View"
Jump to navigation
Jump to search
(Added reason for model change.) |
|||
| Line 13: | Line 13: | ||
* More explicit link between non-SL data stored on the Agent domain and the Viewer. Data in Format F or G must have an equivilent F or G Renderer in the Viewer | * More explicit link between non-SL data stored on the Agent domain and the Viewer. Data in Format F or G must have an equivilent F or G Renderer in the Viewer | ||
[[User:Burhop Piccard|Burhop Piccard]] 15:21, 3 November 2007 (PDT) | |||
Revision as of 14:55, 3 November 2007
Given Zero Linden's discussion on Oct 30th and an earlier disucssion at the AWGroupies meeting, I'm hoping we can reformulate the Geometry and Physics discusions to provide better input to the AWG. This is an intial stab at something that:
- Provides useful information to the AWG as they define the components and comunication protocols.
- Meets the needs of content creators that want greater variety of geometric content and better support for current and future creation tools.
- Can be incrementally implemented starting with existing SL geometry.
It needs much discussion so please feel free to add your thoughts here. --Burhop Piccard 19:17, 30 October 2007 (PDT)
I updated the geometry model following the SLDEV discussion on this topics (see https://lists.secondlife.com/pipermail/sldev/2007-October/006237.html and additional emails in November for more information) The main differences are:
- Changes to the "Client Side Library" so only one Application plugs into a "Reusable Client Side Library".
- Clarification on SL data versus non-SL data.
- More explicit link between non-SL data stored on the Agent domain and the Viewer. Data in Format F or G must have an equivilent F or G Renderer in the Viewer
Burhop Piccard 15:21, 3 November 2007 (PDT)