search

KhronosGroup / glTF-Project-Explorer

Tool to provide a filterable registry of glTF community projects.
Apache License 2.0
87 stars 46 forks source link

Add fastgltf #155

Closed spnda closed 1 year ago

spnda commented 1 year ago

I also noticed that the "import" and "load" tasks seem to have the same meaning, is that known?

CLAassistant commented 1 year ago

CLA assistant check
All committers have signed the CLA.

javagl commented 1 year ago

I also noticed that the "import" and "load" tasks seem to have the same meaning, is that known?

There is an issue talking about the exact meaning of "task" and its possible values: https://github.com/KhronosGroup/glTF-Project-Explorer/issues/111 . The issue also explains a bit of where the current categories came from.

One difficulty is that it's hard to assign a "strong" meaning to these keywords: They don't have semantics that all developers can agree on. A library developer might call a function readGltf(uri), or loadGltf(uri), or importGltf(uri). The potential differences in the meaning are subtle and maybe even subjective. And on a technical level, this even might depend on the context - e.g. whether this is the implementation of an existing Reader, Loader or Importer interface of another library.

For me, "load" sounds a little bit more bare-boned, like in a library that only reads the glTF data structures, whereas "import" sounds more like something that happens in the context of an application - e.g. to import a glTF into Blender or so. But this is highly subjective. Maybe we can clarify that in the context of the other issue.