--===============6485598850698638690== Content-Type: multipart/signed; boundary="nextPart1537642.nS4goHeoUd"; micalg="pgp-sha1"; protocol="application/pgp-signature" --nextPart1537642.nS4goHeoUd Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" On Monday, December 1, 2014 10.34:33 Milian Wolff wrote: > Could this be added to KJobs instead of reinventing the wheel complet= ely? Or the API of KJob is a bit different from what is needed here, though KJo= bs may=20 be able to be used in the implementations. that said, a lot of what KJo= b does,=20 particularly the things like optionally updating a global job tracker G= UI and=20 suspension, is not directly relevant to the majority of use cases in kd= epim.=20 so ... kind of an awkward fit imo. KJob exists, +1; it is well known, += 1; it=20 doesn't really map to the use case here ... i'm reminded of kdepim's usage of kio everywhere once upon a time. it w= as=20 there, it was well known, it basically worked, but didn't really map to= the=20 use case ... what would really be useful in many cases is something not a job-orient= ed API=20 but a process flow oriented one, like several of the common patterns=20= implemented in this node library:=20 =09https://github.com/caolan/async we have some of these in C++ / Qt, but the various composition patterns= for=20 sets of tasks with sinks and generic error handlers are generally missi= ng in=20 our toolbox. these new classes could be folded into KCoreAddons at some point, thoug= h, if=20 they are found to be valuable and useful enough. and yes, they may even= use=20 KJobs internally or within the API .. the topics are a bit orthogonal i= n that=20 way. for more context and some experiments Christian did earlier in the year= , see: https://cmollekopf.wordpress.com/2014/10/03/putting-the-code-where-it-b= elongs/ =2D-=20 Aaron J. Seigo/opt/kde5/include/KF5/KCoreAddons/KJob --nextPart1537642.nS4goHeoUd Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEABECAAYFAlR8PD0ACgkQ1rcusafx20MN0wCfa5/6ZXIG3HkntsCJ93s7w2kD pZcAn1298O3t3SB6j9imaXpca6vKUeSW =Jpk+ -----END PGP SIGNATURE----- --nextPart1537642.nS4goHeoUd-- --===============6485598850698638690== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ KDE PIM mailing list kde-pim@kde.org https://mail.kde.org/mailman/listinfo/kde-pim KDE PIM home page at http://pim.kde.org/ --===============6485598850698638690==--