Re: [Development] [Interest] Printer-specific options in Qt5's print dialog (Linux, CUPS)

Development på vegne av Thiago Macieira skrev følgende den 30.01.2017, 17.57: Resending this to the development mailing list. Others: please read Michael's email below. On

Re: [Development] Calendar Systems proposal

On Mon, Jan 30, 2017, at 09:07 PM, Hamed Masafi wrote: > My prefer option is form (3) > We can add an enumeration to global space. > var date = new Date; > var out = date.toString(Qt.JalaliCalendar, "-MM-dd"); I would prefer to not modify standard APIs if we can avoid it (unless we have a

Re: [Development] Calendar Systems proposal

> That shall complement Soroush Rabiei's work on the C++ side: Yes, that's right. I'm trying to port Soroush's calendar mechanism to qml side of Qt. > If I understand Lars correctly, he prefers an API where the calendar > object carries methods that act on a date and any further arguments it >

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

On 2017-01-30 12:29, André Pönitz wrote: > *If* it turns out to be a problem elsewhere, which I don't expect, > there needs to be an explanation why a transcription of "ä" can be > considered a more severe "legal issue" than the "legal issue" > originating from transcribing "©" as "(C)" in the

[Development] Feature Freeze Exception: QStringView

Hi, QStringView is ready to be merged, but the maintainer has asked for another week before he can properly review the class. In case you don't remember, here's the discussion thread from 2015: http://lists.qt-project.org/pipermail/development/2015-October/023358.html Here's the evolving

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

On Mon, Jan 30, 2017 at 11:23:30AM +, Simon, Hausmann wrote: > We practically support three different front-ends: GCC, clang and > MSVC. All three - MSVC with the help of an option - can > grok UTF-8. Let's use it at least inside Qt :) Qt source is handled by a variety of tools, not only

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

On Sun, Jan 29, 2017 at 05:21:57PM -0800, Thiago Macieira wrote: > On domingo, 29 de janeiro de 2017 10:33:39 PST André Pönitz wrote: > > We should remove non-ASCII characters from the sources if they cause > > problems. > > We've had this discussion. One of our largest contributors has a full

Re: [Development] [Interest] Printer-specific options in Qt5's print dialog (Linux, CUPS)

Resending this to the development mailing list. Others: please read Michael's email below. On segunda-feira, 30 de janeiro de 2017 14:12:32 PST you wrote: > Hi, > > in September 2015, I asked about the status of printer-specific options > in the Qt 5 print dialog on Linux (with CUPS as printing

Re: [Development] Calendar Systems proposal

On segunda-feira, 30 de janeiro de 2017 15:43:30 PST Soroush Rabiei wrote: > Can we have calendars for 5.9 ? It's not FF yet I suppose. And there's > not much to do. Either we implement calendars as factory classes > operating on QDate, or adding to QDate's API, there is not much work > left to

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

On segunda-feira, 30 de janeiro de 2017 09:58:30 PST Edward, Welbourne wrote: > I'm not sure how that works on MS-Windows, but I'd just set > LANG=en.UTF-8 in my environment on any Unix; this would then only affect > the process in which I set it. So it might be worth seeing if you can > do that

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

On segunda-feira, 30 de janeiro de 2017 14:43:22 PST Konstantin Tokarev wrote: > What about Intel? (IIRC they use EDG frontend, aren't they?) icc on Mac and Windows operates like GCC and Clang. I'll check icl.exe on Windows. It is supposed to operate like MSVC, but it might have some other

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

On segunda-feira, 30 de janeiro de 2017 09:56:46 PST Giuseppe D'Angelo wrote: > Il 30/01/2017 02:21, Thiago Macieira ha scritto: > > So, we should: > > a) still avoid non-ASCII in our source files, aside from comments > > b) allow non-ASCII in comments, as needed > > Didn't we have issues with

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

On segunda-feira, 30 de janeiro de 2017 09:42:05 PST Marc Mutz wrote: > // ∡ Better: // U++2221 MEASURED ANGLE -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing

Re: [Development] Branch request for Qt 3D

On Monday 30 January 2017 13:45:49 Frederik Gladhorn wrote: > On torsdag 26. januar 2017 14.11.33 CET Sean Harmer wrote: > > Hi, > > > > Could somebody create me a new wip/physics branch for the Qt 3D branched > > off of dev please? This is to start preparing a physics aspect hopefully > > for Qt

Re: [Development] Branch request for Qt 3D

On torsdag 26. januar 2017 14.11.33 CET Sean Harmer wrote: > Hi, > > Could somebody create me a new wip/physics branch for the Qt 3D branched off > of dev please? This is to start preparing a physics aspect hopefully for Qt > 5.10. Looks like this has been done, the branch is there. Cheers,

Re: [Development] Calendar Systems proposal

Can we have calendars for 5.9 ? It's not FF yet I suppose. And there's not much to do. Either we implement calendars as factory classes operating on QDate, or adding to QDate's API, there is not much work left to do. ___ Development mailing list

Re: [Development] [Releasing] Change file process & improvement proposal

On 26/01/2017 13:28, Kai Koehne wrote: So, any strong opinion against enforcing a [ChangeLog] line, with "[ChangeLog] -" for commits that don't need one? Yes. Absolutely not. This will just reverse the problem, creating noise in the commits and lots of useless ChangeLog entries, we might as

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

On 30 Jan 2017, at 12:23, Simon, Hausmann > wrote: Making a warning go away for compilers that we know support utf-8 may not come at the price of your life :) I for one am all in favor of requiring just the Qt source code (not talking about

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

> On 30 Jan 2017, at 12:06, Viktor Engelmann wrote: > > > Am 30.01.2017 um 11:40 schrieb Giuseppe D'Angelo: >> Il 30/01/2017 11:35, Viktor Engelmann ha scritto: >>> As far as I can see, all our codes *are* UTF-8 encoded (a least they >>> should be, IMHO), so why would

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

30.01.2017, 14:24, "Simon, Hausmann" : > Making a warning go away for compilers that we know support utf-8 may not > come at the price of your life :) > > I for one am all in favor of requiring just the Qt source code (not talking > about customer code) to be encoded in a

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

30.01.2017, 14:37, "Viktor Engelmann" : > Am 30.01.2017 um 12:23 schrieb Simon, Hausmann: >> Making a warning go away for compilers that we know support utf-8 may not >> come at the price of your life :) >> >> I for one am all in favor of requiring just the Qt source

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

Am 30.01.2017 um 12:23 schrieb Simon, Hausmann: > > > Making a warning go away for compilers that we know support utf-8 may > not come at the price of your life :) > > > I for one am all in favor of requiring just the Qt source code (not > talking about customer code) to be encoded in a 24 year

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

Making a warning go away for compilers that we know support utf-8 may not come at the price of your life :) I for one am all in favor of requiring just the Qt source code (not talking about customer code) to be encoded in a 24 year old standard and add all the necessary flags to the

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

Am 30.01.2017 um 11:40 schrieb Giuseppe D'Angelo: > Il 30/01/2017 11:35, Viktor Engelmann ha scritto: >> As far as I can see, all our codes *are* UTF-8 encoded (a least they >> should be, IMHO), so why would we sneak our UTF8 in behind it's back (in >> 2017!) instead of just telling the compiler

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

Il 30/01/2017 11:35, Viktor Engelmann ha scritto: > As far as I can see, all our codes *are* UTF-8 encoded (a least they > should be, IMHO), so why would we sneak our UTF8 in behind it's back (in > 2017!) instead of just telling the compiler the encoding we are using? So *all* of our compilers

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

Am 30.01.2017 um 02:21 schrieb Thiago Macieira: > That's usually one of the problematic ones. > > Not on this file, though: > > qCDebug(lcTuioSet) << "Processing SET for token " << classId << id << " @ > " << x << y << "∡" << angle << > > That's easy to fix by using "\342\210\241" instead.

Re: [Development] Improve performance (listview + onVerticalVelocityChanged)

Am 26.01.2017 um 20:09 schrieb Bernhard B: I think I solved my problem. In case someone is interested, that's my solution: Can't you bind the "visible" properties to the velocity? Then it doesn't have to execute so much javascript and the code looks cleaner and more declarative. The bindings

Re: [Development] Calendar Systems proposal

On Mon, Jan 30, 2017, at 08:59 AM, Hamed Masafi wrote: > I'm working on qml support of calendar system, > for porting this mechanism to qml we have two option: Have you considered whether Date.prototype.toLocaleDateString could be of use for this? See:

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

I have a unit test for webengine that sends an HTTP Post request which includes several unicode characters (outside of ä,ö,ü or other Latin1 characters). I deliberately did that to make the test harder to pass. Am 29.01.2017 um 10:33 schrieb André Pönitz: > On Sun, Jan 29, 2017 at 12:13:48PM

Re: [Development] Calendar Systems proposal

> Now question is that: witch form is preferred? Will be case (1) break Qt > rules? I don't know about QML and it'd design principles, but I like option 3. Though it must take that calendar instance as second argument I suppose: var out = date.toString("/MM/dd", Qt.JalaliCalendar); // Is

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

Liang Jian (29 January 2017 05:13): >Start from qt-5.8 I can't build qt anymore under Windows(simplified > chinese locale). Since there is a file > src/plugins/generic/tuiotouch/qtuiohandler.cpp which contain > non-latin-1 character, msvc2015 assume the source code's character set > should be

Re: [Development] Calendar Systems proposal

Hamed Masafi (30 January 2017 08:59): > I'm working on qml support of calendar system, That shall complement Soroush Rabiei's work on the C++ side: https://codereview.qt-project.org/182341 http://bugreports.qt.io/browse/QTBUG-58404 Prior discussion:

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

Il 30/01/2017 02:21, Thiago Macieira ha scritto: > So, we should: > a) still avoid non-ASCII in our source files, aside from comments > b) allow non-ASCII in comments, as needed Didn't we have issues with UTF-8 in comments too, when using MSVC? > c) turn the -utf-8 option on for MSVC2015U3.

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

https://codereview.qt-project.org/#/c/183817/ On Mon, Jan 30, 2017 at 4:42 PM, Marc Mutz wrote: > On Monday 30 January 2017 02:21:57 Thiago Macieira wrote: > > qCDebug(lcTuioSet) << "Processing SET for token " << classId << id > << " > > @ " << x << y << "∡" << angle <<

Re: [Development] Policy for examples with large resources?

Hi Konstantin On Friday, 27 January, 2017 at 17:48, Konstantin Tokarev wrote: > 27.01.2017, 19:41, "Oswald Buddenhagen" : >> On Fri, Jan 27, 2017 at 03:48:54PM +, Sean Harmer wrote: >>>  Is there a way we can get a git-lfs repo set up as a submodule to be >>>  

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

On Monday 30 January 2017 02:21:57 Thiago Macieira wrote: > qCDebug(lcTuioSet) << "Processing SET for token " << classId << id << " > @ " << x << y << "∡" << angle << > > That's easy to fix by using "\342\210\241" instead. Which is totally and utterly opaque. So much so that one feels