Re:The Tree Slider - GitHub
by jfager on Tuesday December 07, 2010 @06:46PM
(#1981170)
Very nice, but what I'd personally rather have is a two-pane navigator: explore the tree in the left pane, see file contents in the right, a la NERDtree, eclipse, and other IDEs.
Re:The Tree Slider - GitHub
by jdminhbg on Tuesday December 07, 2010 @11:00PM
(#1981826)
This isn't [only] two panes, but it gives you the ability to navigate files while still seeing the directory structure: https://github.com/sr3d/GithubFinder
It's implemented as a bookmarklet that you can activate on any github repo for an advanced view.
Re:The Tree Slider - GitHub
by jws on Tuesday December 07, 2010 @06:46PM
(#1981167)
From the Digital Equipment Corporation, VMS Guide to Performance Tuning, from before 40% of the HN readership were born:
5.3.4.3 Lower the Baud Rate if Terminals Smooth Scroll
If many of the applications at your site write characters to
terminals in the smooth scrolling mode … you might consider
reducing the baud rate [from 9600 to 4800] … the decrease in
the baud rate would be barely perceptible to the users.
VT100 transitions come to the rescue!
(Smooth scrolling was at 6 lines per second. Glassy smooth, especially if you kept the line saturated to the flow control limits. But as a consequence it couldn't accept more than about 4000bps of data on 80 character lines.
That particular hint never made much sense to me because it is about saving interrupts and a screen of data took the same number of interrupts at 4800 or 9600. I think it was more about slowing down the users without them noticing to avoid upgrading the computing resources.)
Re:The Tree Slider - GitHub
by borism on Tuesday December 07, 2010 @07:48PM
(#1981349)
"A century after the wireless telegraph revolutionised communications, the Internet has re-established a telegraph that runs on (telephone) wires." -Umberto Eco,
who's essay was widely criticized here yesterday for some factual mistakes. He did get one thing right though.
Re:The Tree Slider - GitHub
by kellysutton on Tuesday December 07, 2010 @06:01PM
(#1981036)
The best transitions are those that mask loading of something else. Ever think of why icons on the iPhone explode out when opening an app or the app image zooms to the front?
Re:The Tree Slider - GitHub
by patio11 on Tuesday December 07, 2010 @10:09PM
(#1981696)
Back when BCC was a desktop application, I once got complaints that someone missed my "busy bees" on the splash screen after she upgraded her computer. The JRE load hit below one second and she didn't see the screen anymore.
Re:The Tree Slider - GitHub
by yan on Tuesday December 07, 2010 @10:21PM
(#1981723)
I guess this is a good place to ask, but does anyone know why GitHub opted not to list the file size in the file viewer? Whenever I browse other peoples' code I always want to glance at file sizes to see which files I should peruse first.
Re:The Tree Slider - GitHub
by cdavid on Wednesday December 08, 2010 @06:26AM
(#1982526)
Maybe because it is difficult to do so efficiently ? It is hard to get per-file information in git, so you would have to be pretty clever to get it working w.r.t. history.
Other bugtrackers which were based on svn had a lot of issues with git because of this.
Re:The Tree Slider - GitHub
by storborg on Tuesday December 07, 2010 @05:06PM
(#1980834)
I would love it if this widget eager-loaded the directory structure for a couple levels (doesn't even need to load the commit data) so that it made the navigation to a specific file/folder even faster.
Re:The Tree Slider - GitHub
by tjarratt on Tuesday December 07, 2010 @05:55PM
(#1981018)
Actually I don't think that's necessary - I'd much rather they focus on making individual loads very fast, instead of pre-loading data. 9 times of out 10, I'm not going to peruse the ENTIRE directory structure even one level deep, so it should only get the data I want.
Also, they would need to store that, and I don't necessarily want my browser storing my entire directory structure (and possibly file contents) for any amount of time other than when I'm actually browsing it.
Try it out, it really is very fast without having to eagerly load anything at all.
Re:The Tree Slider - GitHub
by pjscott on Tuesday December 07, 2010 @06:29PM
(#1981118)
They could build a page-transition graph: for each page, what are the links that people are most likely to click? This could let them figure out what the top one or two most common next-pages are, and those could be pre-loaded.
That would be more work for the GitHub guys, but I'm pretty sure it would work.
Re:The Tree Slider - GitHub
by bdonlan on Wednesday December 08, 2010 @03:50AM
(#1982322)
A reasonable fallback would be to look at the proportion of commits that touch files under each directory - the more active a directory is, the more likely it is to be of interest. Still probably not worth it in the majority of cases though.
Re:The Tree Slider - GitHub
by stevenbedrick on Thursday December 09, 2010 @04:46PM
(#1989317)
I like that idea quite a bit, actually- I'm envisioning a sort of "heat map" UI, where each entry in a directory listing's background color is determined by its commit frequency.
Re:The Tree Slider - GitHub
by storborg on Tuesday December 07, 2010 @08:55PM
(#1981521)
The individual load still takes a full HTTP round trip, which is going to be slow no matter how you slice it. Comparatively, storing several layers of a directory structure (all you need is file/directory names in a JSON tree) is pretty tiny.
Re:The Tree Slider - GitHub
by storborg on Tuesday December 07, 2010 @11:26PM
(#1981888)
Yes, I've used the feature--I spend a lot of time every day using Github. At my office, where I have a fast connection, it works very well and I like it. At home, where I have a shitty connection, it's hardly faster than the old method.
I'm just pointing out that since they've changed the arrangement (e.g. no page reload when navigating between directories), they could take advantage of it to get a huge performance gain rather than a small performance gain.
Re:The Tree Slider - GitHub
by binaryfinery on Tuesday December 07, 2010 @05:19PM
(#1980887)
FTFA: "Want more? Check out the HTML History API Demo and MDC's Manipulating the browser history documentation. Facebook has blogged about their use of this stuff, and Flickr has been doing it for months on their lightbox view."
So, its not even news. Unless, I suppose, the reader learned javascript in 2001 and feels they don't need to keep up on new things. That's the HN crowd is it?
Fuck, I've been learning javascript for a week and I know how to do this.
It's implemented as a bookmarklet that you can activate on any github repo for an advanced view.
(Smooth scrolling was at 6 lines per second. Glassy smooth, especially if you kept the line saturated to the flow control limits. But as a consequence it couldn't accept more than about 4000bps of data on 80 character lines.
That particular hint never made much sense to me because it is about saving interrupts and a screen of data took the same number of interrupts at 4800 or 9600. I think it was more about slowing down the users without them noticing to avoid upgrading the computing resources.)
who's essay was widely criticized here yesterday for some factual mistakes. He did get one thing right though.
Other bugtrackers which were based on svn had a lot of issues with git because of this.
Also, they would need to store that, and I don't necessarily want my browser storing my entire directory structure (and possibly file contents) for any amount of time other than when I'm actually browsing it.
Try it out, it really is very fast without having to eagerly load anything at all.
That would be more work for the GitHub guys, but I'm pretty sure it would work.
I'm just pointing out that since they've changed the arrangement (e.g. no page reload when navigating between directories), they could take advantage of it to get a huge performance gain rather than a small performance gain.
Try jQuery Mobile repo:
https://github.com/jquery/jquery-mobile
[Obviously, you will need Chrome/Firefox 4/Safari.]
So, its not even news. Unless, I suppose, the reader learned javascript in 2001 and feels they don't need to keep up on new things. That's the HN crowd is it?
Fuck, I've been learning javascript for a week and I know how to do this.
Relax, dude.