$ ./doogie
./doogie: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.9' not found (required by ./doogie)
Or is it supposed to use the Qt shared objects in the current directory? It seems to find the system ones first.Show HN: Doogie – A Chromium-Based Browser with Tree-Style Pages
11–20 of 82 posts
Re: Show HN: Doogie – A Chromium-Based Browser with Tree-Style Pages
#12Re: Show HN: Doogie – A Chromium-Based Browser with Tree-Style Pages
#13Cool idea. Can't run on the latest Ubuntu though, it seems the latest Qt in the Ubuntu repos is 5.7? $ ./doogie ./doogie: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.9' not found (required by ./doogie) Or is it supposed to use the Qt shared objects in the current directory? It seems to find the system ones first.
Re: Show HN: Doogie – A Chromium-Based Browser with Tree-Style Pages
#14That tree on the left would be better in some kind fuzzy search screen that appears on a key-binding (e.g. like some setups in Emacs) and otherwise be hidden so the full screen can be used for the page. Either as a panel like it is now or a modal/window.
Re: Show HN: Doogie – A Chromium-Based Browser with Tree-Style Pages
#15[1] https://chrome.google.com/webstore/detail/tabs-outliner/eggk...
Re: Show HN: Doogie – A Chromium-Based Browser with Tree-Style Pages
#16I wish someone would create an Emacs buffer style browser where we could easily switch between tabs similar to how Emacs lets you switch buffers. I know you can do this in Emacs, but I just think for all the work people do to get tabs working nicely, maybe the way Emacs has done it actually works pretty well without overwhelming the screen with so much information all the time. That tree on the left would be better i…
https://github.com/ch11ng/exwm
In the tiling mode, Emacs buffers and X11 windows map 1:1. It's like having arbitrary X programs inside Emacs.
Re: Show HN: Doogie – A Chromium-Based Browser with Tree-Style Pages
#17Storytime! When we started designing Chrome back in 2006, and despite having spent the past year working on Google's Firefox team, my favorite browser was iRider, which was an IE shell with tree-style-tabs. It was too power-user for what we were going for, but some of the concepts (pinning) live on in Chrome today.
Re: Show HN: Doogie – A Chromium-Based Browser with Tree-Style Pages
#18Cool idea. Can't run on the latest Ubuntu though, it seems the latest Qt in the Ubuntu repos is 5.7? $ ./doogie ./doogie: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.9' not found (required by ./doogie) Or is it supposed to use the Qt shared objects in the current directory? It seems to find the system ones first.
Eek, yeah, I didn't have a global Qt install when I was testing. I do bundle the Qt libs along side. Maybe change LD_LIBRARY_PATH to local dir? I have filed an issue: https://github.com/cretz/doogie/issues/45 . That's why it's an alpha release :-)
Perhaps you can fix by calling dlopen on the shared objects explicitly rather than linking them and relying on the linker to find the libraries at runtime. I'm not sure, not totally familiar with C linking.
Re: Show HN: Doogie – A Chromium-Based Browser with Tree-Style Pages
#19Re: Show HN: Doogie – A Chromium-Based Browser with Tree-Style Pages
#20Currently juggling between FF Nightly (for speed and memory usage) but lacking critical add-ons (LastPass), and Chrome(/ium). I tried Vivaldi for a bit but was really disappointed with the UX after a while. I miss the golden era of Opera.