1. 12

I am the main developer of qutebrowser, a browser with a keyboard-focused user interface inspired by the vim editor.

It is currently based on the QtWebKit rendering engine which is getting dated and has various issues.

With this campaign, I hope being able to work full-time on qutebrowser for a while. The goal is to add support for the newer QtWebEngine backend, which is based on Chromium.

Nearly 1.5 months are already funded, but there’s a lot of work to do, and I’d be glad if I could afford spending more time on qutebrowser before starting studying in September!

  1.  

  2. 4

    Looks like an awesome project, best of luck getting funded! For anyone who is using chrome as their main browser, I’ve used the Vimium[1] chrome extension with some luck. I’m curious if you’ve seen/used this extension before and some of the benefits of qutebrowser over this extension (beside native support for the vim bindings which I would think lends itself to a more fluid experience)

    [1]https://chrome.google.com/webstore/detail/vimium/dbepggeogbaibhgnhhndojpepiihcmeb?hl=en

    1. 4

      Vimium (which I used for a longer time before starting qutebrowser) is mostly about keybindings, while mostly keeping the Chrome UI (it has no other choice, with Chromium’s plugin API). It doesn’t have things like a real commandline, easy extensibility, or a minimal UI.

      I think the user interface is really important - I have a relatively low-resolution screen (1366x768), and I don’t want a big address/tab bar I almost never look at.

      Also, with qutebrowser you can do things like :spawn mpv {url} to simply launch mpv to play the current URL. Or :hint links spawn mpv {hint-url} to do the same via hints. Or :download-open to simply open the file you just downloaded. Or edit form fields with e.g. vim by using Ctrl-e.

      From my point of view, qutebrowser compared to Vimium is basically like vim compared to some IDE with really bad vim emulation.

      1. 2

        Thanks so much for the run down, qutebrowser sounds awesome. I was sad to see that homebrew dropped QtWebKit as I was exited to give it a try.

        Using qutebrowser with Homebrew on OS X is currently broken, as Homebrew dropped QtWebKit support with Qt 5.6. I’m working on building a standalone .app for OS X instead, but it’ll still take a few days until it’s ready.

        1. 3

          I built a standalone .dmg/.app for qutebrowser just a few hours ago, I’ll release a v0.6.0 dmg once some people confirmed it works - if you want to test it, that’d be most appreciated! https://t.cmpl.cc/qutebrowser.dmg

          1. 1

            App worked perfectly. Was able to download it and fire it up no problem. I’ll play around with it a bit more and let you know if anyone comes up.

            Sent from my qutebrowser

            1. 1

              Awesome, thanks for testing! I assume you’re on OS X 10.11 (~~Yosemite~~El Capitan)? I’d be really curious if it works on 10.10/10.9 as well.

              1. 1

                El Capitan actually (10.11.4 (15E65)). I think I might have an older machine I can try it out on, i’ll have to get back to you on that. I did receive a crash signing into github and reported it through the reporting dialogue box that came up. Not sure how that reporting system works and if you’ll eventually get the crash report but if there’s a better place for me to send it to you let me know.

                1. 1

                  Hmm, I think you’re running into this Qt bug. I fixed it in Qt, but maybe for some reason the Mac I’m building the dmg on didn’t have the fix backported…

                  I think you get an OS X crash report window? Can you look at the details there and confirm the stacktrace mentions WebCore::SocketStreamHandle::platformClose() too?

                  1. 1

                    Sorry for the delay, yes I see that line in the stack trace

                    0   libsystem_kernel.dylib          0x00007fff9d1948ea __kill + 10
                    1   libsystem_platform.dylib        0x00007fff8c61852a _sigtramp + 26
                    2   ???                             000000000000000000 0 + 0
                    3   QtWebKit                        0x000000010774bf04 WebCore::SocketStreamHandle::platformClose() + 84
                    4   QtWebKit                        0x000000010774a79a WebCore::SocketStreamHandleBase::disconnect() + 26
                    5   QtWebKit                        0x000000010773bf96 WebCore::WebSocketChannel::fail(WTF::String const&) + 710
                    6   QtWebKit                        0x0000000107739375 WebCore::WebSocket::close(int, WTF::String const&, int&) + 325
                    7   QtWebKit                        0x00000001077fb42d WebCore::jsWebSocketPrototypeFunctionClose(JSC::ExecState*) + 205
                    
                    1. 1

                      That’s indeed the crash I suspected it was - I installed the patched Qt on my build machine and repacked, can you please try https://t.cmpl.cc/qutebrowser-dmgv2.dmg ?

                      1. 1

                        Yup looks like that fixed the crash. I was able to sign into github no problem.

                2. 1

                  Hi, it seems to run fine on 10.10.4 (Yosemite) for me. Good luck!

        2. 1

          I’ve been a heavy user of Vimium for a few years and I just tried this on my windows machine. It works really well! Will see if I can contribute to development, PyQt5 looks awesome to use.

          1. 1

            I’d be glad! Let me know if you need help :)

        3. 2

          exciting project! :)

          1. 2

            All ready has a great team working on it. Cant wait for the upgrade to QtWebEngine.