From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.bugs Subject: bug#71180: [ELPA Feature Request] Package thumbnail Date: Tue, 28 May 2024 06:21:28 +0000 Message-ID: <875xuy4ftj.fsf@posteo.net> References: <86a5ken8py.fsf@gmail.com> <87plt8x2ev.fsf@posteo.net> <86jzjfjfg0.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38036"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 71180@debbugs.gnu.org, Stefan Kangas , Stefan Monnier To: "Elijah G." Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue May 28 08:22:40 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1sBqEK-0009gw-6L for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 28 May 2024 08:22:40 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sBqDt-0000fx-8E; Tue, 28 May 2024 02:22:17 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sBqDf-0000WH-39 for bug-gnu-emacs@gnu.org; Tue, 28 May 2024 02:22:02 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1sBqDZ-0005Ll-Gc for bug-gnu-emacs@gnu.org; Tue, 28 May 2024 02:21:58 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1sBqDi-0001HZ-Ca for bug-gnu-emacs@gnu.org; Tue, 28 May 2024 02:22:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Philip Kaludercic Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 28 May 2024 06:22:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 71180 X-GNU-PR-Package: emacs Original-Received: via spool by 71180-submit@debbugs.gnu.org id=B71180.17168773094911 (code B ref 71180); Tue, 28 May 2024 06:22:02 +0000 Original-Received: (at 71180) by debbugs.gnu.org; 28 May 2024 06:21:49 +0000 Original-Received: from localhost ([127.0.0.1]:45578 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sBqDV-0001H8-9P for submit@debbugs.gnu.org; Tue, 28 May 2024 02:21:49 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]:56133) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sBqDT-0001Gu-0a for 71180@debbugs.gnu.org; Tue, 28 May 2024 02:21:48 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 27748240104 for <71180@debbugs.gnu.org>; Tue, 28 May 2024 08:21:30 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1716877291; bh=Rqnt/SQ44l41e6PpoAV3g1c6OMly6rlBIt/eb4M5+sk=; h=From:To:Cc:Subject:OpenPGP:Date:Message-ID:MIME-Version: Content-Type:From; b=qy4eTHybL/kg16DylV+TcDr2Cu5uXpxMh/WjmOi6z/nYF4g0Z55ic2Vavh4bAukh0 LKX2Mxq3lnIPdVQEh4iPYwJBPkt4lyoPuQj5Wp+wrrN/oOuNYvMzDQnsb3YIHAHOFn svKwDLDSv5inmJMMTN2PyBqCvgevT1pr6jZLAfTz3sY6GHAlvZD8CIItvvA1ssE62I 9NS0lyZ1/SqDBCorVRfEbsZdShVtWYcfaSOIDpxydQ+pT1z94fYWwSgLuDynf2iRaC ebFG9QBAjP49zekyo/tR3W9g+zWnl+1fBqBetA5Ztj5NeYW2miSH02nvhSemFDb3ZL kRA+zdvmKzJcw== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4VpMpx5Zz4z9rxL; Tue, 28 May 2024 08:21:29 +0200 (CEST) In-Reply-To: <86jzjfjfg0.fsf@gmail.com> (Elijah G.'s message of "Mon, 27 May 2024 12:08:15 -0600") OpenPGP: id=7126E1DE2F0CE35C770BED01F2C3CC513DB89F66; url="https://keys.openpgp.org/vks/v1/by-fingerprint/7126E1DE2F0CE35C770BED01F2C3CC513DB89F66"; preference=signencrypt X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:286077 Archived-At: "Elijah G." writes: > Philip Kaludercic writes: > >> Stefan Kangas writes: >> >>> tags 71180 - notabug >>> severity 71180 wishlist >>> thanks >>> >>> "Elijah G." writes: >>> >>>> Tags: notabug >>>> >>>> Hi, i'm wondering if would be a good idea add support for thumbnail for >>>> elpa packages (for elpa website and package-menu *Help* buffers). >>>> I think this is a missing feature that most other editors and non-editors >>>> does (such as synaptic and vscodium). >> >> I am not sure if you mean this as a kind of "logo" or as a kind of >> screenshot? I assume you mean the latter. > > I meant a screenshot. > >>>> My idea is to only support 1 image (jpg or png, adding more than 1 >>>> thumbnail would be hard to read the package *Help* buffer) and resize it >>>> (if possible) for not take all the buffer size. >>>> >>>> For packages developers i think would be fine define new header comment >>>> line for let them to choose which image they want to use, something like: >>>> ;;; Thumbnail: ./image.png >> >> If anything, I think it would be best to mandate SVG, which after all we >> can easily generate using (x-export-frames nil 'svg), if supported. >> That should solve the scaling issue. AFAIK we currently don't support >> animated SVGs in Emacs, right? That might be a nice feature for some >> packages. > > About animated screenshot/thumbnail i think that GIF images fits > better with this. The issue is that .gif is still a bitmap format, so we wouldn't have the advantage of scaling that vector graphics give us. As this is a feature that would only be added in a future version of Emacs, we could start another feature request to support SVG animations as well, perhaps even a way to record Emacs into such a animation. See https://en.wikipedia.org/wiki/SVG_animation for a few examples. >> Two points I am not fond of is that screenshots on sites like GitHub are >> often not uniform and contain a lot of noise. It would be nice if we >> could give some guidelines, or better yet generate the screenshots >> ourselves from a given sequence of keys. That might not be nice from a >> security or performance perspective and could still be circumvented. > > I agree about a guideline. It might even be worth considering restricting screenshots to GNU ELPA packages, so that the guidelines can be enforced more effectively. >> If we are talking about screenshots, that these aren't hard >> requirements to understand what a package does, just as describe-package >> can do its job now without the help of images. Visual examples should >> be regarded as an enchantment, where they make sense. > > Of course, the screenshot would be something optional, allowing > packages add a screenshot/thumbnail would make more easy watch what does > a package or what can do a package (instead going to their repository or > read its description). > > Here is a little mockup how i think it would look like in > package-describe *Help* buffer That seems like the screenshot is part of the README file? I would have imagined them before or after the file, perhaps even in a different buffer. > x > -- Philip Kaludercic on peregrine