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

List:       kde-pim
Subject:    Re: [Kde-pim] Quo vaids KPilot
From:       David Bishop <david () bishop ! dhs ! org>
Date:       2001-10-29 22:48:14
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 29 October 2001 02:39 am, Adriaan de Groot wrote:
> I know -- and David reminded me -- that I'd said "mid-october" for a new
> KPilot release. Well, NOT. I'm pretty sure it could have been done if I'd
> continued working at the pace I was -- those heady halcyon days when David
> would send me a new .ui file every day, etc. Before my hardware broke.
> Before it turned out that converting conduits is less trivial than the
> NULL-conduit had suggested. Before I noticed that the KNotes conduit
> sucked.

I'm still up for sending you .ui files, just tell me what you want :-)  And I 
too noticed that the knotes conduit sucked (iirc, I was going to start 
converting conduits with that one. that was a mistake).

> Anyway, the KDE 3.0 freeze is coming closer. Please check the release
> schedule (somewhere under developer.kde.org) to see if your favorite
> feature <B><FONT SIZE=+15>that can feasibly be implemented</FONT></B>
> (preferably by you) is on the list, and to see if I've left anything out
> there (like the generalized PDB viewer?).

Well, my favorite feature is already implemented (working usb) so everything 
else is gravy.  

> As for the fabled KPilot 4.3.0 release for KDE 2.2, that's still what I'm
> aiming for, and yes, it really should be out Real Soon Now, assuming I can
> curb my enthusiasm for fiddling around with software RAID under freeBSD and
> new hardware and old hardware too (I've got a barcode scanner. What should
> I do with it?). Currently I'm really working on the address book conduit,
> and as soon as I get something together that can sync reliably using just
> that one conduit, I'll release KPilot 4.3.0 into the wild. 4.3.1 will then
> have the remaining conduits. I hope that will make it possible to get
> people using the new setup, and help find bugs in it, without having to fix
> all the conduits first. Of course, it will mean that KPilot will be kinda
> crippleware (one conduit? you gotta be kidding) for a short while.

Suggestion for bar-code scanner: label all your keys and instead of typing, 
use the scanner for input.  Or not......

As for the crippleware thing, those whose needs aren't satisfied by it, don't 
have to upgrade (very simple).  And I doubt the 4.3.x line will be snarfed up 
by distrobutions, so I don't see it as a concern.  

> [ade]
>
> PS. The TODO file has been updated, and gives a reasonable indication of
> the kinds of jobs that are lying around.

All the things in the TODO file sound hard :-(  And as easy as "learn c++" is 
to say, it's considerably more difficult to do .......

- -- 
D.A.Bishop
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE73dyvKEJ4huP2XBERAikqAKCSp/uGicO71+QChHUN11kBs/0PYgCeJsEQ
e7OyXweH6SDCK/cKmK7fFMo=
=0ba4
-----END PGP SIGNATURE-----
_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim

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