# 2026.11.03 Weekly Meeting

**URL:** <https://discourse.slicer.org/t/2026-11-03-weekly-meeting/48633>\
**Category:** Weekly meetings\
**Created:** [October 28, 2026, 3:19pm UTC](https://discourse.slicer.org/t/2026-11-03-weekly-meeting/48633 "2026-10-28T15:19:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ebrahim](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ebrahim/32/13403_2.png) [@ebrahim](https://discourse.slicer.org/u/ebrahim)\
**Post date:** [October 28, 2026, 3:19pm UTC](https://discourse.slicer.org/t/2026-11-03-weekly-meeting/48633/1 "2026-10-28T15:19:15Z")

</div>

Title: 2026.11.03 Weekly Meeting

Next Tuesday, we will be having our next weekly hangout at **10:00 AM ET**

Anyone is welcome to join at this link: [Google Meet meeting](https://meet.google.com/ymg-ahrz-www)

* * *

> **Weekly Meeting**
>
> **Starts:** November 3, 2026, 10:00am (America/New\_York)\
> **Link:** <https://meet.google.com/ymg-ahrz-www>

**Agenda:**

Please post to this thread to put a topic on the agenda! We will try to prioritize agenda items during the meeting.

* * *

Thanks  
Sam and Ebrahim

---

<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:** [October 28, 2026, 3:20pm UTC](https://discourse.slicer.org/t/2026-11-03-weekly-meeting/48633/2 "2026-10-28T15:20:07Z")

</div>

I’m doublebooked next week, but will join late if I can.

---

<div class="post-metadata">

**Author:** ![Thibault\_Pelletier](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/thibault_pelletier/32/4767_2.png) [@Thibault\_Pelletier](https://discourse.slicer.org/u/Thibault_Pelletier)\
**Post date:** [October 29, 2026, 1:22pm UTC](https://discourse.slicer.org/t/2026-11-03-weekly-meeting/48633/3 "2026-10-29T13:22:38Z")

</div>

Since it was discussed during a previous weekly, I looked a bit into QWebEngineView alternatives and the solution would be in Qt itself with the [QWebView](https://doc.qt.io/qt-6/qwebview.html) component (Qt 6.11+).

Behavior will change depending on the platform:

- Windows: delegates to WebView2
- MacOs: delegates to system WKWebView
- Linux: Still requires QtWebEngineView + Chromium

Linux systems don’t seem to provide yet native browser embedding, so there wouldn’t be a clean solution for Linux at the moment.

FYI: @pieper & @lassoan

---

<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:** [October 29, 2026, 3:40pm UTC](https://discourse.slicer.org/t/2026-11-03-weekly-meeting/48633/4 "2026-10-29T15:40:52Z")

</div>

Thanks for looking into that @Thibault_Pelletier .

I don’t think there’s any rush to get rid of QWebEngine from the Slicer distribution, but as I mentioned it is a big part of the binary that we ship, so it impacts download and startup times. Using a native browser is no doubt more secure too, since it should get more frequent patches. I think we could make it pretty seamless.