-
Notifications
You must be signed in to change notification settings - Fork 347
The Lesser Of The QT Evils - Which Way To Go? #1504
Comments
Your question is not easy to answer. Technically QupZilla supports both Qt4 and Qt5. So, there is no reason to limit QupZilla to the use to one of those versions. But as you already stated, QupZilla is affected by the issues, that come with Qt4 or Qt5 - depending on the version you are using. My personal opinion: Due to the fact, that I am a "modest" user I prefer to use the latest Qt-version 5.4.0 and I am not affected by the issues you have mentioned above. "Modest" means I am using QupZilla for example for
For me, QupZilla is an excellent browser, that fits all my needs! People, who have their focus on viewing videos on youtube or playing online games (both flash content) might think about using QupZilla with Qt4 in this case, which is more stable than Qt5. However, viewing videos on youtube (html5-content) works for me with Qt5, but has some other limitations, see here. As a very helpful option QupZilla extension Videoner might be used to stream video content in an external application like for example smplayer, which will overcome all issues with streaming content. Conclusion: I am a very happy QupZilla user with qt5. |
It works perfectly for me (Qt5 5.3.2) and I don't experience these issues. I have been browsing internet without flash for about almost two years, never actually had any real need for it during that time. |
@pejakm: You didn't suffer from WebM-Crashes in the NetworkManager-Stack? That crash only happened when doing something with the NetworkManager. Qupzilla, Otter, even the demo broweser from Qt-Examples crashed. Just opening a WebView worked fine. AFAIR that was with Qt-5.2.* |
I guess I'm holding my breathe until QT 5.4 goes stable and see how that goes... |
Any luck with qt5.4? :) It appears not much has changed: http://tinyurl.com/fixedwebkit |
To my experience so far, qtwebkit that came with Qt-5.4 behaves pretty good so far, and I recommend switching to qt5 where applicable. |
To be honest everytime I turn around, there's a QT bug, with functionality of some sort not working in QupZIlla... QT and bugs bugs bugs, all I find myself doing is sitting around waiting for the next release of something to work... Seriously, I'd like to think when there's an upstream issue, that possibly the QupZilla developers might be able to do some patch work on their own, until things get worked out upstream, if this could be a reality to work around issues... Sometimes I wonder which is the worst to deal with GTK or QT, but the way I'm seeing things going in regards to QupZilla and QT, QT seems like a bloody awful mess... :( Hmmm |
That is not true ... the issues are only with QtWebKit which is now in "done" state. All development is focused on QtWebEngine, which will QupZilla be ported to. |
No, I see issues with QT and other applications right now... We all have our own ideas, so let me share mine, I've used Linux almost 15 years and in that time I've never had problems in GTK, but in the past year, everytime I turn around I keep running into QT problems, and this is not BS, so think about that. I'm either one lucky bastard to go 15 years with no issues, and one unlucky bastard when it comes to QT then... LOL... |
QT4 or QT5 either way you go there's always something going on, how sad...
So it seems to be a toss up of which bugs I don't want to deal with, the lesser of the evils, which so far seems to be to go with QT4 since I want keepassx working with the Auto type shortcut, and it doesn't with QT5...
So it would be great if we could have clarification on what the developers really want us to compile against QT4 or QT5, because the DOCS say QT4, but for all the bugs I'm running into people are saying to compile against 5...
Pretty much everywhere you look on Github everyone says to compile against QT5, and if that is now becoming the move ahead, then it would be great to get the DOCS changed to reflect this...
Bugs with QT4;
#1473
#1474
#1448
Bugs with QT5;
#1498
#1484
#1497
The text was updated successfully, but these errors were encountered: