From: "Evgeny M. Zubok" <evgeny.zubok@tochka.ru>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: debbugs.el
Date: Fri, 25 Feb 2011 19:51:29 +0300 [thread overview]
Message-ID: <87sjvcvyzy.fsf@tochka.ru> (raw)
In-Reply-To: <87zkpkmlhc.fsf@gmx.de>
Michael Albinus <michael.albinus@gmx.de> writes:
>> One year old screenshot:
>>
>> http://s006.radikal.ru/i214/1001/d1/08ef5f85246e.png
>
> That includes both frontend and backend. For better exploitation,
> debbugs.el is intended to offer backend functionality only, it does
> not care about any UI.
> I've also written a frontend similar to what you have done, but it is
> based on widgets instead of outline mode. Like yours, it is
> unfinished.
My solution is also have a layered architecture: (i) a separate package
with generic SOAP client library; (ii) a separate package with
debbugs-soap.el as backend; (iii) debian-bts mode as a frontend. One of
my initial design consideration was to allow custom
frontends. debbugs-soap.el backend is very small library. It only
performs the requests to Debbugs server such as: get_bugs, get_status,
get_versions, get_bug_log, etc. All mbox functionality currently
implemented in frontend. I think it's a good idea to move it into
backend as alternative (to SOAP) method of receiving logs from server.
> That's how I also started mid of 2009. Last year, I switched to
> soap-client.el (recently added to Emacs' trunk). My code is much less
> ugly now.
This library appeared at the same time with my library. I was going to
prepare my soap-client.el for Emacs but someone is way faster than
me. :) Well, I will help soap-client.el from 'trunk' with patches. :)
>> I want to start hacking again and hope to finish it some day. :)
>
> Let's do it together. We could merge the backend functionality into
> debbugs.el, and continue to work on the different frontends. As I have
> said already, I would also be interested in an nnir integration.
Is your project published somewhere?
next prev parent reply other threads:[~2011-02-25 16:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8762sa9770.fsf@gmx.de>
[not found] ` <87pqqibr30.fsf@stupidchicken.com>
[not found] ` <87mxllambw.fsf@marauder.physik.uni-ulm.de>
2011-02-24 11:33 ` debbugs.el Michael Albinus
2011-02-24 23:44 ` debbugs.el Evgeny M. Zubok
2011-02-25 10:55 ` debbugs.el Michael Albinus
2011-02-25 16:51 ` Evgeny M. Zubok [this message]
2011-03-01 10:15 ` debbugs.el Michael Albinus
2011-03-02 15:56 ` debbugs.el Evgeny M. Zubok
2011-02-25 3:37 ` debbugs.el Lars Ingebrigtsen
2011-02-25 8:17 ` debbugs.el Eli Zaretskii
2011-02-25 8:33 ` debbugs.el Michael Albinus
2011-02-25 8:54 ` debbugs.el Eli Zaretskii
2011-02-25 9:29 ` debbugs.el Miles Bader
2011-02-25 9:55 ` debbugs.el Eli Zaretskii
2011-02-25 15:43 ` debbugs.el Stefan Monnier
2011-02-25 15:52 ` debbugs.el Eli Zaretskii
2011-02-25 9:59 ` debbugs.el Lars Ingebrigtsen
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=87sjvcvyzy.fsf@tochka.ru \
--to=evgeny.zubok@tochka.ru \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).