Recent searches
Search options
@klardotsh @neauoire @technomancy Oooh yeah, this history tree looks sweet. And I'm another keyboard navigator here, using qutebrowser for this despite its extortionate memory usage. I also do program in C, but am yet to contribute to any programs other than my own! Nevertheless intrigued to look into Netsurf, and maybe, just maybe…
@miblo @klardotsh @neauoire no offense but the idea of building out the link hinting system in C seems real bad! I don't want to use a browser that has an obscure navigation functionality used by 0.5% of the already-small userbase that could contain a coding mistake which causes private data to be leaked
there's a lot to hate about XUL and a lot to hate about JS, but building out the user interface in a different language from the rendering engine was 100% the right move; they are very different types of coding with very different constraints
@miblo @klardotsh @neauoire sorry if this came across as too negative; I don't want to discourage you from hacking on what you find fun
I just get kind of down when I get to thinking about browsers, and the immense gap between where we could be and where we are, yknow?
@technomancy @klardotsh @neauoire Oh yeah, no offence taken! I just read it that the bit keeping you from doing it may be that you don't work in C. And then from Devine doing it is that they hardly ever use keyboard shortcuts. (At which point the Venn diagram came and drew itself for me.)
Keyboard-junky fistbump? 
@technomancy @miblo @klardotsh I've only brought up the history navigation interface so others might be inspired to try it, and if they want, port it to other systems. I didn't think this would so rapidly devolve into language-bashing.
@neauoire @miblo @klardotsh sorry; I didn't mean it as language bashing
I'm not saying it's wrong to use C for netsurf in general; I'm saying you need an extension system for this specific feature
different languages are good at different things and it's best to play to their strengths
@neauoire @technomancy @miblo @klardotsh Oh, I was thinking of doing so already! Seems like a perfect fit for TVs!
@alcinnz @neauoire @technomancy @klardotsh And with this you've sparked my imagination! You mean the history tree in particular, I understand(?), but my mind is just on TV browser navigation in general.
The idea: Treating the screen as a 3×3 grid, we may press the remote's number keys 1−9 to subdivide it, repeatedly and maybe zooming to it, until our view contains 9 or fewer links. Then each link gets numbered, and we may press the key to open it, or press-and-hold to open in new tab…
@miblo I was thinking of using those as scrolling shorthands, but I like your idea... It may be better to use them as link navigation shorthands!
@alcinnz @neauoire @technomancy @klardotsh Ah, interesting! Yeah, maybe having all 9 number keys for scrolling might be overkill, unless you've got "non-reflowing" zooming as a big deal, and need lots of horizontal scrolling?
Or, what about making it toggleable? In one case 1−9 scrolls. Toggle the mode with, say, the Blue key, and then 1−9 does the link nav?
@miblo @neauoire @technomancy @klardotsh I've got uses for all the colour buttons, in case I can't rely on certain other buttons existing.
Red & Record would bookmark a page.
Green & Info would show page metadata, find-in-page, & machine translation. If I have a Subtitle button that'd also do machine translation.
Blue & Angle would cycle stylesheets (I think that's an important feature!).
Yellow & Menu would toggle the history view.
@alcinnz @neauoire @technomancy @klardotsh Oh cool, okay! Well, yeah, I will say that this all sounds sweet, and I reckon having Yellow toggle a NetSurf-style history tree would be amazing! 