From: "Elijah G." <eg642616@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 71180@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#71180: [ELPA Feature Request] Package thumbnail
Date: Mon, 27 May 2024 12:08:15 -0600 [thread overview]
Message-ID: <86jzjfjfg0.fsf@gmail.com> (raw)
In-Reply-To: <87plt8x2ev.fsf@posteo.net> (Philip Kaludercic's message of "Sun, 26 May 2024 11:01:28 +0000")
[-- Attachment #1: Type: text/plain, Size: 2397 bytes --]
Philip Kaludercic <philipk@posteo.net> writes:
> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> tags 71180 - notabug
>> severity 71180 wishlist
>> thanks
>>
>> "Elijah G." <eg642616@gmail.com> 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.
> 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.
> 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
[-- Attachment #2: elpa-thumbnail.png --]
[-- Type: image/png, Size: 58219 bytes --]
next prev parent reply other threads:[~2024-05-27 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 22:30 bug#71180: [ELPA Feature Request] Package thumbnail Elijah G.
2024-05-26 9:23 ` Stefan Kangas
2024-05-26 11:01 ` Philip Kaludercic
2024-05-27 18:08 ` Elijah G. [this message]
2024-05-28 6:21 ` Philip Kaludercic
2024-05-30 3:10 ` Elijah G.
2024-06-02 19:41 ` Philip Kaludercic
2024-05-27 2:15 ` Elijah G.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86jzjfjfg0.fsf@gmail.com \
--to=eg642616@gmail.com \
--cc=71180@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
--cc=stefankangas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.