[Feature Request]: Improve extra networks UI

[halr9000]

Is there an existing issue for this?

• I have searched the existing issues and checked the recent builds/commits

What would your feature do ?

I have a love/hate relationship with the extra networks flyover. Another recent issue about inconsistent handling raises a point I have been considering. We would expect all networks to act consistently. So, why not hide the less important aspects of the technical differences entirely?

As a ui-ux user, I want to:

• browse available networks for inspiration
• quickly find an installed fine tuning in a list that can grow to 100's

TL;DR why not take some design cues from Civitai?

What's good here IMO?

• The single most important filter is at the top: categories (corresponds to local folder structure)
• Sorting by date...that's interesting as well (can look at file modtime, or what about the updatedAt key in the .info file?)
• If I care about network type (ti vs lora), there is a visual added to each preview (not sure how well this would work on mobile). Could add a filter for this as well
• all of the less important filters are hidden on the top-right

What more could be done:

• filter: baseModel
• filter: nsfw (I would really like this actually)

Proposed workflow

1. click on networks flyover
2. scroll, or pick category
3. choose networks(s) as before, but without having to first pick ti, hy, ckpt, lora

Additional information

No response

[PaulCoddington]

Extra Networks displays subfolders as buttons which behave as both filter and path.
Whether this is a feature or a bug depends on how you want to arrange your subfolders.

The buttons display folder paths but do not strictly use them, they combine some levels and not others:

\subfolder1              -> display \subfolder1 + \subfolder3\subfolder1
\subfolder2              -> display \subfolder2
\subfolder3\subfolder1   -> display \subfolder3\subfolder1
\subfolder3\subfolder4   -> display \subfolder3\subfolder4

If subfolders are going to be used as keywords in this way, it might be less cluttered and easier to navigate if there was an option to reduce buttons to unique combined subfolders only:

subfolder1               -> display \subfolder1 + \subfolder3\subfolder1
subfolder2               -> display \subfolder2
subfolder3               -> display \subfolder3
subfolder4               -> display \subfolder3\subfolder4

This would make it possible to symlink in other collections with identical (or not) subfolder structure to combine categories into a shorter list of simpler easier to read buttons.

Retaining the original behaviour as an option might work better as strictly path-based?:

\subfolder1              -> display \subfolder1
\subfolder2              -> display \subfolder2
\subfolder3\subfolder1   -> display \subfolder3\subfolder1
\subfolder3\subfolder4   -> display \subfolder3\subfolder4

Personally, I would prefer an option to be able to specify several model paths for each network type and have subfolders as categories to be combined into single unique topic buttons without having to use symlinks at all.

But there are other designs which could be considered, such as allowing some form of metadata to be defined for models by users to restrict presented lists to compatible selections (such as unique Style list per model combined with a global Style list for all models, and/or filtering LoRA by currently selected model, etc).