[Development] Branch request: wip/webassembly in Qt Declarative

2017-12-04 Thread Eskil Abrahamsen Blomfeldt
Hi, We currently have a WIP branch in Qt Base for the WebAssembly work, but it turns out that we will also need changes in Qt Declarative that significant enough that it would be good to keep them in a WIP branch until we merge the feature back. No CI needed. -- Eskil Abrahamsen Blomfeldt S

[Development] Qt 5.10.0 RC3 out

2017-12-04 Thread Jani Heikkinen
Hi, We have released Qt 5.10.0 RC3 today. Delta to RC2 as an attachment. With my current knowledge this should be now final Qt 5.10.0 content which we are planning to release this Thursday (if all still ok according to tests). Instructions how to get the release are here: https://wiki.qt.io/How

Re: [Development] QtCS 2017 QtCore sessions

2017-12-04 Thread Marc Mutz
On 2017-12-03 22:57, Allan Sandfeld Jensen wrote: On Samstag, 2. Dezember 2017 17:48:19 CET Marc Mutz wrote: If that analyis were true, you'd need to explain why it is, then, that the Qt containers now have more or less the same API as std ones, when in Qt 1 they were very different. And why I k

Re: [Development] QT printing via CUPS (advanced printing dalog box missing)

2017-12-04 Thread Albert Astals Cid
El dilluns, 20 de novembre de 2017, a les 23:45:18 CET, Thiago Macieira va escriure: > On segunda-feira, 20 de novembro de 2017 14:01:25 PST GMAIL wrote: > > This bug has been reported on QT ( see > > https://bugreports.qt.io/browse/QTBUG-54464) on *June 2016*. Almost a > > year and half now, the

Re: [Development] QtCS 2017 QtCore sessions

2017-12-04 Thread Allan Sandfeld Jensen
On Montag, 4. Dezember 2017 15:00:53 CET Marc Mutz wrote: > > Ah, well, yes. Nothing truly originates in C++, true. But, IIRC, the > Haskell name is maybe. So why is it QOptional and not QMaybe? Because > the C++ interface is used as the basis, not something from Haskell. > I believe the name "o

Re: [Development] QtCS 2017 QtCore sessions

2017-12-04 Thread Ville Voutilainen
On 4 December 2017 at 16:20, Allan Sandfeld Jensen wrote: > On Montag, 4. Dezember 2017 15:00:53 CET Marc Mutz wrote: >> >> Ah, well, yes. Nothing truly originates in C++, true. But, IIRC, the >> Haskell name is maybe. So why is it QOptional and not QMaybe? Because >> the C++ interface is used as

Re: [Development] QtCS 2017 QtCore sessions

2017-12-04 Thread Konstantin Tokarev
04.12.2017, 17:31, "Ville Voutilainen" : > On 4 December 2017 at 16:20, Allan Sandfeld Jensen wrote: >>  On Montag, 4. Dezember 2017 15:00:53 CET Marc Mutz wrote: >>>  Ah, well, yes. Nothing truly originates in C++, true. But, IIRC, the >>>  Haskell name is maybe. So why is it QOptional and not

Re: [Development] QtCS 2017 QtCore sessions

2017-12-04 Thread Thiago Macieira
On Monday, 4 December 2017 06:00:53 PST Marc Mutz wrote: > Ah, well, yes. Nothing truly originates in C++, true. But, IIRC, the > Haskell name is maybe. So why is it QOptional and not QMaybe? Because > the C++ interface is used as the basis, not something from Haskell. FYI, I wrote QMaybe some 9 t

Re: [Development] QT printing via CUPS (advanced printing dalog box missing)

2017-12-04 Thread Lars Knoll
On 4 Dec 2017, at 15:16, Albert Astals Cid mailto:albert.astals@kdab.com>> wrote: El dilluns, 20 de novembre de 2017, a les 23:45:18 CET, Thiago Macieira va escriure: On segunda-feira, 20 de novembro de 2017 14:01:25 PST GMAIL wrote: This bug has been reported on QT ( see https://bugreports

Re: [Development] QtCS 2017 QtCore sessions

2017-12-04 Thread Allan Sandfeld Jensen
On Montag, 4. Dezember 2017 15:30:49 CET Ville Voutilainen wrote: > On 4 December 2017 at 16:20, Allan Sandfeld Jensen wrote: > > On Montag, 4. Dezember 2017 15:00:53 CET Marc Mutz wrote: > >> Ah, well, yes. Nothing truly originates in C++, true. But, IIRC, the > >> Haskell name is maybe. So why i

Re: [Development] QtCS 2017 QtCore sessions

2017-12-04 Thread Ville Voutilainen
On 4 December 2017 at 21:29, Allan Sandfeld Jensen wrote: >> > I believe the name "optional" comes from Haskell and Java where it >> > appeared >> > first. The standard library only imports things that are already industry >> > standard, and once there were several implementations of optional out