<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Jul 20, 2013, at 5:04 AM, Burak Nehbit <<a href="mailto:burak@nehbit.net">burak@nehbit.net</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">Is there such a thing for Qt5? Is it planned?</span></blockquote></div><br><div>Well, it sounds like <i>you're</i> planning it, so, I guess so :).</div><div><br></div><div>I doubt that anyone on this list has plans to do it (or there would already be work qt5 work done in the qt reactor repository) but there are plenty of people (myself included) who would be very happy to help you learn enough about Twisted to do it yourself. And, honestly, if you're motivated to do it it's probably *not* a huge amount of effort to update the implementation. Feel free to ask any questions you have on this list.</div><div><br></div><div>In the meanwhile though, maybe you could report a bug to Nokia or Trolltech or whoever runs Qt development right now that they should stop gratuitously breaking interfaces between versions? We've had (at least one) major rewrite of the Qt reactor for every version of Qt, which seem to come out relatively frequently. Nothing about the nature of event loops or sockets has changed sufficiently in the meanwhile to justify the constant re-work that Qt seems to require from us.</div><div><br></div><div>-glyph</div><div><br></div></body></html>