[Kde-pim] [Job] K3Process should be replaced by QProcess

Sam Bishop sam at bishop.dhs.org
Mon May 28 18:58:03 BST 2007


Tom Albers wrote:
> Op zo 27 mei 2007 14:29 schreef u:
>> On Monday 21 May 2007 22:06:53 Ingo Klöcker wrote:
>> > On Monday 21 May 2007 09:55, Volker Krause wrote:
>> > > Ok, then let's try again ;-)
>> > > Here are some other small jobs I came across yesterday:
>> > >
>> > > kdepimlibs/mailtransport:
>> > > Add history for ad-hoc transports (manually entered urls like
>> > > smtps://me@myserver.org) to MailTransport::TransportComboBox.
>> > > KMail already does this manually in the composer, but it would of
>> > > course be nice if it would be available everywhere (ie. also in
>> > > Mailody and KNode) with the same data.
>> >
>> > Is this really useful? I wanted to get rid of this in KMail because
>> it's
>> > an easy source for errors (if the user accidentally changes
>> something).
>>
>> Well, no idea. I just didn't want to silently remove features from KMail
>> ;-)
>> Of course, without ad-hoc transports things would be a bit easier in
>> mailtransport. If it should be kept, some kind of input-validation would
>> certainly be useful.
>>
>> Personally, I've only needed it once for testing a newly installed
>> mailserver, so I wont object a removal.
>
> Mailody has not enabled the ad-hoc transports as I considered it too
> advanced for Mailody. So no objections here either.
>
> So there is a new job for someone !

I'll take this one too.  (The signal-throttling patch is nearly done.) 
Are there any other places besides the Mailody project where I ought to
look for uses of this, outside of the kdepim module?

Thanks,
Sam

_______________________________________________
kde-pim mailing list
kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/



More information about the kde-pim mailing list