From owner-freebsd-cvsweb@FreeBSD.ORG Thu Feb 9 17:46:30 2006 Return-Path: X-Original-To: freebsd-cvsweb@freebsd.org Delivered-To: freebsd-cvsweb@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E538416A420 for ; Thu, 9 Feb 2006 17:46:29 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: from smtp107.biz.mail.re2.yahoo.com (smtp107.biz.mail.re2.yahoo.com [206.190.52.176]) by mx1.FreeBSD.org (Postfix) with SMTP id 6ED1D43D45 for ; Thu, 9 Feb 2006 17:46:29 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: (qmail 92126 invoked from network); 9 Feb 2006 17:46:28 -0000 Received: from unknown (HELO optimator.noacks.org) (noackjr@supercrime.org@24.99.22.177 with login) by smtp107.biz.mail.re2.yahoo.com with SMTP; 9 Feb 2006 17:46:27 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 822496144; Thu, 9 Feb 2006 12:46:25 -0500 (EST) Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 00629-10-2; Thu, 9 Feb 2006 12:46:24 -0500 (EST) Received: from [127.0.0.1] (optimator [192.168.1.11]) by optimator.noacks.org (Postfix) with ESMTP id E24EE6143; Thu, 9 Feb 2006 12:46:23 -0500 (EST) Message-ID: <43EB7FF2.3070606@alumni.rice.edu> Date: Thu, 09 Feb 2006 12:46:26 -0500 From: Jonathan Noack User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Manuel Lemos References: <43C9913E.1050005@acm.org> <43DEE1C7.60809@alumni.rice.edu> <43EB798C.3090807@acm.org> In-Reply-To: <43EB798C.3090807@acm.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at noacks.org Cc: freebsd-cvsweb@freebsd.org Subject: Re: File descriptions X-BeenThere: freebsd-cvsweb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: CVS Web maintenance mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2006 17:46:30 -0000 Manuel Lemos wrote: > on 01/31/2006 02:04 AM Jonathan Noack said the following: >> Manuel Lemos wrote: >>> Maybe I am missing something obvious, but I could not find an option to >>> make the descriptions of each file appear at least in the page to browse >>> the file. >>> >>> I see the use_descriptions option in the cvsweb.conf but that seems for >>> module descriptions. >>> >>> Is there a way to make cvsweb display the file descriptions? At least it >>> should appear in the file page, but I think it would be nice if it could >>> appear somehow in the respective file listing too. >> Right now it appears that use_descriptions only works for directories. >> Adding a Description column to files would make them very wide, although >> there's nothing preventing us from doing it. Displaying the >> descriptions on the file page is a decent idea. The descriptions file >> would have to be loaded for each page, so making it large would have an >> adverse effect on interactivity. > > I am not sure what you mean by descriptions file. I mean the description > that you used when you add a file this way: > > cvs add -m "Description here" filename.txt Ah! I zeroed in on use_descriptions and completely missed your point. Sorry for misunderstanding. Parsing out the description in readLog doesn't look too bad. I'll hack a prototype and get back to you. > In directory listings, the description could optionally appear in second > line below the file name, as at least in my browser, the file icon is > usually taller than twice the height of the current file name font. > > The description could be clipped to not exceed a configurable length > limit. It could also take the whole table row span since it would the > only thing in a second line. > > This would be an option, so other people that do not like the idea, can > disable file descriptions on directory listings. Personally I think that > a description is better than guessing what the file is from the file name. > > Another complementary idea is to set the file link tag title > attribute to the file description. That would make the description > appear in many browsers as tool tip when the mouse passes over the link. > > As for descriptions in the file pages, that would be an obvious feature, > so I think it should appear at the top below the file path header. These are all great ideas. Thanks! > BTW, one thing that I miss in file pages is a direct link to show the > HEAD revision of the file. I know it works with an URL like this, but > there seems to be no link directly to that. > > filename.txt?rev=HEAD;content-type=text%2Fplain > >> If you are having problems getting use_descriptions to work with >> directories, be sure you add the descriptions file to >> CVSROOT/checkoutlist as documented in section 9 of the INSTALL file. > > No, I was talking only about files. Gotcha... -Jonathan