[Development] Nominating QtGRPC & Qt Protobuf maintainers

[Alex Blasche via Development]

Hi,

Qt GRPC and Qt Protobuf were added to Qt a while ago. However until now they 
have been in Tech Preview mode. As we investigate the remaining issues which 
might prevent us from leaving TP, we need to address the open issue of 
maintainer-ship.

I'd like to nominate Tatiana Borisova as maintainer for Qt Protobuf and Alexey 
Edelev as maintainer for Qt GRPC. In fact, both have been working on this code 
base even before they officially became part of Qt. I am glad they agreed to 
continue this work going forward in the context of Qt Development.

--
Alex

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Monthly CI maintenance break - November (Mon, Nov 6th 2023)

[Ville-Pekka Karhu via Development]

This is now DONE

From: Ville-Pekka Karhu 
Sent: Monday, November 6, 2023 08:08
To: Qt development mailing list 
Subject: Re: Monthly CI maintenance break - November (Mon, Nov 6th 2023)

Server part of this starts NOW

From: Ville-Pekka Karhu 
Sent: Thursday, November 2, 2023 15:26
To: Qt development mailing list 
Subject: Re: Monthly CI maintenance break - November (Mon, Nov 6th 2023)

UPDATE:

This maintenance break starts already at 5:00 UTC because of network changes in 
our data center.

From: Ville-Pekka Karhu
Sent: Monday, October 30, 2023 10:16
To: Qt development mailing list 
Subject: Monthly CI maintenance break - November (Mon, Nov 6th 2023)


Hi,



We’ll have our scheduled maintenance break on next Monday (6th of November). 
We’ll begin our work at 6:00 UTC and you can prepare for 6 hours of CI not 
working.

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Replacement for QFont::ForceIntegerMetrics in Qt 6?

[Eskil Abrahamsen Blomfeldt via Development]

Hi!

ForceIntegerMetrics was originally added to get CoreText to look at little bit 
better with WebKit, since WebKit did not support subpixel positioning at the 
time and CoreText did not support font hinting. I removed it in Qt 6 because 
it's honestly not a typographically sensible thing to do, and the original use 
case had become irrelevant 

For your case, where you want to make sure your font aligns to the pixel grid, 
you could try enabling hinting  on it with 
font.setHintingPreference(QFont::PreferFullHinting). Font hinting will slightly 
alter the glyphs so that they actually align to the pixel grid instead of 
introducing kerning errors (which is what ForceIntegerMetrics did). I'm not 
sure if this is what you mean by "disabling design metrics"? If so, what 
exactly was the issue with it? I principle, I think this is the most correct 
solution to the problem, so maybe there's some way of getting it to work.

If that does not work, then another option is to manually get the QGlyphRuns 
from the QTextLayout and align the glyphs yourself before drawing them. That 
should get you the same layout as with ForceIntegerMetrics, both good and bad, 
without much extra work.

(Of course, ideally the rendering code should not assume integer advances for 
the characters, since this is not really a reasonable expectation for unhinted, 
scalable fonts, but I can see how it's not tempting to rewrite it just for this 
port.)

Eskil Abrahamsen Blomfeldt
Senior Manager, Graphics

The Qt Company
Sandakerveien 116
0484 Oslo, Norway
eskil.abrahamsen-blomfe...@qt.io
http://qt.io

From: Development  on behalf of Kai Uwe 
Broulik 
Sent: Saturday, November 4, 2023 10:50 AM
To: development@qt-project.org 
Subject: [Development] Replacement for QFont::ForceIntegerMetrics in Qt 6?

Hi everyone,

in Qt 5.15 the QFont::ForceIntegerMetrics was deprecated and
subsequently removed in Qt 6.

The rendering engine in Konsole, KDE’s terminal emulator, relies on the
fact that every glyph in the monospace font is rendered at the same
width, since sections of different style (e.g. search highlight, text
selection, various escape sequence formattings, etc) are painted in
different pases, basically positioned at charWidth * letterXPos.

With Qt 6, without this flag, the individual letters might be placed at
fractional positions, so a long text run can end up short of what the
renderer expects, leading to gaps in the rendering, see the attached
screenshot where I selected some text which now makes a gap.

I have read into QFontEngine a bit and found that the general
replacement is disabling use of “design metrics”. I changed the
rendering to use QPainter::paint with a QTextOption disabling design
metrics [1], which fixed the issue on my machine but apparently causes
issues with other fonts again.

Many of us have tried to find a solution for this but haven’t, really,
and it is a major showstopper for the Qt 6 adoption here. Any idea how
to address this properly, short of rewriting the renderer that I assume
has been like this for decades or perhaps some insights on what prompted
the removal?

Cheers
Kai Uwe

[1] 
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Finvent.kde.org%2Futilities%2Fkonsole%2F-%2Fmerge_requests%2F911=05%7C01%7Ceskil.abrahamsen-blomfeldt%40qt.io%7C402caffbb31d49df5cef08dbdd1bc085%7C20d0b167794d448a9d01aaeccc1124ac%7C0%7C0%7C638346883796105023%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=c5whMadCyHEavgFDTdDha8dTpO%2FRUBAnK%2Bp453ynvmk%3D=0
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development