-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Model List Organization #423
Comments
Given that we regularly add test models, the overhead of maintaining separate categories (in folder structure, configuration and UI) is not negligible. |
This work is currently happening. It needs to remain open. |
@UX3D-eckerlein This is not part of the maintenance, however this is currently planned in the Khronos tooling group. So, let's keep this open. |
@DRx3D is this still relevant? |
I don't know exactly which further organization @DRx3D had in mind when opening this issue. Maybe some sort of "hierarchy" in the dropdown list, like
that reflects the categories (tags) in glTF-Sample-Assets? I also wondered whether hovering an entry could show the screenshot of that entry in a small popup (or ... maybe, depending on the screen size, the screenshots or thumbnails could be incuded in the list to begin with). But in view of further possible "restructurings" of the Model List:
For example: With one caveat: When users are dragging-and-dropping a model, then the selection in that model list should reflect that, and turn into something like |
It would be really good to have some sort of organization to the list of models. There is a tremendous variety of items there from test models to production-quality ones. This list is sufficiently long to (85 items, I think) that it is easy to miss the ones that should be seen. Several different orderings and information could be displayed, depending on the space and structure that is available.
in general I think the production-quality models should be listed first, perhaps in reverse chronological order; and the system test models last, probably in alphabetical order.
The text was updated successfully, but these errors were encountered: