You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current package selection interface in the GUI is starting to get more difficult to sift through as more packages get added.
It would be nice to have drop down menus or branches for the categories we use for our packages. This way people know what each tool is used for at a glance without having to know what a tool is or look up what a tool does.
Another nice thing to have may be to have the ability search/filter. i.e., someone starts to start typing a package name and have the package list filter down to that for easier searching. The alphabetical ordering right now is fine, just tedious.
I'm planning to take a stab at improving the FlareVM GUI packages interface and sorting things into categories.
My initial attempt has led me to realizing that we may need a slight design change somewhere, so that I'm able to get categories (and ideally their associated packages) over to the flare-vm installer easily.
I wish we could pass more metadata through our CI via choco push to our myget so that when we pull the info via choco search, we'd be able to get the associated category as well, but that seems to be unlikely since that's not what it's designed for.
My current thought is to modify categories.txt to be an xml instead so that we include the associated package names with each category (and possibly categories associated with FlareVM vs CommandoVM if we want to do that as well).
This would require us to keep it in sync with any category changes (either at a package level or just category name level), but I think this trade-off is worth the investment.
This also gives us a quick high level overview of what packages fall into each category at a glance, which might be useful data to be aware of.
This would also of course require some modifications to various templates and scripts that rely on categories.txt the way it is now, which should be fairly trivial imo.
As packages continue to increase, it'd be great if we had a way to better display / organize available packages.
Initial ideas:
The text was updated successfully, but these errors were encountered: