From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Re: [ELPA] Package proposal: EBDB
Date: Tue, 01 Aug 2017 09:04:24 -0700 [thread overview]
Message-ID: <87fudbi8af.fsf@ericabrahamsen.net> (raw)
In-Reply-To: m2efsvx36c.fsf@newartisans.com
John Wiegley <jwiegley@gmail.com> writes:
>>>>>> "EA" == Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
> EA> It's a port/re-write of BBDB using the EIEIO libraries.
>
> Can you explain the benefit of including this work into Emacs? Specifically,
> does it solve problems being encountered with the current BBDB, or does it
> pave the way for new work?
It was originally meant to be a set of patches to BBDB, but snowballed
from there. My feeling was that the original package was inflexible, and
very difficult to extend. EBDB is made to be extensible: multiple
databases, an internationalization mechanism, hooks for integration into
other packages, subclassable records and fields that can have arbitrary
behavior... The code as it stands offers a few solid benefits over BBDB,
but most importantly there's a lot of room for building on top of it.
The class/generic method approach means that other packages could add
all kinds of new behavior to EBDB simply by being loaded.
Probably some of it did end up being new code for new code's sake...
I wasn't thinking of ELPA as "inclusion into Emacs", but maybe that's
what it is?
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> It's a port/re-write of BBDB using the EIEIO libraries.
>> Perhaps apropos of the recent copyright discussions: there's a fair
>> bit of BBDB code still in there.
>
> BTW, which BBDB are we talking about, here.
> Is it the BBDB v2, or BBDB v3?
>
>
> Stefan "presuming v3"
Yup, I started out with version 3.
Eric
next prev parent reply other threads:[~2017-08-01 16:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 19:18 [ELPA] Package proposal: EBDB Eric Abrahamsen
2017-07-31 0:49 ` Richard Stallman
2017-07-31 3:10 ` Eli Zaretskii
2017-07-31 3:12 ` Eric Abrahamsen
2017-07-31 3:28 ` Eli Zaretskii
2017-07-31 3:30 ` Eric Abrahamsen
2017-08-09 21:17 ` Eric Abrahamsen
2017-08-13 1:03 ` Eric Abrahamsen
2017-08-13 21:47 ` Stefan Monnier
2017-08-14 1:44 ` Eric Abrahamsen
2017-08-14 9:45 ` Stefan Monnier
2017-08-14 15:59 ` Eric Abrahamsen
2017-08-14 23:15 ` Stefan Monnier
2017-08-14 23:50 ` Eric Abrahamsen
2017-08-15 7:49 ` Stefan Monnier
2017-08-15 15:30 ` Eric Abrahamsen
2017-08-17 16:57 ` Eric Abrahamsen
2017-08-17 22:21 ` Stefan Monnier
2017-08-17 22:52 ` Eric Abrahamsen
2017-08-17 23:27 ` Stefan Monnier
2017-08-17 23:31 ` Eric Abrahamsen
2017-08-01 5:33 ` John Wiegley
2017-08-01 16:04 ` Eric Abrahamsen [this message]
2017-08-01 22:25 ` John Wiegley
2017-08-01 23:52 ` Eric Abrahamsen
2017-08-02 1:28 ` John Wiegley
2017-08-02 3:08 ` Eric Abrahamsen
2017-08-01 5:58 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2017-08-06 22:12 Roland Winkler
2017-08-07 0:44 ` Eric Abrahamsen
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=87fudbi8af.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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.