On Friday 16 October 2015 01:32:26 Bubke Marco wrote:
> On October 16, 2015 00:20:22 Marc Mutz wrote:
> > Guys, this thread is for QStringView. Could we keep it on-topic, please?
> > There are more than enough bits floating around to create your own
> > threads (with a tip of the hat to Kai).
>
>
On 15/10/15 17:59, "Thiago Macieira" wrote:
>On Thursday 15 October 2015 18:26:23 Александр Волков wrote:
>> Hi,
>>
>> Currently Qt supports libxcb 1.5, which is very old (it was released on
>> December 3, 2009)
>> It complicates adding new bundled xcb libraries, because they have to be
>> check
Can you refocus the discussion for everyone? For me at least?
QString is my favorite class of all time. I use it every day in every program;
it always works, and I never make a mistake.
1. What is the problem with QString that QStringView will solve?
2. Why can't QString be fixed?
3. What is a
On Thursday 15 October 2015 21:02:09 Bubke Marco wrote:
> Actually I think Qt is not main developing library people use. It is there
> to make the boring stuff easy, to hide the different interfaces between
> different platforms. That is why many people use Qt, they want to have a
> GUI but don't
On October 16, 2015 00:20:22 Marc Mutz wrote:
> Guys, this thread is for QStringView. Could we keep it on-topic, please?
> There
> are more than enough bits floating around to create your own threads (with a
> tip of the hat to Kai).
>
Good argument but actually I think before we introduce so
On 16 October 2015 at 05:50, Samuel Gaist wrote:
>
> On 15 oct. 2015, at 19:12, Giuseppe D'Angelo
> wrote:
>
>> Il 15/10/2015 19:06, Volny ha scritto:
>>> Same on Linux.
>>
>> It's https://bugreports.qt.io/browse/QTBUG-48781 , no idea about an ETA. You
>> could try redownloading until you get
Guys, this thread is for QStringView. Could we keep it on-topic, please? There
are more than enough bits floating around to create your own threads (with a
tip of the hat to Kai).
Thanks,
Marc
On Thursday 15 October 2015 23:02:09 Bubke Marco wrote:
> On October 15, 2015 00:27:45 Thiago Macieira
On 15 oct. 2015, at 19:12, Giuseppe D'Angelo wrote:
> Il 15/10/2015 19:06, Volny ha scritto:
>> Same on Linux.
>
> It's https://bugreports.qt.io/browse/QTBUG-48781 , no idea about an ETA. You
> could try redownloading until you get a good mirror :(
>
> HTH,
> --
> Giuseppe D'Angelo | giusep
On October 15, 2015 00:27:45 Thiago Macieira wrote:
> On Wednesday 14 October 2015 21:51:23 Bubke Marco wrote:
>> On October 14, 2015 23:10:26 Thiago Macieira
> wrote:
>> > Do it on your own. You just said that ICU has the function you want, so
>> > use
>> > it.
>>
>> So Qt is always shipping
On October 15, 2015 17:58:27 Thiago Macieira wrote:
> On Thursday 15 October 2015 07:34:30 Koehne Kai wrote:
>> > -Original Message-
>> > [...]
>> >
>> > >BTW: functions storing a passed QString as-is should provide a
>> > >QString&& overload, and that might be a good idea even when othe
Il 15/10/2015 19:06, Volny ha scritto:
Same on Linux.
It's https://bugreports.qt.io/browse/QTBUG-48781 , no idea about an ETA.
You could try redownloading until you get a good mirror :(
HTH,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Software Engineer
KDAB (UK) Ltd., a KDAB Group co
Same on Linux. Fanda
It looks like there’s a problem downloading Qt 5.5.1 using the Windows online
installer. I get the message
Hash verification while downloading fails. This is a temporary error, please
retry.
while downloading archive '3.5.1-0qt-creator-opensource-vs2013-32.7z' for
component: Qt Creator 3..5.1_
2015-10-15 17:52 GMT+03:00 André Somers :
> Op 15-10-2015 om 14:52 schreef Konstantin Ritt:
> >
> >
> > For everything but US-ASCII / Latin-1, UTF-8 isn't faster than UTF-16
> > (feel free to compare their complexity against UTF-32).
> > And why "pure Chinese signs" again? Did you ever look into t
On Thursday 15 October 2015 08:29:00 Marc Mutz wrote:
> On Thursday 15 October 2015 06:03:40 Thiago Macieira wrote:
> > We'll have to have a long discussion on what to name the class, though...
> > QTimeExtended? QExtendedTime? QTimeV2? QMicroTime? QTimeSpan?
>
> std::chrono::{duration,time_point,
On Thursday 15 October 2015 15:38:02 Иван Комиссаров wrote:
> It's hardly to create more non-intuitive API than std::chrono...
Yes, 3ms + 15ns is extremely unintuitive. How could they?! I have absolutely
no idea what that means...
--
Marc Mutz | Senior Software Engineer
KDAB (Deutschland) GmbH
On Thursday, 15 October 2015, Dustin Mitchell wrote:
> What about something like QHighResolutionTime, or something to reflect
that it's indeed a point in time with higher resolution?
Yes, or QPreciseTime?
> Dustin
> On Thu, Oct 15, 2015 at 8:42 AM, Dustin Mitchell
wrote:
>>
>> I agree, QTimeSpa
On Thursday 15 October 2015 18:26:23 Александр Волков wrote:
> Hi,
>
> Currently Qt supports libxcb 1.5, which is very old (it was released on
> December 3, 2009)
> It complicates adding new bundled xcb libraries, because they have to be
> checked
> for compatibility with this old version and mayb
On Thursday 15 October 2015 07:34:30 Koehne Kai wrote:
> > -Original Message-
> > [...]
> >
> > >BTW: functions storing a passed QString as-is should provide a
> > >QString&& overload, and that might be a good idea even when otherwise
> > >using QStringView only.
> >
> > Yes, agree with t
On Thursday 15 October 2015 16:34:47 André Somers wrote:
> Op 15-10-2015 om 14:18 schreef Edward Sutton:
> > +1 for naming QTimeSpan with support for arithmetic operators.
>
> -1 for that one. To me QTimeSpan is something else. I have an old WIP
> lying around with exactly that name. It does not m
Alexander said:
> Qt officially supports the following platforms that use libxcb:
> OpenSuSE 13.1 (libxcb 1.9.1, xcb-proto 1.8)
> Red Hat Enterprise Linux 6.6 (libxcb 1.9, xcb-proto 1.8)
> Ubuntu 14.04 - 64bit (libxcb 1.10, xcb-proto 1.10)
For reference, Debian stable (Jessie) is also on 1.10
Hi,
Currently Qt supports libxcb 1.5, which is very old (it was released on
December 3, 2009)
It complicates adding new bundled xcb libraries, because they have to be
checked
for compatibility with this old version and maybe patched.
Qt officially supports the following platforms that use libxc
What about something like QHighResolutionTime, or something to reflect that
it's indeed a point in time with higher resolution?
Dustin
On Thu, Oct 15, 2015 at 8:42 AM, Dustin Mitchell wrote:
> I agree, QTimeSpan has a different meaning than what I'm looking for. I
> just need timestamps, partic
Op 15-10-2015 om 14:52 schreef Konstantin Ritt:
>
>
> For everything but US-ASCII / Latin-1, UTF-8 isn't faster than UTF-16
> (feel free to compare their complexity against UTF-32).
> And why "pure Chinese signs" again? Did you ever look into the
> Unicode's Scripts.txt [1], for example? It clear
I agree, QTimeSpan has a different meaning than what I'm looking for. I
just need timestamps, particular points in time, that provide more than
millisecond resolution.
And thus begins the never-ending debate on what to name something. This is
always the hardest part of writing code for me...
Dust
Op 15-10-2015 om 14:18 schreef Edward Sutton:
> +1 for naming QTimeSpan with support for arithmetic operators.
-1 for that one. To me QTimeSpan is something else. I have an old WIP
lying around with exactly that name. It does not model a specific time,
it models a duration.
André
___
On October 15, 2015 15:56:35 Matthew Woehlke wrote:
> On 2015-10-15 02:38, Ziller Eike wrote:
>> So from where does 's.indexOf(‘c’, i-2)' search?
>>
>> This is similar to integer overflow, and I think utilizing that in an
>> API leads to less readable and potentially unexpectedly behaving
>> code
On 2015-10-14 18:27, Thiago Macieira wrote:
> On Wednesday 14 October 2015 21:51:23 Bubke Marco wrote:
>> Is UTF 16 seekable? You still have surrogates and you can merge merge code
>> points.
>
> Seekable enough. It's much easier to deal with than UTF-8. A surrogate pair,
> as its name says, appe
On 2015-10-15 02:38, Ziller Eike wrote:
> So from where does 's.indexOf(‘c’, i-2)' search?
>
> This is similar to integer overflow, and I think utilizing that in an
> API leads to less readable and potentially unexpectedly behaving
> code.
It depends on the value of i, of course. And you're not go
On October 15, 2015 14:53:29 Konstantin Ritt wrote:
> 2015-10-15 11:00 GMT+03:00 Bubke Marco
> mailto:marco.bu...@theqtcompany.com>>:
> On October 15, 2015 08:45:30 Knoll Lars
> mailto:lars.kn...@theqtcompany.com>> wrote:
>
>> On 14/10/15 23:51, "Bubke Marco"
>> mailto:marco.bu...@theqtcompany
On Thursday 15 October 2015 14:52:46 Konstantin Ritt wrote:
> For everything but US-ASCII / Latin-1, UTF-8 isn't faster than UTF-16 (feel
> free to compare their complexity against UTF-32).
> And why "pure Chinese signs" again? Did you ever look into the Unicode's
> Scripts.txt [1], for example? It
It's hardly to create more non-intuitive API than std::chrono...
2015-10-15 17:41 GMT+03:00 Marc Mutz :
> On Thursday 15 October 2015 14:50:10 Mathias Hasselmann wrote:
> > Plus user defined literals (for hours, minutes, seconds) and adoption in
> > QTimer and friends.
>
> Ah, the old NIH syndrom
On Thursday 15 October 2015 14:50:10 Mathias Hasselmann wrote:
> Plus user defined literals (for hours, minutes, seconds) and adoption in
> QTimer and friends.
Ah, the old NIH syndrome...
Here's your existing QTimeSpan, with operators and user-defined literals:
http://en.cppreference.com/w/cpp/
On Thursday 15 Oct 2015 13:13:52 Edward Sutton wrote:
> On Thursday 15 Oct 2015 12:18:22 Edward Sutton wrote:
> > +1 for naming QTimeSpan with support for arithmetic operators.
>
> Andre and I did start something along these lines way back before Open
> Governance if anybody wants to pick it up.
>
On Thursday 15 Oct 2015 12:18:22 Edward Sutton wrote:
> +1 for naming QTimeSpan with support for arithmetic operators.
Andre and I did start something along these lines way back before Open
Governance if anybody wants to pick it up.
It was at
https://qt.gitorious.org/qt/qt/merge_requests/1014
On Thursday 15 Oct 2015 12:18:22 Edward Sutton wrote:
> +1 for naming QTimeSpan with support for arithmetic operators.
Andre and I did start something along these lines way back before Open
Governance if anybody wants to pick it up.
It was at
https://qt.gitorious.org/qt/qt/merge_requests/1014
2015-10-15 11:00 GMT+03:00 Bubke Marco :
> On October 15, 2015 08:45:30 Knoll Lars
> wrote:
>
> > On 14/10/15 23:51, "Bubke Marco" wrote:
> >
> >>On October 14, 2015 23:10:26 Thiago Macieira
> >>wrote:
> >>> Qt does not have to provide a comparator that operates on something
> >>>other than
> >
Plus user defined literals (for hours, minutes, seconds) and adoption in
QTimer and friends.
Am 15.10.2015 um 14:18 schrieb Edward Sutton:
> +1 for naming QTimeSpan with support for arithmetic operators.
>
> On Thursday 15 October 2015 02:09:07 Aleix Pol wrote:
>> Maybe you could look into forkin
+1 for naming QTimeSpan with support for arithmetic operators.
On Thursday 15 October 2015 02:09:07 Aleix Pol wrote:
> Maybe you could look into forking QTime with the microseconds changes?
> That could be reasonable even within Qt.
Indeed, that would.
We'll have to have a long discussion on wha
+1
--
Michael Brunning, Senior Software Engineer | The Qt Company
The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der
Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
On Thursday, October 15, 2015 9:25:35 AM CEST Koehne Kai wrote:
> Hi,
>
> I hereby nominate Allan Jensen as the official maintainer for the Qt
> WebEngine module. He's been the official maintainer for Qt WebKit already,
> but nowadays works full time on Qt WebEngine, and is also the default
> assi
Hi all,
Qt 5.5.1 has just been released. For details check the blog post at
http://blog.qt.io/blog/2015/10/15/qt-5-5-1-released/
In addition to Qt 5.5.1, we also released Qt Creator 3.5.1, see
http://blog.qt.io/blog/2015/10/15/qt-creator-3-5-1-released/
Big thanks to everyone who have helped to
+1.
Cheers,
Lars
On 15/10/15 11:25, "Koehne Kai" wrote:
>Hi,
>
>I hereby nominate Allan Jensen as the official maintainer for the Qt
>WebEngine module. He's been the official maintainer for Qt WebKit
>already, but nowadays works full time on Qt WebEngine, and is also the
>default assignee for t
+1
Cheers,
Jocelyn
> On 15 Oct 2015, at 11:25, Koehne Kai wrote:
>
> Hi,
>
> I hereby nominate Allan Jensen as the official maintainer for the Qt
> WebEngine module. He's been the official maintainer for Qt WebKit already,
> but nowadays works full time on Qt WebEngine, and is also the defau
+1
Tobias Hunger, Senior Software Engineer | The Qt Company
The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der
Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
___
+1
Simon
From: development-bounces+simon.hausmann=theqtcompany@qt-project.org
on behalf
of Koehne Kai
Sent: Thursday, October 15, 2015 11:25
To: 'development@qt-project.org'
Subject: [Development] Nominating Allan Jensen as maintainer for Qt WebEn
Hi,
I hereby nominate Allan Jensen as the official maintainer for the Qt WebEngine
module. He's been the official maintainer for Qt WebKit already, but nowadays
works full time on Qt WebEngine, and is also the default assignee for the
WebEngine component in JIRA.
Regards
Kai
--
Kai Köhne, S
On October 15, 2015 08:45:30 Knoll Lars wrote:
> On 14/10/15 23:51, "Bubke Marco" wrote:
>
>>On October 14, 2015 23:10:26 Thiago Macieira
>>wrote:
>>
>>> On Wednesday 14 October 2015 20:52:12 Bubke Marco wrote:
On October 14, 2015 22:13:11 Thiago Macieira
>>> wrote:
And I don't w
> -Original Message-
> [...]
> >BTW: functions storing a passed QString as-is should provide a
> >QString&& overload, and that might be a good idea even when otherwise
> >using QStringView only.
>
> Yes, agree with this.
I guess this advice is not only for QString arguments though (from 5
On 15/10/15 08:29, "Marc Mutz" wrote:
>On Thursday 15 October 2015 06:03:40 Thiago Macieira wrote:
>> We'll have to have a long discussion on what to name the class,
>>though...
>> QTimeExtended? QExtendedTime? QTimeV2? QMicroTime? QTimeSpan?
>
>std::chrono::{duration,time_point,clock}. In Qt6,
50 matches
Mail list logo
