Re: New to list.Would like to help with kpilot

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

Am Freitag, 31. Mai 2002 16:28 schrieben Sie:
> My suggestion would be a malsync conduit. It's the only thing keeping me
> using jpilot right now. Oh and password-enabled syncing, but I'm hoping to
> looking into that myself this weekend. (after learning C++ - give me a
> while...)

Right, that's another one. I don't think it would be too hard to write (the 
libmal already provides everything to talk to AvantGo et al.). The only 
problem is, there is no documentation how to write a KPIlot conduit... (The 
one that exists is terrible out of date and no longer applicable) You have to 
learn from looking at the existing conduits.

Some time ago I started a JPilotPluginProxy conduit which would allow kpilot 
to use JPilot plugins. I was even able to sync AvantGo (although KPilotDaemon 
crashed after the sync). The problem is, every dialog(box) the JPilot plugins 
use, needs gtk and thus it's own message loop for event handling. So what 
needs to be done for the JPilot plugin proxy is to implement it as a separate 
application which is included in the KPilot conduit dialog via xparts. That 
separate application the would use QGtkWidget and QGtkAppliation, so that 
means diving deep into the internals of kde and gtk... Currently I simply 
don't have the time to work on that.

Reinhold

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE894yiTqjEwhXvPN0RAq9RAKCRA6DKBmZoEZTCtN+B/NS/nbSB8ACeMejR
vbLsyRic57r4CbX2DLfzOlg=
=1pyT
-----END PGP SIGNATURE-----
_______________________________________________
kde-pim mailing list
kde-pim@xxxxxxxxxxxx
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/