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

Show HN: A Tree-Based Way to Navigate Browsing History

joeltg.github.io

Post reply on HN
Print view View original

11–17 of 17 posts

Re: Show HN: A Tree-Based Way to Navigate Browsing History

#11

Post by nornagon »

joelg wrote: post #3
nornagon wrote: post #2

I've been wanting this for years. I worked on the Chrome team and wanted to make something like this the built-in way to browse history. Instant install :) Thanks!

Thank you! Let us know if you find any bugs or have any suggestions. On a side note, we were really torn on whether to use favicons or tab screenshots as the node images. If anyone has design opinions on this, we'd love to hear them!

It'd be awesome if `Esc` closed the visualization, it took me a moment to figure out I had to click the icon again to close out of it.

Re: Show HN: A Tree-Based Way to Navigate Browsing History

#12

Post by nornagon »

darkerside wrote: post #5
nornagon wrote: post #2

I've been wanting this for years. I worked on the Chrome team and wanted to make something like this the built-in way to browse history. Instant install :) Thanks!

Was it something that languished in the feature backlog, or was there an intentional decision against it? Just curious :)

I think that with sufficient determination I could have pushed it through, but it was a side project, I was a junior engineer, & I would have needed significant design resources & buy-in to get it to shippable. I believe it would have been possible (Chrome is an especially open & flat structure within google, compared to e.g. Android), but I wasn't willing to go through the effort at the time. I ended up leaving Google to be one of the first engineers at Transcriptic :)

Re: Show HN: A Tree-Based Way to Navigate Browsing History

#13

Post by nornagon »

joelg wrote: post #3
nornagon wrote: post #2

I've been wanting this for years. I worked on the Chrome team and wanted to make something like this the built-in way to browse history. Instant install :) Thanks!

Thank you! Let us know if you find any bugs or have any suggestions. On a side note, we were really torn on whether to use favicons or tab screenshots as the node images. If anyone has design opinions on this, we'd love to hear them!

... Also, I just realised it overrides cmd+arrow keys. Those are super important for navigating in text on OS X! Unfortunately I'll have to disable until it doesn't do that, since there doesn't seem to be an option to remap or disable those keybinds.

Re: Show HN: A Tree-Based Way to Navigate Browsing History

#14

Post by joelg »

nornagon wrote: post #13
joelg wrote: post #3

Earlier quoted context omitted.

Thank you! Let us know if you find any bugs or have any suggestions. On a side note, we were really torn on whether to use favicons or tab screenshots as the node images. If anyone has design opinions on this, we'd love to hear them!

... Also, I just realised it overrides cmd+arrow keys. Those are super important for navigating in text on OS X! Unfortunately I'll have to disable until it doesn't do that, since there doesn't seem to be an option to remap or disable those keybinds.

You can remap or disable keyboard shortcuts in chrome://extensions, I believe! (you might have to enable developer mode first)

Edit - also, dismissing the view with esc. or clicking anywhere is something I should have done from the start. Thanks!

Re: Show HN: A Tree-Based Way to Navigate Browsing History

#15

Post by willlma »

I've been wanting to build something like this. It would be really cool to see all tabs' histories side by side rather than just the current tab. Even though a tree gets wide pretty quickly, you're seldom using multiple tabs simultaneously, so if you make line-height a function of time, you shouldn't have too many items on a row.

Re: Show HN: A Tree-Based Way to Navigate Browsing History

#16

Post by [deleted] »

nornagon wrote: post #11
joelg wrote: post #3

Earlier quoted context omitted.

Thank you! Let us know if you find any bugs or have any suggestions. On a side note, we were really torn on whether to use favicons or tab screenshots as the node images. If anyone has design opinions on this, we'd love to hear them!

It'd be awesome if `Esc` closed the visualization, it took me a moment to figure out I had to click the icon again to close out of it.

[deleted]
Post reply on HN