--nextPart1223662.WJvq3QodWq
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

I'd like to ask to go for another partitial lift of the freeze to add some=
=20
minor stuff for KDE 3.5.3. I for one would like to seize it to integrate=20
Will's great online status patches to KDE PIM and possibly add new ones for=
=20
other application in that module where appropriate (knode comes to my mind).

Details on that: SUSE/Novell has undergone a huge effort to make integrate=
=20
network manager, an effort to control your network connections from the=20
desktop, with KDE. network manager can signal the systems current online=20
status so applications can react properly, i.e. kmail will not try to send =
or=20
fetch messages.

SUSE 10.1, SLED 10 as well as Kubuntu Dapper are three distributions that w=
ill=20
support network manager. Others are likely to follow (I for one am already=
=20
drawn to it due to its ease of use :). I therefore think it's a good idea t=
o=20
have this technology in KDE 3.5 to let our users benefit from that advantag=
e,=20
since KDE 4.0 is still far away for our users and and this feature=20
enhancement is quite a low hanging fruit, thanks to Will's work.

Will has written a nice set of patches which are currently only applied to=
=20
SUSE rpms. One patches the networkstatus kded service, which currently stil=
l=20
resides in kdelibs, to listen to network manager via DBUS and then inform=20
attached applications via DCOP (the DCOP-API is in place for quite a while=
=20
IIRC). The other patches kmail and the SLOX-resource to remain to properly=
=20
communicate with networkstatus.

KMail is technically well prepared for offline handling since 3.5 and it wo=
uld=20
be easy to add it to other applications in KDE PIM that need it without=20
creating a big GUI string mess. If other application maintainers care, we=20
could also move it to libs, but I think that's quite a drastic change for a=
=20
minor release. Still, it would be nice to have since Kopete or even=20
Konqueror/khtml could profit from it. Since we're talking about a DCOP=20
service, the move is not strictly needed anyway.

What's your opinion

a) on the freeze lift?

b) on the network manager changes?

Cheers,
  Daniel

--nextPart1223662.WJvq3QodWq
Content-Type: application/pgp-signature

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

iD8DBQBEM7mFu1Wkf8kBwz4RAsffAKDu3lJ2mXDIK21W3jLx5Q5zxgr5TgCfVVPD
DXUODFOcTEqy9zfLdO950sg=
=Ehs8
-----END PGP SIGNATURE-----

--nextPart1223662.WJvq3QodWq--