From: Matthew Sauer <improv.philosophy@gmail.com>
To: Bastien <bzg@altern.org>
Cc: SAKURAI Masashi <m.sakurai@kiwanami.net>, emacs-orgmode@gnu.org
Subject: Re: New backend for org-agenda: (Was Calendar-like view of the org-agenda)
Date: Mon, 18 Jul 2011 18:20:09 -0500 [thread overview]
Message-ID: <CALRk1sbsrhA_EA4Cdhhc-DTohepKqHackOxTDRkA6UtfGimeHg@mail.gmail.com> (raw)
In-Reply-To: <87d3h7w5nd.fsf@gnu.org>
Bastien,
What I am hearing is that an API that allows caching could be built
that could benefit extensions and then once that is deemed stable
enough an optional or separate track would be rebuilding the Agenda as
it is today into that API?
Matt
On Mon, Jul 18, 2011 at 6:06 PM, Bastien <bzg@altern.org> wrote:
> Hi Masashi,
>
> SAKURAI Masashi <m.sakurai@kiwanami.net> writes:
>
>> I'm sure that the caching mechanism is useful, but I'm not sure that
>> we should do it with paying the large cost of rewrite whole codes.
>
> FWIW, this is a two separate steps process: 1) write a usable cache,
> then 2) re-implement (parts of) the agenda by using it.
>
> I think (1) could be interesting /per-se/ and if it helps calfw, then
> it's even more interesting.
>
> 2 cents,
>
> --
> Bastien
>
>
next prev parent reply other threads:[~2011-07-18 23:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 15:41 New backend for org-agenda: (Was Calendar-like view of the org-agenda) SAKURAI Masashi
2011-07-12 7:37 ` Bastien
2011-07-16 16:22 ` SAKURAI Masashi
2011-07-18 23:06 ` Bastien
2011-07-18 23:20 ` Matthew Sauer [this message]
2011-07-18 23:54 ` Bastien
2011-07-20 7:50 ` SAKURAI Masashi
2011-07-20 12:43 ` Rasmus
2011-07-20 13:31 ` New backend for org-agenda: Giovanni Ridolfi
2011-07-21 4:38 ` New backend for org-agenda: (Was Calendar-like view of the org-agenda) SAKURAI Masashi
2011-07-21 9:52 ` Bastien
2011-07-23 2:35 ` SAKURAI Masashi
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALRk1sbsrhA_EA4Cdhhc-DTohepKqHackOxTDRkA6UtfGimeHg@mail.gmail.com \
--to=improv.philosophy@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=m.sakurai@kiwanami.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).