[Fwd: Re: PIM Schema ideas]

Data elements like what field should be displayed etc probably do not
belong within a globel schema as they are likly to only ever be related
to the one application. ?

In a situation like this I think my approch would be to create views
related directly to your apt .. In the event that your apt is unistalled
it should be a very simple matter to remove these views from the schema?

It should be very easy to have a user interface that allows users to add
or remove fields from that view.

maybe even use a config schema instead of the traditional rc file for
this sort of thing ?

just ideas ?

On Thu, 2002-06-06 at 02:37, Tom wrote:
> On Thu, Jun 06, 2002 at 01:02:13AM -0400, Dave A Hall wrote:
> > GPE Contact Schema
>
> two points, both of them slightly related to the very-unfinished
> contacts app that I started a while ago and that's since moved into the
> gpe CVS.
>
> a) seriously, how many *gpe* contact apps will there ever be? are we
> talking about 2-3 or 500? the amount of generality and extension scheme
> should, IMHO, reflect that. no need to create levels of abstraction
> that nobody will ever use.
>
> b) the scheme as proposed is not extensible enough as it only contains
> new fields. however, even the unfinished contacts app I wrote already
> has need for non-field extensions. in this case, a definition of which
> fields should be displayed on the first page in "view".
>
>
> --
> New GPG Key issued (old key expired):
> http://web.lemuria.org/pubkey.html
> pub 1024D/2D7A04F5 2002-05-16 Tom Vogt <tom_at_lemuria.org>
> Key fingerprint = C731 64D1 4BCF 4C20 48A4 29B2 BF01 9FA1 2D7A 04F5
> _______________________________________________
> GPE mailing list
> GPE_at_handhelds.org
> http://handhelds.org/mailman/listinfo/gpe
>
Received on Thu Jun 06 2002 - 07:13:11 EDT