[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] Usability help needed for KPilot
From:       Adriaan de Groot <adridg () cs ! kun ! nl>
Date:       2003-04-21 22:18:41
[Download RAW message or body]

On Monday 21 April 2003 21:53, Reinhold Kainhofer wrote:
> > Right. The idea is that this will eventually not be a dialog, but a page
> > inside KPilot itself.
>
> So what about "kpilot -c" then? And the "Configure Conduits..." menuitem of
> the kpilotDaemon RMB menu?

O yeah ... see, that's why I'm still working with the dialog. Seriously, 
changing pages like in KCM seems like a workable idea, and "OK" or "Cancel" 
in the dialog would be like switching away from that view in KPilot. You 
might get a confirmation message box when closing the dialog though.


> > See snapshot9.png (same address) for what I had in
> Would be nice if you could give us read permissions for that file on the

Picky, picky.

>
> > > Also, we should add a checkbox to enable the automatic backup of all
> > > changed databases (and add a list of databases that will be ignored).
> >
> > Fast sync was supposed to just run conduits, while normal sync is
> > supposed
> > backup (sync) all databases anyway.
>
> Ah, I always thought full sync would just ignore the changed flag of
> records on the handheld and walk through all records of each database to
> see if any has been changed since the last sync (e.g. because the handheld
> was synced with a differenc pc since then, so the changed flag was reset
> then).

Yes, but that's _full_ sync. There's three levels:

- fast, just do conduits
- normal, run conduits and sync other databases too (walk the 
pilotserialdatabase with readnextmodifiedrecord())
- full, when you can't trust the changed bits


> How about moving the backup action code to a separate "Backup conduit",
> which has its own config dialog (where you can give databases that will be
> ignored)? The user then can enable or disable it in the conduit
> configuration dialog.

Which backup action code? Right now there is none except for the full backup. 
I don't think it's a good idea to make the difference between fast and normal 
an issue for conduits. (There's actions, and there's conduits. All conduits 
are actions, but there's more actions than conduits. Welcome, cleanup, user 
check, those are all actions.)


-- 
pub  1024D/FEA2A3FE 2002-06-18 Adriaan de Groot <groot@kde.org>
     Key fingerprint = 934E 31AA 80A7 723F 54F9  50ED 76AC EE01 FEA2 A3FE
_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]