... | ... | @@ -19,6 +19,8 @@ Currently the above three resources have no common inheritance though they do ha |
|
|
* 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.`
|
|
|
|
|
|
`bob - Actually if there are more than one models in the native model file, the smtk file must also have multiple models (one per native model)`
|
|
|
|
|
|
* A Mesh Resource is represented by a collection of meshes
|
|
|
* Each Resource is composed of a set of Resource Components:
|
... | ... | @@ -66,6 +68,8 @@ The base class for all resources modeled in SMTK would contain the following inf |
|
|
|
|
|
`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?`
|
|
|
|
|
|
`bob - Yes`
|
|
|
|
|
|
* 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
|
... | ... | |