From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luis Felipe =?UTF-8?Q?L=C3=B3pez?= Acevedo Subject: bug#25045: [Website] Packages page takes too long to load Date: Mon, 28 Nov 2016 13:41:49 -0500 Message-ID: References: <878ts4jz8m.fsf@gnu.org> <87inr7pmj2.fsf@pompo.co> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38577) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cBQtN-00024y-QF for bug-guix@gnu.org; Mon, 28 Nov 2016 13:43:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cBQtK-0006id-Kf for bug-guix@gnu.org; Mon, 28 Nov 2016 13:43:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:58047) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cBQtK-0006iY-Gq for bug-guix@gnu.org; Mon, 28 Nov 2016 13:43:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cBQtK-0008Rj-Aj for bug-guix@gnu.org; Mon, 28 Nov 2016 13:43:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87inr7pmj2.fsf@pompo.co> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: alex@pompo.co Cc: 25045@debbugs.gnu.org On 2016-11-28 12:00, Alex Sassmannshausen wrote: > Hi Luis, > > Indeed, I had a first bash at solving this problem by providing a set > of > static html pages paginated by the first letter of the package name. > > I'm not particularly wedded to this solution, so if you feel strongly > about going another way, I'd be keen to hear/see about it. > > In the meantime, I'm open to testing/feedback. I will unfortunately > not > be able to put work into this until at least Saturday/Sunday, as some > Perl work has higher priority at the moment. > > But let me know if you have questions or feedback! > > Best wishes, Hi, Alex :) The solution I had in mind includes an alphabetic index, and pagination as well. However, it includes a few more things, and would take some time to design and implement. So I think we should use your patch to fix the size issue as soon as possible. For what is worth, this is what I had in mind: /packages/ First page of the list of packages. Packages listed here only provide a summary: package logo (if any), name, version, description, and an indicator if it has issues. This page also has filters to find packages (for now, alphabetic filter. In the future, category filter, and search box). /packages/page/N/ Page N of the list of packages. /packages/a/ First page of the list of packages whose name starts with A. Packages are presented the same way as in /packages/. /packages/a/page/N/ Page N of the list of packages starting with letter A. /packages/icecat/X.Y.Z/ Page with details about IceCat version X.Y.Z. It includes all the information about this package, including its issues (which are currently listed in a separate page along with the issues of other packages: /packages/issues.html). Including the issues of a package in its detail page could avoid having the current issues page grow too much, like the current Packages page. This static pagination and filtering would generate A LOT of pages, but of reasonable size for web browsers to load. Best, -- Luis Felipe López Acevedo http://sirgazil.bitbucket.org/