AfflictionNetworks/narya
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added note.

Browse Source 
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@248 542714f4-19e9-0310-aa3c-eee0fc999fb1
This commit is contained in:
Michael Bayne
2001-08-15 01:08:00 +00:00
parent 8d017e268f
commit 1ffbae2cc4
1 changed files with 22 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/miso/design.txt
+22 -20
View File
@@ -1,6 +1,13 @@
# #
# $Id: design.txt,v 1.2 2001/07/10 22:22:35 shaper Exp $ # $Id: design.txt,v 1.3 2001/08/15 01:08:00 mdb Exp $
* Notes
Consider making MISO sufficiently sophisticated to allow the cluster stuff
to be implemented as an extension. This would included allowing the XML
scene stuff to allow extensions, the scene editor to allow extensions and
of course extending the MisoScene class itself.
* Discussion
Date: 07/10/01 Date: 07/10/01
Venue: General discussion in vast sweeping loft area. Venue: General discussion in vast sweeping loft area.
Participants: mdb, shaper. Participants: mdb, shaper.
@@ -28,8 +35,8 @@ TBD: art details, how many frames of animation, what kinds of things
can be carried, paper-doll-ing of character clothing, possibility of can be carried, paper-doll-ing of character clothing, possibility of
color-replacement to allow increased re-use of clothing art. color-replacement to allow increased re-use of clothing art.
Scene Description * Design
----------------- ** Scene Description
- sid: unique scene identifier - sid: unique scene identifier
- name: scene name - name: scene name
- version: scene description file format version - version: scene description file format version
@@ -38,17 +45,13 @@ Scene Description
of scene coords of scene coords
- exits: set of scene coords and associated sids that the exits lead to - exits: set of scene coords and associated sids that the exits lead to
Potential Classes ** Potential Classes
-----------------
SceneIDBroker: dynamic scene creation and obtaining/tracking scene ids SceneIDBroker: dynamic scene creation and obtaining/tracking scene ids
SceneManager: scene retrieval, caching SceneManager: scene retrieval, caching
TileManager: tile retrieval, caching TileManager: tile retrieval, caching
Config: tileset/tile info Config: tileset/tile info
Tile Sets and Tiles ** Tile Sets and Tiles
-------------------
General high-level categories of tiles: General high-level categories of tiles:
3 * outside (three prospective themes) 3 * outside (three prospective themes)
@@ -104,15 +107,14 @@ needed for drawing tiles (e.g. exclude corners of iso squares), but
only if noteworthy perf gain achieved. Perhaps other similar only if noteworthy perf gain achieved. Perhaps other similar
worthwhile uses. worthwhile uses.
TBD: ** TBD
*** Resource mgmt
When is scene data and art loaded, how big are the chunks of data
downloaded, what's the user experience during download like.
- Resource mgmt: when is scene data and art loaded, how big are the *** On-screen "map" display of the surrounding scenes
chunks of data downloaded, what's the user experience during The scenes comprising a town, etc. potentially impacts how we allow
download like. placement of exits in a scene since allowing folks to place exits to their
houses/bldgs willy-nilly may make map generation wacky. perhaps useful
- on-screen "map" display of the surrounding scenes, the scenes for game designer use as well when laying things out and "surveying the
comprising a town, etc. potentially impacts how we allow placement landscape."
of exits in a scene since allowing folks to place exits to their
houses/bldgs willy-nilly may make map generation wacky. perhaps
useful for game designer use as well when laying things out and
"surveying the landscape."