From: joakim@verona.se
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: emacs-tangents@gnu.org
Subject: Re: The xwidget branch origin story
Date: Thu, 26 Nov 2015 22:16:12 +0100 [thread overview]
Message-ID: <m3k2p4cvhf.fsf@exodia.verona.se> (raw)
In-Reply-To: <m2io4rm1am.fsf@newartisans.com> (John Wiegley's message of "Tue, 24 Nov 2015 15:21:21 -0800")
John Wiegley <jwiegley@gmail.com> writes:
>>>>>> Andy Moreton <andrewjmoreton@gmail.com> writes:
>
>> Emacs already has lisp/widget.el and lisp/wid-edit.el with a set of widget-*
>> functions used by customize.
>
>> Any name using widget will lead to confusion - please try to find a name
>> that does not clash with an existing feature.
>
> Andy makes an excellent point: "widgets" (without clarification) have a
> precise meaning, so "Emacs widgets" vs. "emacs-widgets" would cause a great
> deal of confusion.
>
> We need another name for these interactive objects that can be inserted into a
> buffer, whose functionality is not implemented by Emacs itself. Sort of
> like... hosted components, gadgets?
To demonstrate my lack of naming skills:
- ele : emacs linking and embedding. But thats a bit short for a unique
prefix
- elec : emacs linking and embedding controls
- eniac : emacs native interactive advanced controls
I guess I'll stop now.
But I think I need to do a rename soon, and it would be some work to get
it right, so I would like to have some consensus on a name before I do it.
>
> John
>
--
Joakim Verona
next prev parent reply other threads:[~2015-11-26 21:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-14 20:13 The xwidget branch origin story joakim
2015-11-20 19:23 ` John Wiegley
2015-11-20 19:31 ` Drew Adams
2015-11-20 19:38 ` John Wiegley
2015-11-22 13:56 ` joakim
2015-11-22 17:26 ` Michael Abrahams
2015-11-22 19:19 ` joakim
2015-11-22 20:02 ` Michael Abrahams
2015-11-22 20:10 ` John Wiegley
2015-11-22 20:13 ` joakim
2015-11-22 20:16 ` John Wiegley
2015-11-24 23:05 ` Andy Moreton
2015-11-24 23:21 ` John Wiegley
2015-11-24 23:28 ` Drew Adams
2015-11-25 0:47 ` John Wiegley
2015-11-26 21:16 ` joakim [this message]
2015-11-26 21:51 ` Iñigo Serna
2015-11-27 7:28 ` Eli Zaretskii
2015-11-27 0:33 ` Andy Moreton
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3k2p4cvhf.fsf@exodia.verona.se \
--to=joakim@verona.se \
--cc=andrewjmoreton@gmail.com \
--cc=emacs-tangents@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).