Volker Hilsheimer wrote:
> The overall goal here is to make sure that we don’t have to carry poorly
> designed architecture or APIs around with us throughout the Qt 6 series,
> and as long as we care about binary and source compatibility within a
> major series, doing what we can for Qt 6.0 (and do
Philippe wrote:
> On Sat, 1 Jun 2019 14:36:12 +0200
> André Pönitz wrote:
>
>> So it might make even sense to step back further and start with
>> asking "What should Qt be?" before trying to find out on whether
>> a specific API is poorly designed or not, as that decision depends
>> on the purpo
Am Mittwoch, den 29.05.2019, 23:34 +0200 schrieb Mutz, Marc via Development:
> > So, yes, this is borne out of frustration with the lack of maintenance
> > of QtCore plumbing. I don't see that changing and I acknowledge and
> > understand that the focus of development has shifted towards QML.
>
Here's a PS1 script that more or less does it (god that language is awful
to use) :
xxd.ps1:
param([String]$path)
$bytes = [System.IO.File]::ReadAllBytes($path);
$size = $bytes.length;
$bytes = (($bytes | %{ "0x" + $_ ; }) | Out-String);
$content = $bytes -replace "`r",", " -replace "`n","" -re
On Saturday, 1 June 2019 03:46:34 PDT André Pönitz wrote:
> I am getting mildly irritated by those ongoing suggestions (not just
> yours) to use anything but Qt to get stuff done, even Qt's own tasks.
> It's sending an odd message.
>
> Sure, one can pull e.g. any "plain C++" replacement for QXmlSt
On 5/31/19 4:24 PM, Volker Hilsheimer wrote:
> Nobody is forced to move to Qt 6 right away; Qt 5.15 is an LTS with
> three years maintenance. We are not expecting lots of people to jump
> on Qt 6.0 anyway (because .0, and not an LTS release anyway), so when
> an API was marked as deprecated makes p
On Sat, 1 Jun 2019 14:36:12 +0200
André Pönitz wrote:
> So it might make even sense to step back further and start with
> asking "What should Qt be?" before trying to find out on whether
> a specific API is poorly designed or not, as that decision depends
> on the purpose.
I second a recent quo
On Fri, May 31, 2019 at 01:24:13PM +, Volker Hilsheimer wrote:
> The overall goal here is to make sure that we don’t have to carry
> poorly designed architecture or APIs around with us throughout the Qt
> 6 series, and as long as we care about binary and source compatibility
> within a major se
On Fri, May 31, 2019 at 02:50:45PM +0200, Giuseppe D'Angelo via Development
wrote:
> I guess that the idea is that the port to Qt 6 can then happen in multiple
> steps:
>
> 1) port to Qt 5.latest;
> 2) (enable and) fix all deprecation warnings;
> 3) port to Qt 6.
> If this is still the plan, I m
On Fri, May 31, 2019 at 11:22:03AM +0200, Tobias Hunger wrote:
> Hi Thiago,
>
> On Thu, May 30, 2019 at 8:18 PM Thiago Macieira
> wrote:
> > On Wednesday, 29 May 2019 06:33:23 PDT Giuseppe D'Angelo via Development
> > wrote:
> > > 2) should QRegExp stay in bootstrap? I have no idea of what's happ
10 matches
Mail list logo
