From owner-freebsd-cvsweb@FreeBSD.ORG Thu Feb 9 17:19:11 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 002F116A420 for ; Thu, 9 Feb 2006 17:19:10 +0000 (GMT) (envelope-from mlemos@acm.org) Received: from phpclasses.org (phpclasses.org [69.55.226.116]) by mx1.FreeBSD.org (Postfix) with SMTP id B6FD943D49 for ; Thu, 9 Feb 2006 17:19:10 +0000 (GMT) (envelope-from mlemos@acm.org) Received: (qmail 551 invoked from network); 9 Feb 2006 17:23:36 -0000 Received: from unknown (HELO ?127.0.0.1?) (127.0.0.1) by localhost with SMTP; 9 Feb 2006 17:23:36 -0000 Message-ID: <43EB798C.3090807@acm.org> Date: Thu, 09 Feb 2006 15:19:08 -0200 From: Manuel Lemos User-Agent: Thunderbird 1.5 (X11/20060111) MIME-Version: 1.0 To: noackjr@alumni.rice.edu References: <43C9913E.1050005@acm.org> <43DEE1C7.60809@alumni.rice.edu> In-Reply-To: <43DEE1C7.60809@alumni.rice.edu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-cvsweb@freebsd.org Subject: Re: File descriptions X-BeenThere: freebsd-cvsweb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list 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:19:11 -0000 Hello, 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 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. 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. -- Regards, Manuel Lemos Metastorage - Data object relational mapping layer generator http://www.metastorage.net/ PHP Classes - Free ready to use OOP components written in PHP http://www.phpclasses.org/ 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 From owner-freebsd-cvsweb@FreeBSD.ORG Fri Feb 10 14:42:50 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 9FF1C16A420 for ; Fri, 10 Feb 2006 14:42:50 +0000 (GMT) (envelope-from gael.vittu@cnqd.cnamts.fr) Received: from smtpp.cnamts.fr (smtpc.cnamts.fr [81.255.27.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAB0C43D48 for ; Fri, 10 Feb 2006 14:42:49 +0000 (GMT) (envelope-from gael.vittu@cnqd.cnamts.fr) Received: from smtpp.cnamts.fr (imss2 [127.0.0.1]) by localhost.cnamts.fr (Postfix) with ESMTP id EE6A16F371 for ; Fri, 10 Feb 2006 15:42:47 +0100 (CET) Received: from pivot1.crip.cnamts.fr (unknown [55.36.5.2])by smtpp.cnamts.fr (Postfix) with ESMTP id E36156F348for ; Fri, 10 Feb 2006 15:42:47 +0100 (CET) Received: from hermes2.cnamts.fr (unknown [55.36.30.1])by pivot1.crip.cnamts.fr (Postfix) with ESMTP id E154A57249for ; Fri, 10 Feb 2006 15:42:47 +0100 (CET) Received: from hermes2.cnamts.fr (localhost [127.0.0.1])by localhost.cnamts.fr (Postfix) with ESMTP id 9B2462682Dfor ; Fri, 10 Feb 2006 15:43:39 +0100 (MET) Received: from [55.24.1.60] (unknown [55.24.1.60])by hermes2.cnamts.fr (Postfix) with ESMTP id 43F8C2682Afor ; Fri, 10 Feb 2006 15:43:39 +0100 (MET) Message-ID: <43ECA602.5010101@cnqd.cnamts.fr> Date: Fri, 10 Feb 2006 15:41:06 +0100 From: =?ISO-8859-1?Q?Ga=EBl_Vittu?= User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-cvsweb@freebsd.org Content-Type: multipart/mixed; boundary="=_Boundary_KF8enygvY8o3MyWfnBFx" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: CVSWeb improvement: per profile CVSroots display X-BeenThere: freebsd-cvsweb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS Web maintenance mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2006 14:42:50 -0000 This is a multi-part message in MIME format. --=_Boundary_KF8enygvY8o3MyWfnBFx Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Hello, Due to the number of CVSRoots contained in our organization, I'm actually working on cvsweb to add a per-profile selection functionality for displayed CVSroots. The aim is to permit a user to see *all* CVSRoots displayed in a default file (see below) and to choose CVSRoots the user wants to add in his profile For the client, there's just a new text box (Profile) on the right of 'Module Path or Alias' where he can: - put the name of the profile he wishes to use - use the default profile - link to a new page to select the CVSRoots and the name of the profile to save What I've done is: - add in the cvsweb.conf file a DEFAULTVALUE "profile" => "default", - add the functionality to read the text box "profile" and then read a secondary "cvsweb.conf" file where the variable @CVSrepositories only contains what the user selected. I've somes questions to you, masters of CVSWeb: 1/ Do you guys think such a functionality could be included in CVS? 2/ How should I manage my users profile? creating a secondary conf file as I've already did it or using a proprietary format? 3/ Can I use another program than *cvsweb* to display all the cvsroots or should I include a case in the main program? I'm a rookie in Perl and trying to do my best, but if this functionality is included in the official cvsweb, please, do not be too cruel with me ;-) -- Gaël VITTU - ATOS-Origin/CNAMTS-CNQD +33 (0)4.76.69.43.91 --=_Boundary_KF8enygvY8o3MyWfnBFx Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable ***************************************************** "Le contenu de ce courriel et ses eventuelles pi=E8ces jointes sont confidentiels. Ils s'adressent exclusivement =E0 la personne destinataire. Si cet envoi ne vous est pas destin=E9, ou si vous l'avez re=E7u par= erreur, et afin de ne pas violer le secret des correspondances, vous ne devez pas le transmettre =E0 d'autres personnes ni le reproduire. Merci de le= renvoyer =E0 l'=E9metteur et de le d=E9truire. Attention : L'Organisme de l'=E9metteur du message ne pourra =EAtre tenu= responsable de l'alt=E9ration du pr=E9sent courriel. Il appartient au destinataire de v=E9rifier que les messages et pi=E8ces jointes re=E7us ne contiennent pas de virus. Les opinions contenues dans ce courriel et ses =E9ventuelles pi=E8ces jointes sont celles de l'=E9metteur. Elles ne refl=E8tent pas la position= de l'Organisme sauf s'il en est dispos=E9 autrement dans le pr=E9sent courriel." ****************************************************** --=_Boundary_KF8enygvY8o3MyWfnBFx--