[Gpe-list] Rationalising tasks databases
mpalmer at hezmatt.org
Sat Dec 30 23:45:46 CET 2006
On Sat, Dec 30, 2006 at 10:44:56PM +0100, Neal H. Walfield wrote:
> At Sat, 30 Dec 2006 21:55:14 +1100,
> Matthew Palmer wrote:
> > The first thing to do is to rationalise the databases, so that the timesheet
> > tasks can be stored in the tododb. As far as I can tell, the only database
> > field that's missing from the tododb when compared to the timesheet db is
> > the parent task ID. This seems like a fairly simple change to make to
> > libtododb.
> Personally, I'd like to see libeventdb be a bit generalized so that it
> can handle both events and todos. First, semantically, there is not
> that much separating them.
That would solve another (far less important) problem I found in the PIM
suite -- that tasks with due dates don't show up on the calendar.
> If you find this approach reasonable,
I do. It seems like it'd be a big win. A fair bit more work, but the
benefits are significant.
> the first thing to do is to take a look at libeventdb's API and articulate
> what extensions are required to manipulate todos and how (and when) to
> distinguish them for events.
<clickety-click> And off I go...
I don't do veggies if I can help it. -- stevo
If you could see your colon, you'd be horrified. -- Iain Broadfoot
If he could see his colon, he'd be management. -- David Scheidt
More information about the Gpe-list