[Kde-pim] KDE Addressbook on an Appliance

[Anne Wilson]

On Tuesday 04 May 2010 21:31:22 Ingo Klöcker wrote:
> > There's a good deal of confusion around, about this.  On this laptop,
> > for instance, it was brand-new, therefore a clean install.  When I
> > started kontact, it carried out first-run.  At that point I had no
> > addressbok set up - so I ended up with an empty
> > ~/.local/share/contacts.  At that point I'm left guessing.  And I
> > might say, that I've seen other users perplexed at the same point.
> 
> Guessing? Guessing what?
> 
What to do next.  They know this is something new.  New things are often 
fragile.  There is a natural fear of doing something that may interfere with 
the proper working of the new system.

> > In fact I copied my std.vcf from the old laptop, set it as an
> > addressbook, then simply copied all the entries into Personal
> > Contacts.  As far as I can tell there were no ill effects.  But
> > users shouldn't be left guessing like this.
> 
> I'm not sure where you are getting at. What are you trying to tell us? 
> What should we do differently/better?

There needs to be some easily understood documentation to give the simplest 
possible setup.  At the moment, a clean install leaves you with an empty 
addressbook, and no documented way of filling it, other than entering each 
record by hand.

If you do it the way I did, you have two addressbooks, and then have to go 
through the process of marking one of them as default.  Anyone who tries to 
remove the std.vcf after simply copying across the entries is likely to find 
that he can't, because it could well be being seen as the default.  Of course 
it's all editable, but it's a hassle that should be avoided.

IMO what would really help is if the first run could register whether it found 
any records to migrate.  If it didn't, it should re-run at the next boot - and 
each time until it actually finds records.  That would allow for users to 
panic and close the addressbook because it's empty, realise that the old one 
has to be made available, fix that, and still have an automatic migration.

Of course it's easy to tell others what to do :-)  I would have thought that 
just setting a flag might accomplish this, but if it's not so easy, I 
apologise.  I'm simply reflecting the problems that some users have reported.

Anne
-- 
KDE Community Working Group
New to KDE Software? - get help from http://userbase.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20100505/30b21ec6/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/