... | ... | @@ -17,6 +17,9 @@ Currently the above three resources have no common inheritance though they do ha |
|
|
* Each Resource is typically stored atomically in a file or data management system. Therefore they are typically identified by a URL.
|
|
|
* An Attribute Resource is represented by a single attribute system
|
|
|
* A Model Resource is represented by a collection of models
|
|
|
|
|
|
`john> I might not understand the current design, but I don't think that a collection of SMTK 1 models is stored atomically in one file. Do you mean one .smtk file? I think that can only reference one model.`
|
|
|
|
|
|
* A Mesh Resource is represented by a collection of meshes
|
|
|
* Each Resource is composed of a set of Resource Components:
|
|
|
* The Attribute System is composed of Attributes
|
... | ... | @@ -42,6 +45,8 @@ The Model Manager class manages all Model Resources and Model Resource Component |
|
|
The Mesh Manager is similar to the Model Manager in that is provides access to mesh resources. In this case these are Mesh Collections since a mesh file may contain more than one mesh.
|
|
|
### Attribute Management
|
|
|
In SMTK 1.x there is no manager for Attribute Systems and the management of these systems are left to the application.
|
|
|
|
|
|
|
|
|
## Resources in SMTK 2.0
|
|
|
### Resource Base Class
|
|
|
The base class for all resources modeled in SMTK would contain the following information:
|
... | ... | @@ -58,6 +63,9 @@ The base class for all resources modeled in SMTK would contain the following inf |
|
|
* Geometric Models - vertices, edges, faces, volumes, aux geometry, component
|
|
|
* Meshes - Mesh Sets
|
|
|
* Been Modified - indicates that the resource has been modified since it was last saved
|
|
|
|
|
|
`john> The distinction between "Versioning" and "Been Modified" is not clear. Is one of them a bit/flag indicating that the model has changed in the current session? And the other a digest of the history of changes using, for example, the list of UUIDs as was discussed recently?`
|
|
|
|
|
|
* Resource Links - a set of resources that this resource references - Note that this does not mean that these resources must be loaded in prior to this resource being load into memory
|
|
|
* (Maybe) - a mapping between the component structure and the relevant workflow. For example in a surface water problem a vertex might be a hard point, an edge could be a coastline, and a face a water area.
|
|
|
* Resource Manager - this can be NULL meaning that the resource is not being managed and is up to the application to take care of it
|
... | ... | |