https://bugs.kde.org/show_bug.cgi?id=299517
--- Comment #33 from Nate Graham <n...@kde.org> --- That's more or less how it actually works. :) The part that's the same (SANE) is common, and the part you can see (the user interface) is made with different tools: Qt and GTK and so on.What I think you're trying to say though is that Qt and GTK shouldn't be separate; we should have a single UI toolkit or set of low-level application development tools that are common to everybody, and each environment would just write a custom UI on top of it according to their HIG. And yeah, that would be great. But Qt and GTK both *do* exist. And Enlightenment, and Flutter, and a bunch of others. We can't go back in time and delete them all except for one. For better or worse, we are stuck in a world with multiple GUI toolkits. And this means that you can't just grab the code from an app that's written in another GUI toolkit; it doesn't work like that. To use your car metaphor, it would be like trying to put the engine from a Volkswagen into a Honda. By the time you made it work, it would have been easier, cheaper and work better to just get a new engine for the Honda! That's the situation here with this feature; how SimpleScan implements the feature is not applicable for Skanlite because of all the other technical differences between them. Fortunately, a new scanning app called SkanPage is under heavy development. It already has this feature and I expect it will eventually replace Skanlite over time. It uses the same backend SANE library but it's written with a more modern user interface component set which makes it easier to work on and extend in the future. -- You are receiving this mail because: You are watching all bug changes.
