Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Doogie – A Chromium-Based Browser with Tree-Style Pages

cretz.github.io

Post reply on HN
Print view View original

41–50 of 82 posts

Re: Show HN: Doogie – A Chromium-Based Browser with Tree-Style Pages

#41

Post by jcelerier »

kodablah wrote: post #13
cjbillington wrote: post #11

Cool 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 :-)

You should look into distributing an AppImage. Its author has a very nice script that you can use to ship Qt apps that works on all linux distros: https://github.com/probonopd/linuxdeployqt

Also, is there a particular technical reason you went with CEF directly instead of QtWebEngine or QtWebkit ? It would be interesting to know about it.

Re: Show HN: Doogie – A Chromium-Based Browser with Tree-Style Pages

#43

Post by dotancohen »

kodablah wrote: post #7
mateuszf wrote: post #2

Looks great! I'll wait for the OSX version. Also - vim or emacs shortcuts would be appreciated.

Yeah, sorry. I developed this on my Thinkpad and I didn't really want to dev this in a hackintosh VM. My fear is that even if I develop a OSX version, it will become stale because I don't use it regularly. I abstracted all the platform-specific stuff, so it should be really easy for anyone wanting to add OSX support. I'll happily help/guide anyone.

> My fear is that even if I develop a OSX version, it will become stale

Being open source and hosted on Github, I doubt that will be a problem. The Mac community is rather active.

By the way, here's my vote for VIM keybindings!

Do you have a Paypal address that we could donate to?

Re: Show HN: Doogie – A Chromium-Based Browser with Tree-Style Pages

#45

Post by kodablah »

jcelerier wrote: post #41
kodablah wrote: post #13

Earlier quoted context omitted.

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 :-)

You should look into distributing an AppImage. Its author has a very nice script that you can use to ship Qt apps that works on all linux distros: https://github.com/probonopd/linuxdeployqt Also, is there a particular technical reason you went with CEF directly instead of QtWebEngine or QtWebkit ? It would be interesting to know about it.

I'll look into linuxdeployqt. I am probably just going to statically link Qt. I am not using anything security conscious with Qt and I don't want versions changing underneath, so a system-level Qt makes little sense I think.

QtWebKit was deprecated then just recently undeprecated IIRC (with a non-Qt maintainer). As for the QWebEngine stuff, it was a bit premature when I was looking and didn't offer everything I needed at a low level. It's quite possible it does now (and would make my work easier!), but I have not looked.

Re: Show HN: Doogie – A Chromium-Based Browser with Tree-Style Pages

#46

Post by kodablah »

dotancohen wrote: post #43
kodablah wrote: post #7

Earlier quoted context omitted.

Yeah, sorry. I developed this on my Thinkpad and I didn't really want to dev this in a hackintosh VM. My fear is that even if I develop a OSX version, it will become stale because I don't use it regularly. I abstracted all the platform-specific stuff, so it should be really easy for anyone wanting to add OSX support. I'll happily help/guide anyone.

> My fear is that even if I develop a OSX version, it will become stale Being open source and hosted on Github, I doubt that will be a problem. The Mac community is rather active. By the way, here's my vote for VIM keybindings! Do you have a Paypal address that we could donate to?

For macOS support: https://cretz.github.io/doogie/guide/faq#where-is-the-macos-...

For donations: https://cretz.github.io/doogie/guide/faq#where-can-i-donate-...

Re: Show HN: Doogie – A Chromium-Based Browser with Tree-Style Pages

#47

Post by anotheryou »

jdc0589 wrote: post #38

I switched to Firefox (dev edition) a month or so ago almost completely becuase the TreeStyleTabs extension is better than anything for chrome. I LOVE having nested tabs. It totally prevents me from getting lost when I'm links deep in technical documentation.

it will change a bit though. A rewrite for firefox' new plugin architecture is on the way

Re: Show HN: Doogie – A Chromium-Based Browser with Tree-Style Pages

#49

Post by yellowapple »

0xCMP wrote: post #14

I 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…

This is what Conkeror was meant to be.

Unfortunately, Conkeror is reliant on XULRunner, which is deprecated if not outright EOL now (especially since XUL itself is deprecated / nearing EOL).

Re: Show HN: Doogie – A Chromium-Based Browser with Tree-Style Pages

#50

Post by tokenizerrr »

nachtigall wrote: post #21
gmurphy wrote: post #17

This is a great use of Chromium! Storytime! 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.

> It was too power-user for what we were going for Chrome might as well support the Sidebar API to make this possible like Firefox will do with Tree-Tab-Style Add-on iirc. I read a bug report once at the Chromium bug tracker saying roughly "Sidebar API wont be implemented because UI needs to stay simple".

I hate the "UI must be simple" aspect of chrome so much. So many features don't get implemented because of it.
Post reply on HN