If the GTK3 developers "don't give a sh*t" as you say, if they prefer the "decorations" (it is a fortunate word isn't it?) over functionality, could it be high time to port the whole project to QT?
I realize it would be an ambitious undertaking, but it is not without precedent. Wireshark is probably the biggest project ported away from GTK; that was done two years ago (and accomplished to beta in six months), and they have not looked back.
Although it would represent a substantial investment in development time it would end the latency issue, which I've experienced and read about since at least version 0.48. Since this project has a relatively high profile, you might be able to get some sponsorship or development assistance from QT. In the end I think the application would perform better and be more maintainable.
If there is a philosophical barrier to QT, I'd like to know what it is. Also I would be glad to donate to the project to help with the cost of porting or the development time.
If the GTK3 developers "don't give a sh*t" as you say, if they prefer the "decorations" (it is a fortunate word isn't it?) over functionality, could it be high time to port the whole project to QT?
I realize it would be an ambitious undertaking, but it is not without precedent. Wireshark is probably the biggest project ported away from GTK; that was done two years ago (and accomplished to beta in six months), and they have not looked back.
Although it would represent a substantial investment in development time it would end the latency issue, which I've experienced and read about since at least version 0.48. Since this project has a relatively high profile, you might be able to get some sponsorship or development assistance from QT. In the end I think the application would perform better and be more maintainable.
If there is a philosophical barrier to QT, I'd like to know what it is. Also I would be glad to donate to the project to help with the cost of porting or the development time.