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

List:       kde-pim
Subject:    Re: [Kde-pim]  KPilot TODO
From:       Adriaan de Groot <adridg () cs ! kun ! nl>
Date:       2003-04-12 15:54:14
[Download RAW message or body]

On Saturday 05 April 2003 15:21, Reinhold Kainhofer wrote:
> On Friday 04 April 2003 23:00, Adriaan de Groot wrote:
> > 'K folks, just in case people missed it: Reinhold and I (the main KPilot
> > developers) currently have personal issues that are taking up 100% of our
> > time.
>
> Well, my issues take up almost all of my time. Still, I intend to work on
> kpilot as much as my limited time permits. Thus, I made a large todo list
> with everything that needs/should/might be done in kpilot and its conduits
> and rated them according to their priority (as I see it).

The baby is sleeping (I _tried_ to name her so her initials would turn out to 
be KDE, but mom vetoed that for good reasons). So I have a little time to 
deal with the KPilot TODO.

> Essential
> =========
> 1)  VCal conduit: Currently using the ResourceCalendar (standard
>     calendar) doesn't work for some (unknown) reason. Every sync
>     happens with the filename given in the setup dialog. Probably
>     very easy to fix.

What irritates me a little is that the HEAD vcal conduit is totally 
incompatible with previous KDE versions. This is because of the new resource 
framework, of course, but it does mean a considerable code fork and support 
burden. 

> 2)  Redesign the config dialog of kpilot (get rid of deprecated
>     options, include conflict resolution, etc.)

OK, I'm on this one. I want to redo KPilot's look _anyway_ to integrate all 
the different parts - log, database viewers, config - into the KJanusWidget 
and make it clear what is editable and what not. I'm going to do that in 
HEAD. 

> 11) Merge between HEAD and BRANCH (again).

This has been done for lib/ and kpilot/ ; there's not much point in doing it 
for conduits. I have the feeling that the bugs that need attention now need 
new strings as well; I'm going to start working in HEAD again and consider 
BRANCH done. We'll need to split the KPilot tarballs up more now: build for 
KDE 3.0, 3.1, 3.2, kpilot sources, and conduit sources for KDE 3.[01] and KDE 
3.2. 

> 16) Remove the edit capabilities from the built-in viewers.

Combine with #2.

> 17) Include a calendar viewer, or get rid of the internal viewers
>     altogether.

I'd call this a GJJ and it can be combined into #2.

> 21) GJJ: Hunt down and kill printfs. Hunt down bad i18n.

Printfs are now isolated in various conduits - popmail is bad, as is JPilot. 
PalmDoc, expense and malconduits have isolated printfs that look ok. Bad i18n 
is something a non-english user will have to complain about, and the TL teams 
have pointed out most of the problems already.

> 23) GJJ: Move the conduit configuration dialog (for the umpteenth time)
>     to a list of QCheckBoxes, like noatun's plain playlist or
>     kdebugdialog

Part of #2.

> 38) Should interactiveSync and syncStack be moved to lib/ ?

Yes.

-- 
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]