all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mauro Aranda <maurooaranda@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Bryce Carson <bovine@cyberscientist.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Community improvements to the Emacs Widget Library manual?
Date: Sun, 9 Jul 2023 09:02:38 -0300	[thread overview]
Message-ID: <739c05a4-7a64-872a-bd5e-972eb8a90346@gmail.com> (raw)
In-Reply-To: <83sf9xbqqb.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

 >> Date: Sat, 8 Jul 2023 14:18:21 -0600
 >> From: Bryce Carson <bovine@cyberscientist.ca>
 >>
 >> Would anyone like to collaborate to improve The Emacs Widget Library
 >> manual? Are there any active
 >> Emacs Lisp hackers that actually understand this library at a deep 
level?
 >
 > I think Mauro (CC'ed) is our widget expert.

Thank you for CCing me, Eli, although I'm pretty sure I'm far from an
expert.

 >> The Emacs Widget Library manual could use a re-write, preferably
 >> following the Diataxis
 >> documentation framework if possible. Does anyone want to collaborate
 >> over the long-term, creating a
 >> study group and editing the manual to a high standard to benefit the
 >> community and ourselves?
 >
 > I don't think I understand the plan in this aspect.  If important
 > information is missing from the manual, it can and should be added.
 > If you want to add tutorial-style sections, that could also be a good
 > idea, provided that the subject is so complex that reading the main
 > description is too hard without first reading a tutorial introduction.

I think the manual lacks more information about how to do more
"advanced" stuff.  It's not hard, but I feel like some ideas about
what one can do with widgets only pop up after reading the code. Which
of course is really useful, but the manual could do a better job so it
isn't as required as of now.

That would fall in the category of adding tutorial-style sections, I
think.  I'd love to help with that, but I don't have much time available
to do it on my own.




  reply	other threads:[~2023-07-09 12:02 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-08 20:18 Community improvements to the Emacs Widget Library manual? Bryce Carson
2023-07-09  5:26 ` Eli Zaretskii
2023-07-09 12:02   ` Mauro Aranda [this message]
2023-07-09 12:16     ` Eli Zaretskii
2023-07-11  0:52   ` Bryce
2023-07-12 12:30     ` Eli Zaretskii
2023-07-12 16:42       ` Corwin Brust
2023-07-13 23:05         ` Bryce Carson
2023-07-13 23:27           ` [External] : " Drew Adams
2023-07-13 23:57             ` Bryce Carson
2023-07-10  3:38 ` Michael Heerdegen
2023-07-11 23:17   ` Bryce
2023-07-12  5:18     ` Michael Heerdegen
2023-07-12  7:21       ` Bryce
2023-07-13  2:59         ` Michael Heerdegen
2023-07-11 11:04 ` Kjartan Oli Agustsson
2023-07-14  2:02   ` Richard Stallman
2023-07-14  5:28     ` Bryce Carson
  -- strict thread matches above, loose matches on Subject: below --
2023-07-09 12:17 Mauro Aranda
2023-07-12  4:07 ` Bryce
2023-07-12 11:34   ` Mauro Aranda
2023-07-13  3:30     ` Michael Heerdegen
2023-07-23 23:06   ` Bryce
2023-07-24 11:37     ` Eli Zaretskii
2023-07-12 11:43 Mauro Aranda
2023-07-12 20:17 ` Bryce
2023-07-14  6:32 ` Bryce Carson
2023-07-14  6:52   ` Bryce Carson
2023-07-14  6:56     ` Bryce Carson
2023-07-14  6:59       ` Bryce Carson
2023-07-14  7:07         ` Bryce Carson
2023-07-14 14:41     ` Mauro Aranda
2023-07-14 18:50       ` bovine
2023-07-15  0:08         ` Mauro Aranda
2023-07-14 10:48   ` Mauro Aranda

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=739c05a4-7a64-872a-bd5e-972eb8a90346@gmail.com \
    --to=maurooaranda@gmail.com \
    --cc=bovine@cyberscientist.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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.