chaiNNer-org / chaiNNer

A node-based image processing GUI aimed at making chaining image processing tasks easy and customizable. Born as an AI upscaling application, chaiNNer has grown into an extremely flexible and powerful programmatic image processing application.

Home Page:https://chaiNNer.app

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Allow the user to define which viewer/app is used in the "View Image (external)" node in the Settings

mrjschulte opened this issue · comments

commented

Currently the viewer hardcoded in the "View Image (external)" uses a set of OS specific basic default/system image viewers.

Optionally, not as a default, allow for the user to change/select the Application being used by creating a new option to select a path to the application of choice in chaiNNer's Settings module. For instance, if a User wants to use Photoshop, Gimp or Krita to view their images then they would enter the path to their respective app and save it in this new dialog.

Alternatively, a "use custom viewer" checkbox which would then show a path selector, but then this would become a per-node setting rather than a global one.

Optionally, not as a default, allow for the user to change/select the Application being used by creating a new option to select a path to the application of choice in chaiNNer's Settings module.

This seems like a good change. For best UX, I think the following settings layout would be best:

  • A dropdown with the options "System Default" and "Custom".
  • An application path selector that is available when "Custom" is selected.

This will allow us to add application detection later. Basically, we can try to detect installed photo programs and show them in the dropdown as well. So if e.g. Gimp and Photoshop are installed, the dropdown would list "System Default", "Gimp", "Photoshop", "Custom". Since cross-platform application detection might be a tiny bit difficult, this would be an optional goal.

Alternatively, a "use custom viewer" checkbox which would then show a path selector, but then this would become a per-node setting rather than a global one.

This would make chains dependent upon specific software being installed (in specific locations), so I'm not a fan. I would like chains to be portable.

Chains are already dependent on other files being in specific locations, such as image files or model files. But I get your point