From mboxrd@z Thu Jan  1 00:00:00 1970
From: SAKURAI Masashi <m.sakurai@kiwanami.net>
Subject: Re: New backend for org-agenda: (Was Calendar-like view of	the
 org-agenda)
Date: Wed, 20 Jul 2011 16:50:46 +0900
Message-ID: <20110720075047.13A8013C4EB@vps1.kiwanami.net>
References: <20110710154117.881A213C51B@vps1.kiwanami.net>
	<87fwmcar0u.fsf@gnu.org>
	<20110716162238.DC9D213C517@vps1.kiwanami.net>
	<87d3h7w5nd.fsf@gnu.org>
Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([140.186.70.92]:46993)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <m.sakurai@kiwanami.net>) id 1QjRYW-00041m-5e
	for emacs-orgmode@gnu.org; Wed, 20 Jul 2011 03:51:00 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <m.sakurai@kiwanami.net>) id 1QjRYR-0002u3-KQ
	for emacs-orgmode@gnu.org; Wed, 20 Jul 2011 03:50:55 -0400
Received: from vps1.kiwanami.net ([182.48.41.71]:49813)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <m.sakurai@kiwanami.net>) id 1QjRYQ-0002tO-U4
	for emacs-orgmode@gnu.org; Wed, 20 Jul 2011 03:50:51 -0400
In-Reply-To: <87d3h7w5nd.fsf@gnu.org>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: </archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: bzg@altern.org
Cc: emacs-orgmode@gnu.org

Hi Bastien,

At Tue, 19 Jul 2011 01:06:14 +0200,
Bastien wrote:
> :
> > 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.

What does '/per-se/' mean ?
Excuse me for asking a trivial word.

I'm also think about cache in the calfw side, such as an alist:
(date . [a list of contents]). Then, uses can refresh the cache
explicitly. It is easy to implement.

Is the plan(1) the same idea?


Regards,
--
SAKURAI, Masashi (family, given)
m.sakurai@kiwanami.net