News for hackers. Stuff that matters.

A comment on Proton Native – React Native for the desktop. Parent comment

Re:Proton Native – React Native for the desktop by amelius on Wednesday May 02, 2018 @05:10PM (#16981189)
I used Qt in the early days, and always found the signal/slot model to handle events quite cumbersome. Handling events through closures (like typically done in JavaScript) is, imho, much nicer.
[ Parent | on HN ]
Re:Proton Native – React Native for the desktop by jcelerier on Wednesday May 02, 2018 @05:35PM (#16981354)
> I used Qt in the early days, and always found the signal/slot model to handle events quite cumbersome. Handling events through closures (like typically done in JavaScript) is, imho, much nicer.

You have been able to bind closures to events in Qt for... dunnno... 6 years maybe ?

[ Parent | on HN ]
Re:Proton Native – React Native for the desktop by drb91 on Wednesday May 02, 2018 @06:19PM (#16981653)
Perhaps ironically, Javascript is a first class qt/qml citizen these days. You’ve been able to use QML with javascript—including/mainly via closures—for a while now.
[ Parent | on HN ]
Re:Proton Native – React Native for the desktop by mnutt on Wednesday May 02, 2018 @10:37PM (#16982960)
I'm only an occasional Qt user but I believe since c++11 they've gained much better support for anonymous functions.
[ Parent | on HN ]