Migrating Qt Crytpographic Architecture to KDE CVS

[Waldo Bastian]

On Thursday 30 September 2004 16:56, Jason Keirstead wrote:
> > The most important reasons for
> > putting the code in TCPSlaveBase directly were:
> > 1) it was the only potential user at that time, and it needed to be
> > transparent
> > 2) there were issues with where dialogs come from, synchronization, etc.
>
> For those who don't want to bother, the gist of it is that KSSL is in
> kdecore, and you can't put the code that calls to the UI server to create
> the dialogs in kdecore, because then kdecore would depend on kdeui.

KSSL is in KIO. However, KSSL is mostly used by the io-slaves and it's not 
such a good idea to do dialogs in the io-slaves themselves.

Cheers,
Waldo
-- 
bastian at kde.org  |  Wanted: Talented KDE developer  |  bastian at suse.com
  http://www.suse.de/de/company/suse/jobs/suse_pbu/developer_kde.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20040930/667dd3e6/attachment.sig>