Re: [Evolution-hackers] Delete Calendar events

[Rodrigo Moya <rodrigo ximian com>]

On Wed, 2003-10-08 at 18:53, Ronald Kuetemeier wrote:
> On Wed, 2003-10-08 at 02:29, Rodrigo Moya wrote:
> > On Tue, 2003-10-07 at 19:03, Ronald Kuetemeier wrote:
> > > Hi Guys,
> > > has anybody given any thoughts to deleting calendar events and how the
> > > gui to it should look like?
> > > 
> > > Here are my history and some thoughts.
> > > I used to reverse delete calendar events, using a program which would
> > > create a new calendar file with events back 60 days from today and 1
> > > year in the future. This way I could archive my old calendar and just
> > > use the new file in future evolution sessions. 
> > > Pros: fast, simple, works, easy to archive. 
> > > Cons: Not very intuitive, have to shut down evolution to install new
> > > calendar file. 
> > > 
> > > Now there is another problem, one really doesn't know when the program
> > > is done (Ok one can look at the screen and see if there is any more
> > > output), but that's not easy to automate.
> > > 
> > > We could write a daemon which listens to calendar events and deletes old
> > > calendar entries.
> > > Pros: easy to write, auto start up
> > > Cons: hard to use for archiving, uses resources even when doing nothing.
> > > 
> > There is already a 'Purge' command in HEAD, which allows you to remove
> > old entries based on a date. It could have a way to allow users to
> > archive the entries somewhere if they want to.
> > 
> > > Now I thought doing the following, write the daemon but create a new
> > > calendar file with all the entries which should be deleted, then count
> > > the entries in the new calendar file. Now since we have a count we know
> > > when we are done (daemon exit) and can delete the entries which are in
> > > the new file from the org. calendar.
> > > This way the daemon can run on a timely basis and run in parallel to 
> > > evolution and create archive files. No Gui.
> > > 
> > hmm, is there really a need for that daemon if we've got the 'archive'
> > option in Purge?
> 
> My guess is not, but you defiantly want to implement an archive feature.
>
yes, of course, we want an archive feature. I was just saying there is
no need for the daemon. We can either have a menu option, to have the
user archive when she wants, or have the calendar code do the archiving
on startup/exit/modification/whatever.

> I basically archive every 6mth in a separate file.
> Anyhow, keep in mind I'm working against 1.4.5.
>
if we add the archiving feature, of course that will be for 2.0 :-)

cheers