Skip to content
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

Table View for plugin list #274

Open
someguynamedphil opened this issue Nov 7, 2024 · 3 comments
Open

Table View for plugin list #274

someguynamedphil opened this issue Nov 7, 2024 · 3 comments
Labels
duplicate This issue or Pull Request already exists

Comments

@someguynamedphil
Copy link

I don't find the default display of the plugins all that useful.

I think a simple table-list would work better enabling one to sort by plugin name (how many copies of FartinATOR do I have on the system?), or by format (which VST2 plugins are on my system?) or by version number (What version of FartinATOR do I have?)

It should be pretty easy to add as it just displays the data already present in the application. just in a more straightforward manner.

I've included a mockup:

OwlPlug-database-view

it could be handy to have a tags field but not critical.

You could have it as just a tab on front of the plugin.

@arendej
Copy link

arendej commented Nov 12, 2024

I agree this would be very useful for sorting thru and managing long lists of plugins.

Additional to this request: also have colums for:

  • if a plugin is a demo/trial
  • if a plugin requires internet connectivity or a launcher or parent VST/app
  • if a plugin is managed by an external app

@DropSnorz DropSnorz added the duplicate This issue or Pull Request already exists label Nov 19, 2024
@DropSnorz
Copy link
Owner

Hello !

Thanks for your suggestions, I've opened issue #270 to display plugins as table.

Additional to this request: also have colums for:

  • if a plugin is a demo/trial
  • if a plugin requires internet connectivity or a launcher or parent VST/app
  • if a plugin is managed by an external app

Unfortunately, it's quite hard (to not say impossible) to get these data just by scanning plugins. I might flag plugins "Installed by OwlPlug", but i think there is nothing else I can do 😢

If you have an idea on how to implement this, i'm open to suggestions.

@someguynamedphil
Copy link
Author

someguynamedphil commented Nov 19, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or Pull Request already exists
Projects
None yet
Development

No branches or pull requests

3 participants