-
Notifications
You must be signed in to change notification settings - Fork 662
Consider switching GUI toolkits for iv #4897
Copy link
Copy link
Open
Labels
help wantedA task that is desired, but needs somebody to commit the effort to implement it.A task that is desired, but needs somebody to commit the effort to implement it.ivImage viewerImage viewerroadmapThis is a priority item on the roadmap for the next major release.This is a priority item on the roadmap for the next major release.strategicStrategic initative with far-reaching effects (in time and code space)Strategic initative with far-reaching effects (in time and code space)
Metadata
Metadata
Assignees
Labels
help wantedA task that is desired, but needs somebody to commit the effort to implement it.A task that is desired, but needs somebody to commit the effort to implement it.ivImage viewerImage viewerroadmapThis is a priority item on the roadmap for the next major release.This is a priority item on the roadmap for the next major release.strategicStrategic initative with far-reaching effects (in time and code space)Strategic initative with far-reaching effects (in time and code space)
The
ivviewer is the only part of OIIO that uses Qt, which is an extremely heavy dependency, especially considering the tiny sliver of its functionality that we use. I didn't pick Qt for any special reason -- it just seemed to be a safe choice for a popular, dependable, cross-platform GUI toolkit when I wrote the first version of OIIO's iv in 2008.We have talked before about maybe switching to something that would be a much simpler dependency to build and use. We've mentioned Dear Imgui or Nanogui as possibilities.
Let's use this issue to discuss, offer suggestions and debate the pros/cons, and track progress of the work.
As a reminder, when evaluating which toolkit to switch to, I think the considerations should include: