Re: Difference between EBDB and BBDB

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Drew Adams <drew.adams@oracle.com> writes:

>> > Just food for thought:
>> >
>> > It's good to be able to separate the use (UI, UX or
>> > whatever) from the database itself - form of records
>> > etc.  Regardless of whether it's BBDB or whatever
>> > else might come along or already exists out there
>> > somewhere.
>> 
>> That was absolutely my first principle in making this package: the
>> classes responsible for storage and behavior have nothing to do with the
>> interface presented to the user. In fact, ebdb.el should be usable as an
>> API for other packages, while ebdb-com.el should only be responsible for
>> the ebdb-mode buffers. I wouldn't be surprised if I've screwed up this
>> separation somewhat, but that was the original idea, and I will fix
>> relevant bugs!
>> 
>> > A generic way for a user to define her own
>> > record-to-record mapping (for whatever storage form)
>> > could help.  It could be a mapping for one-time
>> > conversion or a mapping to use at runtime to access
>> > another database directly.
>> 
>> While the documentation doesn't go into this at this point, this is
>> precisely how the whole system works, right down to the "generic" term:
>> `cl-defgeneric' is basically how you take control of the whole system.
>
> The curmudgeon has nothing more to say.  Good job!

I hope it actually lives up to these principles :)