# Qt in 4.9.0-2018-04-30

**URL:** <https://discourse.slicer.org/t/qt-in-4-9-0-2018-04-30/2748>\
**Category:** Development\
**Created:** [May 1, 2018, 6:38pm UTC](https://discourse.slicer.org/t/qt-in-4-9-0-2018-04-30/2748 "2018-05-01T18:38:35Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ebremer](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ebremer/32/607_2.png) [@ebremer](https://discourse.slicer.org/u/ebremer)\
**Post date:** [May 1, 2018, 6:38pm UTC](https://discourse.slicer.org/t/qt-in-4-9-0-2018-04-30/2748/1 "2018-05-01T18:38:35Z")

</div>

I downloaded the above nightly build, but qt.QWebView() seems to be missing. Is it part of the nightly?

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [May 1, 2018, 7:13pm UTC](https://discourse.slicer.org/t/qt-in-4-9-0-2018-04-30/2748/2 "2018-05-01T19:13:05Z")

</div>

With Qt5 there’s been a migration from QtWebKit to [QtWebEngine](https://wiki.qt.io/QtWebEngine). There’s some debate as to whether this is a good thing, but for now we are aiming to make QtWebEngine work for us. Within Slicer the slicer.qSlicerWebWidget() is planned as a usable replacement for the qt.QWebView() which seems to work okay on windows but has some issues elsewhere.

---

<div class="post-metadata">

**Author:** ![ebremer](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ebremer/32/607_2.png) [@ebremer](https://discourse.slicer.org/u/ebremer)\
**Post date:** [May 2, 2018, 5:12pm UTC](https://discourse.slicer.org/t/qt-in-4-9-0-2018-04-30/2748/3 "2018-05-02T17:12:32Z")

</div>

Thanks Steve! I will give it a spin. We would like to update SlicerPathology so that it will work with our newest QuIP system. - Erich

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [May 2, 2018, 7:37pm UTC](https://discourse.slicer.org/t/qt-in-4-9-0-2018-04-30/2748/4 "2018-05-02T19:37:56Z")

</div>

> [@ebremer](#):
>
> We would like to update SlicerPathology

Note that SlicerPathology has not been functional for quite some time. The underlying issue has been discussed on this forum: [Pathology module install fail due to sliceWidget attribute error](https://discourse.slicer.org/t/pathology-module-install-fail-due-to-slicewidget-attribute-error/2269), and documented in this GitHub issue: [Module won't start - testing code committed by accident? · Issue #100 · SBU-BMI/SlicerPathology · GitHub](https://github.com/SBU-BMI/SlicerPathology/issues/100).

More recently, build errors cropped in, most likely due to the recent upgrade of the Slicer dependency libraries - see dashboard [here](http://slicer.cdash.org/index.php?project=SlicerPreview&filtercount=1&showfilters=1&field1=buildname&compare1=63&value1=SlicerPathology).

---

<div class="post-metadata">

**Author:** ![ebremer](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ebremer/32/607_2.png) [@ebremer](https://discourse.slicer.org/u/ebremer)\
**Post date:** [May 3, 2018, 3:08am UTC](https://discourse.slicer.org/t/qt-in-4-9-0-2018-04-30/2748/5 "2018-05-03T03:08:09Z")

</div>

We’ll get it squared away. - Erich