Re: [Development] Repository request: qlitehtml

2021-01-21 Thread Kai Pastor, DG0YT via Development
Am 21.01.21 um 12:04 schrieb Jaroslaw Kobus: +1 This may be potentially easily reused in e.g. standalone assistant. I would like to see qlitehtml integrated into QTextBrowser. This, or a source-compatible replacement, would make it available for Qt Assistant, too. Kai Pastor

Re: [Development] Qt Assistant (was: RE: Qt 6 co-installability with Qt 5)

2020-11-19 Thread Kai Pastor, DG0YT via Development
Am 19.11.20 um 09:15 schrieb Kai Köhne: -Original Message- From: Kai Pastor, DG0YT Sent: Thursday, November 19, 2020 8:27 AM To: Kai Köhne ; development@qt-project.org Subject: Re: [Development] Qt 6 co-installability with Qt 5 Am 19.11.20 um 08:20 schrieb Kai Köhne: Am 18.11.20 um 15

Re: [Development] Qt 6 co-installability with Qt 5

2020-11-18 Thread Kai Pastor, DG0YT via Development
Am 19.11.20 um 08:20 schrieb Kai Köhne: Am 18.11.20 um 15:50 schrieb Kai Köhne: FYI, we've been taking assistant out of Qt 6.0. https://bugreports.qt.io/browse/QTBUG-86746 . It's not depending on any particular Qt version, so my suggestion is to resurrect it (if there's enough demand) outside of

Re: [Development] Qt 6 co-installability with Qt 5

2020-11-18 Thread Kai Pastor, DG0YT via Development
Am 18.11.20 um 15:50 schrieb Kai Köhne: FYI, we've been taking assistant out of Qt 6.0. https://bugreports.qt.io/browse/QTBUG-86746 . It's not depending on any particular Qt version, so my suggestion is to resurrect it (if there's enough demand) outside of qt5.git. Could you please clarify:

Re: [Development] QUtf8String{, View}

2020-05-23 Thread Kai Pastor, DG0YT
Am 23.05.20 um 03:06 schrieb Thiago Macieira: On Thursday, 14 May 2020 07:41:45 PDT Marc Mutz via Development wrote: There's only our own lazyness which stands in the way of this better alternative. [snip the rest] Update: As we're reviewing the changes Lars is making to get rid of QStringRef

Re: [Development] QtCS2019 Notes: Clang-based cpp parser for lupdate

2019-11-24 Thread Kai Pastor, DG0YT
Am 22.11.19 um 21:25 schrieb Kai Pastor, DG0YT: Am 22.11.19 um 17:03 schrieb Kai Köhne: Keep in mind that you need this context available both at runtime and at lupdate time. That is, the only setup how this IMO would reliably work is if we make the context a part of the tr() call

Re: [Development] QtCS2019 Notes: Clang-based cpp parser for lupdate

2019-11-22 Thread Kai Pastor, DG0YT
Am 22.11.19 um 17:03 schrieb Kai Köhne: From: Development On Behalf Of Joerg Bornemann On 11/22/19 7:21 AM, Kai Pastor, DG0YT wrote: Given the Qt Creator example, would it be feasible to make explicit declaration of a file's context mandatory, at least for the existing ("fast")

Re: [Development] QtCS2019 Notes: Clang-based cpp parser for lupdate

2019-11-21 Thread Kai Pastor, DG0YT
Am 21.11.19 um 20:23 schrieb André Pönitz: On Thu, Nov 21, 2019 at 07:48:41PM +0100, Oswald Buddenhagen wrote: a more radical and much simpler approach would be switching to gettext The most prominent difference is the (usually) per-class automatic context which I always found too clever to be

[Development] QTextCodec removal and QXmlStreamWriter

2019-11-17 Thread Kai Pastor, DG0YT
(From "RFC: Defaulting to or enforcing UTF-8 locales on Unix systems"...) Am 17.11.19 um 01:55 schrieb Thiago Macieira: It all started with a change (see OP) about removing QTextCodec from the API and from QtCore. It seemed reasonable enough but it turned up quite a few kinks that hadn't been p

Re: [Development] The age-old T* foo vs. T *foo

2019-10-17 Thread Kai Pastor, DG0YT
Am 17.10.19 um 23:24 schrieb Ville Voutilainen: On Fri, 18 Oct 2019 at 00:16, André Pönitz wrote: And it's not "just our style". LLVM uses the same style for stars and ampersands. Who else? From clang-format-configurator [1], I see these base formats using the Qt style: LLVM Google Micros

Re: [Development] The age-old T* foo vs. T *foo

2019-10-17 Thread Kai Pastor, DG0YT
Am 17.10.19 um 23:55 schrieb André Pönitz: On Fri, Oct 18, 2019 at 12:24:12AM +0300, Ville Voutilainen wrote: On Fri, 18 Oct 2019 at 00:16, André Pönitz wrote: On Thu, Oct 17, 2019 at 09:04:36PM +0300, Ville Voutilainen wrote: Since we are about to do a major version upgrade, should be stop b

Re: [Development] Updated high-DPI support for Qt 5.14

2019-09-25 Thread Kai Pastor, DG0YT
Am 25.09.19 um 20:08 schrieb Elvis Stansvik: Den ons 25 sep. 2019 kl 18:34 skrev Matthew Woehlke : On 25/09/2019 08.54, Morten Sørvig wrote: I see two differences between setting the DPI vs a factor: - You set one value per screen (DPI) instead of two (DPI & factor) - Qt can compute the facto

Re: [Development] INTEGRITY

2019-09-19 Thread Kai Pastor, DG0YT
Am 19.09.19 um 10:41 schrieb Mutz, Marc via Development: 1. List a maintainer for INTEGRITY in https://wiki.qt.io/Maintainers 2. That maintainer should either find the missing linker flag, or file a bug with Integrity 3. If there's a work-around (providing those missing functions in Qt, e.g.),

Re: [Development] Using windeployqt from a cross-compiled Qt

2019-08-24 Thread Kai Pastor, DG0YT
Am 24.08.19 um 16:55 schrieb Richard Weickelt: I've been trying to use windeployqt from a cross-compiled (mingw-w64 on Linux) Qt. I must be the only person on the planet doing this because there is a bug in windeployqt preventing it. Tried that in the past, but resorted to CMake and BundleUtili

Re: [Development] Dropping MinGW support in Qt 6 (Was: HEADS-UP: QStringLiteral)

2019-08-21 Thread Kai Pastor, DG0YT
Am 21.08.19 um 21:36 schrieb Kyle Edwards: On Wed, 2019-08-21 at 21:22 +0200, Elvis Stansvik wrote: Why not just ship those DLLs? I wouldn't call that "verboten" (forbidden), just a bit more to do for deployment. It's not "verboten", but it's also not as straightforward as redistributing free s

Re: [Development] Dropping MinGW support in Qt 6 (Was: HEADS-UP: QStringLiteral)

2019-08-21 Thread Kai Pastor, DG0YT
Am 21.08.19 um 22:03 schrieb Thiago Macieira: On Wednesday, 21 August 2019 12:54:11 PDT Thiago Macieira wrote: MSYS2 is Cygwin-like. It tries to emulate a Unix on Windows. It's great for porting Unix software to Windows and I love that it gives me a bash and pacman for when I need to develop on

Re: [Development] Grooming the merges?

2019-07-17 Thread Kai Pastor, DG0YT
Am 17.07.19 um 11:01 schrieb Edward Welbourne: I'm not Cc'd on these unless the bot thinks I'm one of the conflict participants, which it didn't in this case (although its correct resolution of qbytearray.cpp implicated my move of it to corelib/text/). Isn't there something seriously wrong with

Re: [Development] Assistant WebKit/WebEngine support

2019-06-29 Thread Kai Pastor, DG0YT
On 27/06/2019 21:02, Thiago Macieira wrote: On Thursday, 27 June 2019 01:07:45 PDT Konrad Rosenbaum wrote: Please also keep in mind that a fair number of developers use the same tool-chain (qdoc, assistant, QtHelp) to generate their own documentation - this means that assistant gets redistribu