-
-
Notifications
You must be signed in to change notification settings - Fork 21.3k
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
Some QOL improvements for Asset Library interface #5284
Comments
support -> Channel. |
One year later (!) this hasn't seen much work, and 3.0 is around the corner. Assigning to the 3.1 milestone, as I think we might get new ideas and motivation to improve the assetlib as new 3.0 content starts being added to it. |
Bugsquad note: This issue is still relevant as of commit a1f835d. For the record, this is how the Asset Library interface looks like in the editor as of 2018-04-04: |
Hello, there are some usability mysteries about the asset library : |
The only thing left to do is deciding what to call the "support" button |
@flurick Do we have any more suitable name? We could rename it to "Support Level" (it seems we have enough space to do it), but I'm not sure what else we could do. |
Isn't calling it Channel fine? |
It seems to me "Server" suits pretty well. |
All support levels come from the same server (that is, |
Ok, so how about "Channel" as mentioned @Anutrix ? Or "Support channel" -- something like that? |
Personally I'd prefer fewer dropdowns and more asset details (like the update time) shown in the window, which the current interface doesn't allow for. I've edited together a quick draft of what a new interface could look like that would show clearer information and never causes overflow (which happens in both the current Godot 3 and 4 asset libraries): Do any of these changes seem like an improvement? Obviously these are just initial thoughts on how they could look, and some of them could be added while others left out. I'm planning on programming the implementation if this looks alright to anyone else (; |
I'm not sure. it feels like this proposed design makes less efficient use of horizontal space (especially on wider displays), since the two columns on the right are displaying relatively little information compared to the main column on the left. Displaying the asset's last update date is a good idea still. We can use the YYYY-MM-DD format for this, or a relative date system ("today", "yesterday", "X days ago", "X months ago"). |
@Calinou Thanks, that's a good point. Do you think it would be alright to display smaller asset icons in the list, so that more of them can be displayed? I like this format because it adds flexibility to the design; we can easily add more information at a glance if needed, for example if star ratings are added to the library. Alternatively, the icons could be larger at the expensive of slightly fewer items on screen but still a lot more information. |
The icons are designed to be displayed at a size of 64×64, so I'd prefer to keep them at their current size. Non-power-of-two scaling may look blurry, so I'd rather avoid it. Also, we currently don't have a "short description"/blurb field that we could display on the right or below each asset title. Most descriptions are too long to be featured below the asset title in the list of assets. This is something the new asset library features, but we have no ETA for deploying it currently. (Also, existing assets won't have blurbs automatically added to them, as the field is optional.) |
Ok, that makes sense. Still, with putting some of the information in columns, there's no empty space (other than padding) needed below the icons which means you can fit quite a few assets on the screen anyway. Given these changes, would you be happy for me to have a go at programming a draft version of the asset library, or would you prefer for only some or none of the changes to be implemented? I understand if you think it's better left as it is of course (: |
Hey, we've noticed that this issue has existed for about 6 years. We've noticed some changes that have already been made, but the main one about the "Support" button has not been fully touched yet. We are thinking working on it ourselves. Is that okay? Also, this is one of our first time doing this, can you give us some tips on how to do it? |
Feel free to open a pull request for this 🙂 Asset library code is in https://github.com/godotengine/godot/blob/77f4670d001b12a5c7e1f50c100301c8fb1b4d1e/editor/plugins/asset_library_editor_plugin.cpp. The same code is used in both project manager and editor. |
I think this issue should be closed or moved to https://github.com/godotengine/godot-proposals |
The Asset Library is not very polished yet, so I wanted to make some pointers about the interface and open the discussion.
The interface is a bit cryptic and it's hard to tell what some buttons and links do.
The text was updated successfully, but these errors were encountered: