From: Eric Christopherson Date: 2011-10-09T00:05:51+09:00 Subject: Re: [ANN] ruby-doc.org has been updated On Fri, Oct 7, 2011 at 11:51 AM, James Britt wrote: > Eric Christopherson wrote: >> >> [Replying on the list since everyone else is doing it -- apologies.] > > Short-term OK, long-term, not the best way to get my attention since I don't > usually follow the list that closely anymore. > >> >> It looks very nice. However, a few bad things stand out: >> >> 1. I always have to scroll horizontally. I'm probably more picky about >> keeping my browser size fixed (and non-maximized) than most people; so >> at my preferred browser size, the content doesn't fit horizontally. > > What size is good for you? It looks like my Firefox here is 950px. I'd have to check what size I use at home. If you're designing for 960, I could certainly expand it 10 more; but, as others have argued, it would be nice to have it more adaptable to various sizes. > >> Even when I maximize it, it doesn't quite fit, since I have a wide >> taskbar at the left edge. When I hide my taskbar and maximize the >> browser, I can see all of the content except for a few code examples >> that run off the edge (for example, the code in >> instance_variable_set(symbol, obj) → obj under Object); there is still >> a horizontal scrollbar. > > OK. > >> >> (I'm seeing this with more and more sites these days, so it might be >> that designers don't worry about fitting horizontal space anymore, and >> I need to adjust. But I'd rather not :) ) > > I generally assume 960px or so is reasonable. [snip] >> 5. It would be nice to have filtering of methods, etc. on the class pages. > > > Isn't that there?  if you click on the icon next to "Class/Module index" it > should open a search box. > > Perhaps that's not entirely obvious ... No, it wasn't, but I see it now. That brings up another point -- it only filters classes and modules still. I was looking for something to filter the methods (and/or constants, etc.) in the class under discussion. Also -- and I'm assuming you or Phrogz are aware of this -- the filter text box in question doesn't respond to cursor keys, home/end, etc.