Re: an idea

Hello!

nobody wrote:
> I’ve been watching the list for a while. And the way
> something’s are implemented seem like they could be
> done a lot simpler.

Be careful, many things _are_ really more complicated
than they look like.

> You start out with a few basic types:
>
> Notes – Just Text
> Appointments – Information on a date & time
> Contacts – Contact information

Some things are really handled in this way, but the
possebinities are limited with this approach.

> They every thing is constructed by relating them
>
> A Task would comprise of a Note, some other
> information like amount completed.
> An Email would be a Note and a contact(s)

This is one point you could get into trouble:
A contact can have many emails, therfore you'll need
additional information to point a single email
(or more) to send this mail to. If you think about
access control the situation becomes worse. How to handle
if you are allowed to see somone elses contacts but not
his notes?

> Any item could have any number of other related items
> i.e. a task could have a number of number of contacts
> and appointments

Another problem is that you have to decide what an
email is - you could want to attach a contact to a
note without the idea to create an email. It would
be possible to handle this, i only want to show that
it's not so easy how it looks like. But we should
keep this idea in mind.

Greetings

Florian

-- 
The dream of yesterday                  Florian Boor
is the hope of today                    Tel: 0271-771091-14 | Fax:0271-771091-19
and the reality of tomorrow.            florian.boor_at_kernelconcepts.de | boor_at_unix-ag.org
[Robert Hutchings Goddard, 1904]        6C 44 30 4C 43 20 6B 61  16 07 0F AA E6 97 70 A8