--===============16936568329285651==
Content-Type: multipart/signed;
  protocol="application/pgp-signature";
  micalg=pgp-sha1;
  boundary="Boundary-02=_yAn3+biglJ2a8Mu";
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit


--Boundary-02=_yAn3+biglJ2a8Mu
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Wednesday 04 June 2003 10:48, Don Sanders wrote:
> This is because majority of the KMail Kernel code is GUI free in the
> sense that it never blocks on user input. There are some exceptions,
> I see two calls to KMessageBox::sorry in kmfoldermaildir.

In kmfoldermbox there are also some message boxes.

> These exceptions are unfortunate regressions and it would be nice to
> eliminate them. It seems to me that this is basically what your patch
> is doing but for kmaddrbook instead of kmfolder.
>
> That leads me to a question is kmaddrbook part of the KMail kernel
> code? I think this question is basically equivalent to can any of the
> kmaddrbook.cpp code be hit when KMail is being run as server process?
> (That's an actual not a hypothetical question).

After a quick research I'm convinced that the kmaddrbook.cpp code (which
consists of two classes with only static member functions) won't be
called by the server.

KMAddrBookExternal is only used here:
kmcommands.cpp:  KMAddrBookExternal::addEmail( KMMessage::decodeMailtoUrl( mUrl.path() ), mParent );
kmcommands.cpp:  KMAddrBookExternal::openEmail( KMMessage::decodeMailtoUrl( mUrl.path() ), mParent );
kmcomposewin.cpp:  KMAddrBookExternal::launch(this);
kmmainwidget.cpp:  KMAddrBookExternal::launch(this);
vcardviewer.cpp:  if (KMAddrBookExternal::addVCard(mAddressee, this))

KabcBridge is only used here:
kmcomposewin.cpp:    mMsg->setTo( KabcBridge::expandDistributionLists( to() ));
kmcomposewin.cpp:    mMsg->setCc( KabcBridge::expandDistributionLists( cc() ));
kmcomposewin.cpp:      mMsg->setBcc( KabcBridge::expandDistributionLists( mBcc ));
kmcomposewin.cpp:      mMsg->setHeaderField( "X-KMail-Recipients", KabcBridge::expandDistributionLists( recips ) );
kmcomposewin.cpp:      msg->setTo( KabcBridge::expandDistributionLists( to() ));
kmcomposewin.cpp:      msg->setCc( KabcBridge::expandDistributionLists( cc() ));
kmcomposewin.cpp:      msg->setBcc( KabcBridge::expandDistributionLists( bcc() ));
kmcomposewin.cpp:        msg->setHeaderField( "X-KMail-Recipients", KabcBridge::expandDistributionLists( recips ) );

Regards,
Ingo


--Boundary-02=_yAn3+biglJ2a8Mu
Content-Type: application/pgp-signature
Content-Description: signature

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

iD8DBQA+3nAyGnR+RTDgudgRAslbAJ97PDD9A5F+4a1JQ38vLNkC1RhXAACfQjS3
tCqBZ/9+HVbuiVT2kqgqlZM=
=iJ6q
-----END PGP SIGNATURE-----

--Boundary-02=_yAn3+biglJ2a8Mu--

--===============16936568329285651==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail

--===============16936568329285651==--