{"action":"closed","issue":{"url":"https://api.github.com/repos/opencor/opencor/issues/908","repository_url":"https://api.github.com/repos/opencor/opencor","labels_url":"https://api.github.com/repos/opencor/opencor/issues/908/labels{/name}","comments_url":"https://api.github.com/repos/opencor/opencor/issues/908/comments","events_url":"https://api.github.com/repos/opencor/opencor/issues/908/events","html_url":"https://github.com/opencor/opencor/issues/908","id":137076772,"number":908,"title":"Qt: switch to Qt WebEngine","user":{"login":"agarny","id":602265,"avatar_url":"https://avatars.githubusercontent.com/u/602265?v=3","gravatar_id":"","url":"https://api.github.com/users/agarny","html_url":"https://github.com/agarny","followers_url":"https://api.github.com/users/agarny/followers","following_url":"https://api.github.com/users/agarny/following{/other_user}","gists_url":"https://api.github.com/users/agarny/gists{/gist_id}","starred_url":"https://api.github.com/users/agarny/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/agarny/subscriptions","organizations_url":"https://api.github.com/users/agarny/orgs","repos_url":"https://api.github.com/users/agarny/repos","events_url":"https://api.github.com/users/agarny/events{/privacy}","received_events_url":"https://api.github.com/users/agarny/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-02-28T17:47:47Z","updated_at":"2016-11-16T14:30:29Z","closed_at":"2016-11-16T14:30:29Z","body":"We are currently using Qt 5.4.2 (see issue #710 for the rationale behind it), but with Qt 5.6 around the corner (to be released on 3 March 2016), we might want to think about upgrading to version 5.6 (keeping in mind the issues that prevented us from moving away from Qt 5.4.2 in the first place, e.g. issue #706). This will also address issue #514 (i.e. use Qt WebEngine rather than Qt WebKit, which is not shipped with Qt anymore, although it can still be built from source). Otherwise, another reason for upgrading to Qt 5.6 is that Qt 5.4.2 doesn't officially support Windows 10. So, although we can use OpenCOR on Windows 10, we do get a warning that reads `Qt: Untested Windows version 10.0 detected!`\n\nAs of 19 April, we still need to do the following:\n- [x] Get OpenCOR to work on our Windows VM.\n- [ ] Get OpenCOR to work on our Linux VM.\n- [x] Deploy Qt WebEngine on Windows.\n- [ ] Deploy Qt WebEngine on Linux.\n- [ ] Get the `CellMLAnnotation` view to properly rely on Qt WebEngine.\n- [ ] `PMR` window: address the issue (on a vanilla Windows VM only?) that makes the contents of the `PMR` window to be the same as that of the `Help` window (this is clearly linked to the fact that we are now using Qt WebEngine...).\n- [ ] `Single Cell` view (OS X only): address problem of the black graph window flashing crazily (e.g. simulate the N62 model with one or several graphs and with a 200,000 slow down, on my MacBook Pro at least). (Might want to get the latest fixed for Qwt 6.1.2; see [here](https://sourceforge.net/p/qwt/code/2439/log/?path=/branches/qwt-6.1).)\n- [ ] `CellML Text` view (OS X only): to edit, say, the N62 model results in one or two black lines flashing repeatedly.\n- [ ] `QWebEngineView` steals the focus even when you ask for it to have no focus policy (i.e. you make a call to `setFocusPolicy(Qt::NoFocus);`). The end result is that if, in the `CellML Annotation` view for example, you start typing for a term to look up, you will only be able to type the first character before you lose the focus.\n- [ ] `QWebEngineView`: because of the asynchronous (?) loading/rendering, to switch from one CellML element to another, in the `CellML Annotation` view, results in the widget flashing (while it doesn't using WebKit).\n"}}
{"actor":{"display_login":"agarny"}}