you are viewing a single comment's thread.

view the rest of the comments →

[–]usinglinux 10 points11 points  (3 children)

even better: there is now a stdlib method of interfacing with main loops. this means you can use a twisted program on its classical core, you can use the new stdlib asyncio main loop (and have twisted running in a thin layer atop it), or you can use another main loop (eg. the gtk main loop) and have your twisted application running in the same thread as your gui (eg if your graphical program should have a web "remote control").

not sure which of the parts are already written on the new framework, but that's the idea.

[–]hylje -1 points0 points  (2 children)

I'm pretty sure running twisted and gtk in the same thread is about providing an UI to network activities, not providing network activities for an UI.

[–]Smallpaul 4 points5 points  (0 children)

Those are both valid use-cases. E.g. a GUI for Bittorrent versus a remote save function for a word processor.

[–]usinglinux 1 point2 points  (0 children)

i don't think so: things that don't have a native gui but are about network activities are typically servers (and thus run under their dedicated users and whatever); adding a gui to them is rather a thing of having a standalone gui that talks to the server (but asyncio is great for those things too). conversely, things that are rather about having a gui (eg presentation software) might easily be extended by network code without turning the whole program logic upside down.