One could of course let Qt/C++ be "in charge" as he main loop and just run julia as an embedded engine and expose the julia functionality one wants to call as QtObjects & methods so that these can be called from QML.
On Friday, May 1, 2015 at 3:49:12 PM UTC+2, Steven Sagaert wrote: > > The idea would be to describe the GUI & it's behavior via QML/javascript. > Any julia modules/functions (event handlers) that need to be called from > the GUI could be exported as C++ QtObjects/methods (that's the hard part). > These can then be called from QML. Passing the QML to Qt & interpreting it > would be done by wrapping the QtQML C++ code with julia code. > > On Friday, May 1, 2015 at 2:58:06 PM UTC+2, Tom Breloff wrote: >> >> Steven... can you post a summary of how you would ideally interact with >> Qt5.jl? I assume you'd want clean syntax to define a gui with a QML string >> (or file), along with clean syntax to define signals/slots to connect to >> julia callbacks. Could you post some simple/hypothetical code that you >> would ideally call from within julia? This will help as I'm reading the >> Qt5 docs. Thanks. >> >> On Friday, May 1, 2015 at 4:59:43 AM UTC-4, Steven Sagaert wrote: >>> >>> I think it depends how you want to build the GUI: if you want to do it >>> "old school" by calling a bunch of julia functions/methods that wrap the >>> C++ methods than yes a lot of C++ classes/methods will need to be wrapped. >>> However if you stick to the "new school" approach i.e. QtQuick + QML then a >>> lot less C++ classes need to be wrapped and GUI construction would >>> basically be writing QML string and passing them from julia onto the Qt5 >>> side which then interprets it. So it that sense it's not that different >>> from say writing an SQL library wrapper like ODBC. >>> >>> On Thursday, April 30, 2015 at 10:59:32 PM UTC+2, Max Suster wrote: >>>> >>>> Good to hear interest. I will also have to look at what might be a good >>>> strategy for wrapping Qt5 with Cxx. The core functionality of Qt5 (shared >>>> by Qt4) would be an obvious place to start. The part that is clearly >>>> daunting is the interface for event handling, namely signals and slots. >>>> Not >>>> only we have to deal with/replace the underlying XML support, but also the >>>> syntax has changed a lot between Qt4 and Qt5. >>> >>>
