Re: [Development] No SSL on iOS ?

> On 29 Apr 2014, at 00:16, Jeremy Lainé wrote: > >> On 04/28/2014 11:44 AM, Nichols Andy wrote: >> It is possible still in the packaged versions of Qt for iOS to make >> connections using SSL via QNetworkAccessManager as there is a backend that >> uses Apples crypto API, but without OpenSSL

Re: [Development] Question about Qt's future

On 28.04.2014 18:01, Tony Van Eerd wrote: >> >> On 25.04.2014 12:18, Joerg Bornemann wrote: >>> >>> Yep, I hear people keep repeating the mantra "QML is declarative. It's >>> just QML/JS that isn't." >> >> I think the "declarative-mantra" is a good idea, especially when used for >> _specifying_ (no

Re: [Development] Question about Qt's future

On 28.04.2014 16:00, Roland Winklmeier wrote: > 2014-04-27 13:31 GMT+02:00 Peter Kümmel >: > > On 21.04.2014 13 :39, Roland Winklmeier wrote: > > - Memory consumption: Even a mini example took about 70 MB of memory, > > QtWidgets need a lot less. This is n

Re: [Development] No SSL on iOS ?

On 29 Apr 2014 00:39, Thiago Macieira wrote: > > Em ter 29 abr 2014, às 00:16:43, Jeremy Lainé escreveu: > > What would the best course of action be to add support for secure > > websockets > > on iOS? > > Probably to add a new QSslSocket backend that uses the Apple API. OK, I'll take a look

Re: [Development] Perceptions/Understandings of the QML language [was: Question about Qt's future]

On Mon, Apr 28, 2014 at 2:34 PM, André Pönitz wrote: > On Mon, Apr 28, 2014 at 11:12:47AM -0700, Alan Alpert wrote: >> Yes, I agree that more rigorous and agreed definitions would be >> helpful. It also takes time, and impedes innovation, so I'm not sure >> if we're quite mature enough to "nail do

Re: [Development] Perceptions/Understandings of the QML language [was: Question about Qt's future]

On Mon, Apr 28, 2014 at 03:02:50PM -0700, Thiago Macieira wrote: > Em seg 28 abr 2014, às 23:34:21, André Pönitz escreveu: > > On Mon, Apr 28, 2014 at 11:12:47AM -0700, Alan Alpert wrote: > > > Yes, I agree that more rigorous and agreed definitions would be > > > helpful. It also takes time, and im

Re: [Development] No SSL on iOS ?

Em ter 29 abr 2014, às 00:16:43, Jeremy Lainé escreveu: > On 04/28/2014 11:44 AM, Nichols Andy wrote: > > It is possible still in the packaged versions of Qt for iOS to make > > connections using SSL via QNetworkAccessManager as there is a backend > > that uses Apples crypto API, but without OpenSS

Re: [Development] No SSL on iOS ?

On 04/28/2014 11:44 AM, Nichols Andy wrote: > It is possible still in the packaged versions of Qt for iOS to make > connections using SSL via QNetworkAccessManager as there is a backend that > uses Apples crypto API, but without OpenSSL support you can’t use any of the > API’s in Qt that use Ope

Re: [Development] Perceptions/Understandings of the QML language [was: Question about Qt's future]

After 10 years, time to refactor to organize the stack. md On 4/28/2014 6:02 PM, Thiago Macieira wrote: > Em seg 28 abr 2014, às 23:34:21, André Pönitz escreveu: >> On Mon, Apr 28, 2014 at 11:12:47AM -0700, Alan Alpert wrote: >>> Yes, I agree that more rigorous and agreed definitions would be >>>

Re: [Development] Perceptions/Understandings of the QML language [was: Question about Qt's future]

Em seg 28 abr 2014, às 23:34:21, André Pönitz escreveu: > On Mon, Apr 28, 2014 at 11:12:47AM -0700, Alan Alpert wrote: > > Yes, I agree that more rigorous and agreed definitions would be > > helpful. It also takes time, and impedes innovation, so I'm not sure > > if we're quite mature enough to "na

Re: [Development] Perceptions/Understandings of the QML language [was: Question about Qt's future]

On Mon, Apr 28, 2014 at 11:12:47AM -0700, Alan Alpert wrote: > Yes, I agree that more rigorous and agreed definitions would be > helpful. It also takes time, and impedes innovation, so I'm not sure > if we're quite mature enough to "nail down" QML just yet. Should be > soon though, in the next few

Re: [Development] Perceptions/Understandings of the QML language [was: Question about Qt's future]

On Mon, Apr 28, 2014 at 10:36:22PM +0800, Sze Howe Koh wrote: > On 25 April 2014 18:18, Joerg Bornemann wrote: > > On 25-Apr-14 04:21, Sze Howe Koh wrote: > > > >> I consider QML and JavaScript to be different languages. JavaScript > >> can be embedded into QML to extend QML's capabilities, just l

Re: [Development] Perceptions/Understandings of the QML language [was: Question about Qt's future]

On Mon, Apr 28, 2014 at 12:16 PM, Bubke Marco wrote: > > > Alan Alpert: >> That said, part of the path from becoming a trailblazer to being the >> dominant force ruling the world is IDE and tooling support. We want to >> improve tooling capabilities wherever we can do so (without >> compromising t

Re: [Development] Perceptions/Understandings of the QML language [was: Question about Qt's future]

Alan Alpert: > That said, part of the path from becoming a trailblazer to being the > dominant force ruling the world is IDE and tooling support. We want to > improve tooling capabilities wherever we can do so (without > compromising the 'untooled' developer experience - I know they Hmm, again a

Re: [Development] Perceptions/Understandings of the QML language [was: Question about Qt's future]

On Mon, Apr 28, 2014 at 7:36 AM, Sze Howe Koh wrote: > On 25 April 2014 18:18, Joerg Bornemann wrote: >> On 25-Apr-14 04:21, Sze Howe Koh wrote: >> >>> I consider QML and JavaScript to be different languages. JavaScript >>> can be embedded into QML to extend QML's capabilities, just like how >>>

Re: [Development] [QIODevice]How to correctly treat/understand of the documentation?

Em seg 28 abr 2014, às 17:04:31, Denis Shienkov escreveu: > Hi Thiago, > > > By the way, what is that tx-empty event? > > E.g., it is an signal of QSocketNotifier::activated(fd) for the Write type > of notifier. No, it isn't. The socket notifier activates when there's buffer available in the k

Re: [Development] [QIODevice]How to correctly treat/understand of the documentation?

Em seg 28 abr 2014, às 11:16:27, Oswald Buddenhagen escreveu: > On Sun, Apr 27, 2014 at 01:34:52PM -0700, Thiago Macieira wrote: > > yeah, but serial ports can be operated without flow control. if the > kernel does not buffer indefinitely (which seems plausible, as otherwise > one could DoS it), d

Re: [Development] No SSL on iOS ?

Em seg 28 abr 2014, às 09:44:49, Nichols Andy escreveu: > The packaged (binary) versions of iOS do not include support for OpenSSL > because that would require the static linking (and thus distribution) of > OpenSSL which can be problematic due to export restrictions. It is not > possible to build

Re: [Development] No SSL on iOS ?

Unfortunately dlopen is not possible :( Simon Opprinnelig melding Fra: Thiago Macieira Sendt: 18:14 mandag 28. april 2014 Til: development@qt-project.org Emne: Re: [Development] No SSL on iOS ? Em seg 28 abr 2014, às 09:44:49, Nichols Andy escreveu: > The packaged (binary) versions of iOS do

Re: [Development] Perceptions/Understandings of the QML language [was: Question about Qt's future]

On 28 April 2014 22:36, Sze Howe Koh wrote: > Previously, I called [the declarative bits] "QML". But after considering how > people use > this language, and studying other markup languages, I've changed my > mind and think that [wew should be called "QML". OTOH, that's not compatible with where

Re: [Development] Qt binaries with inlined functions

Em seg 28 abr 2014, às 11:15:23, Koehne Kai escreveu: > > -Original Message- > > From: development-bounces+kai.koehne=digia@qt-project.org > > Subject: [Development] Qt binaries with inlined functions > > > > Hello all, > > > > I'd like to start a discussion about .https:/

Re: [Development] Question about Qt's future

> > On 25.04.2014 12:18, Joerg Bornemann wrote: > > > > Yep, I hear people keep repeating the mantra "QML is declarative. It's > > just QML/JS that isn't." > > I think the "declarative-mantra" is a good idea, especially when used for > _specifying_ (not programming) the GUI. > > At Adobe they tr

Re: [Development] Question about Qt's future

On 28-Apr-14 16:36, Sze Howe Koh wrote: > To check if I've understood you correctly: You've found that > classifying QML as "declarative" distorts developers' expectations of > the tools? The term "declarative" is mainly used here as a synonym for "perfectly toolable". So yes, I would expect tha

[Development] Perceptions/Understandings of the QML language [was: Question about Qt's future]

On 25 April 2014 18:18, Joerg Bornemann wrote: > On 25-Apr-14 04:21, Sze Howe Koh wrote: > >> I consider QML and JavaScript to be different languages. JavaScript >> can be embedded into QML to extend QML's capabilities, just like how >> it can be embedded into HTML to extend HTML's capabilities. >

Re: [Development] new Qt5.3 RC snapshot available

Yes, I see the JIRA status, but I tried qt-opensource-mac-x64-android-ios-5.3.0-RC_2014-04-27_10-54-10-50.dmg and all other snapshots later than qt-opensource-mac-x64-android-ios-5.3.0-RC_2014-04-16_06-16-00-40.dmg, this issue still exists. Is there any auto test case to verify this kind of issues

Re: [Development] new Qt5.3 RC snapshot available

On Monday 28. April 2014 22.01.32 Yang Fan wrote: > QTBUG-38526 is not resolved, it should block the release. It's being worked on, as you can see if you look into JIRA. The fix is integrating at this moment. Have you tested it? Simon > On Mon, Apr 28, 2014 at 3:51 PM, Heikkinen Jani wrote:

Re: [Development] new Qt5.3 RC snapshot available

QTBUG-38526 is not resolved, it should block the release. On Mon, Apr 28, 2014 at 3:51 PM, Heikkinen Jani wrote: > Hi all, > > > > We have new snapshot available in > http://download.qt-project.org/snapshots/qt/5.3/5.3.0-RC/2014-04-28_77/ > > These packages aren’t yet official RC candidate pack

Re: [Development] Question about Qt's future

2014-04-27 13:31 GMT+02:00 Peter Kümmel : > On 21.04.2014 13:39, Roland Winklmeier wrote: > > - Memory consumption: Even a mini example took about 70 MB of memory, > > QtWidgets need a lot less. This is not a complain, I know the JS runtime > > needs its initial memory. It was just one factor, bec

Re: [Development] [QIODevice]How to correctly treat/understand of the documentation?

Hi Oswald, > a separate signal would be redundant, as checking byteToWrite() == 0 in > the slot called from bytesWritten() is sufficient. Can you, please, more explain of your idea? BR, Denis 2014-04-28 13:16 GMT+04:00 Oswald Buddenhagen : > On Sun, Apr 27, 2014 at 01:34:52PM -0700, Thiago

Re: [Development] [QIODevice]How to correctly treat/understand of the documentation?

Hi Thiago, > By the way, what is that tx-empty event? E.g., it is an signal of QSocketNotifier::activated(fd) for the Write type of notifier. > Note that sockets and pipes don't > have that, so please don't make QSerialPort use that by default. You can add > an extra signal to QSerialPort to ind

Re: [Development] Qt binaries with inlined functions

I think it depends on whether you see bindings as a single case or as multiple cases (one per binding). About other, let's say, types of projects - I am not aware. About an option - do you mean an option in the, say, online installer? If it's a compile option, I'm afraid you might as well not b

Re: [Development] Question about Qt's future

On Mon, Apr 28, 2014 at 4:39 AM, Hartmann Thomas wrote: > Hi, > > gluing together C++ and Java Script is currently not always that easy. > The solution I propose is the option to write C++ code in the exact same > way you currently write Java Script code. > This means every QML context/component c

Re: [Development] Qt binaries with inlined functions

> -Original Message- > From: Olivier Goffart [mailto:oliv...@woboq.com] > [...] > Maybe it should go in qt_module.prf Thanks, that takes me one step further - linking Qt5Gui fails next. Anyhow, Qt5Core succeeded: Size of libQt5Core.so.5.3.0 without patch:5.9M Size of libQt5Core.so.5.3.0

Re: [Development] Qt binaries with inlined functions

On Monday 28 April 2014 11:15:23 Koehne Kai wrote: > > -Original Message- > > From: development-bounces+kai.koehne=digia@qt-project.org > > Subject: [Development] Qt binaries with inlined functions > > > > Hello all, > > > > I'd like to start a discussion about .https://bu

Re: [Development] qtcore/qt.html is missing

Hi, Not a packaging issue, but an actual documentation problem related to cross-module dependencies. Fix at https://codereview.qt-project.org/84195 Thanks for spotting it! \topi From: development-bounces+topi.reinio=digia@qt-project.org [mailto:development-bounces+topi.reinio=digia@qt-

Re: [Development] QtQml value types

2014-04-24 22:42 GMT+02:00 Dominik Holland : > > I like that idea, but couldn't we do something like this ? > > qRegisterWrapper(qMetaTypeId()) > > MyWrapper is a QObject based class which can whatever you want and gets > YourType as reference or per value. > > It would mean you create your wrappe

Re: [Development] Qt binaries with inlined functions

Unfortunately, I don't. Perhaps you need to add the flag to QMAKE_CFLAGS as well? Dimitar On Monday, April 28, 2014 2:15 PM, Koehne Kai wrote: > -Original Message- > From: development-bounces+kai.koehne=digia@qt-project.org > Subject: [Development] Qt binaries with inlined functio

Re: [Development] Qt binaries with inlined functions

> -Original Message- > From: development-bounces+kai.koehne=digia@qt-project.org > Subject: [Development] Qt binaries with inlined functions > > > > Hello all, > > I'd like to start a discussion about .https://bugreports.qt- > project.org/browse/QTBUG-32995. Please share you

Re: [Development] Question about Qt's future

On 28 Apr 2014, at 9:32 AM, Gunnar Sletta wrote: > > On 28 Apr 2014, at 07:53, Peter Kümmel wrote: >> > ... > >> ATM the problem is to get started because I don't know much about the >> current architecture of the graphic stack. > > http://qt-project.org/doc/qt-5/qtquick-visualcanvas-scenegr

Re: [Development] Question about Qt's future

Hi, gluing together C++ and Java Script is currently not always that easy. The solution I propose is the option to write C++ code in the exact same way you currently write Java Script code. This means every QML context/component can have a C++ object attached to it that implements a set of metho

Re: [Development] Question about Qt's future

Hi, good point and this shows why it is actually no that easy to come up with a nice solution. The most natural solution for me would be to just add the mouse property to the java script context of the function call. The java script context would be a C++ argument. slot: mouseAreaClicked(QJSC

Re: [Development] Question about Qt's future

On 28.04.2014 09:32, Gunnar Sletta wrote: >> ATM the problem is to get started because I don't know much about the >> current architecture of the graphic stack. > > http://qt-project.org/doc/qt-5/qtquick-visualcanvas-scenegraph.html > http://qt-project.org/doc/qt-5/qtquick-visualcanvas-scenegraph-r

Re: [Development] Question about Qt's future

Hartmann Thomas schreef op 28-4-2014 11:32: > Hi, > > yes, writting C++ inline in QML would be another "tooling nightmare". Also > what is the problem with: > > MouseArea { > onClicked: companion.mouseAreaClicked(); > } > > If tooling creates the companion object for you (In a wizard) and cod

Re: [Development] Question about Qt's future

> Also what is the problem with: > > MouseArea { > onClicked: companion.mouseAreaClicked(); > } Where is the event handler's argument (the one that's kind of invisible in QML and requires you to read the documentation, I think it's called "mouse" :-). Could this be a function binding instead?

Re: [Development] Question about Qt's future

On 28.04.2014 09:26, Thiago Macieira wrote: > Em seg 28 abr 2014, às 08:33:23, Peter Kümmel escreveu: ATM the problem is to get started because I don't know much about the current architecture of the graphic stack. Any hints where to start for a first hello world? >>> >>> Maybe a tra

Re: [Development] No SSL on iOS ?

Hi Martin, > I have installed qt-opensource-mac-x64-ios-5.3.0-beta.dmg > and while compiling my app, I get: > no member named 'sslConfiguration' in 'QNetworkReply' > which is happening when QT_NO_SSL is defined - which seems to be the case > in qconfig.h: > #if defined(QT_NO_OPENSSL) && defined(QT

Re: [Development] Question about Qt's future

Hi, yes, writting C++ inline in QML would be another "tooling nightmare". Also what is the problem with: MouseArea { onClicked: companion.mouseAreaClicked(); } If tooling creates the companion object for you (In a wizard) and code completion and code naviagtion (F2) works as expected? Ki

Re: [Development] [QIODevice]How to correctly treat/understand of the documentation?

On Sun, Apr 27, 2014 at 01:34:52PM -0700, Thiago Macieira wrote: > Em dom 27 abr 2014, às 11:08:44, Denis Shienkov escreveu: > > Here I am a little disagree. Because in Unbuffered mode, loss of data is > > exists. For example, in a case when the port accepts a data stream. And > > when the user ign

Re: [Development] Question about Qt's future

Hi, > Another idea is to allow C++ companion objects, that would > take the place of any Java Script code for people who > prefer C++. A companion object would be a QObject > paired with the QML object, that has access to the > QML context. The QObject would then define a couple > of signals/slots

Re: [Development] Updating JIRA components relating to events.

On Monday 28 April 2014 08:42:48 Blasche Alexander wrote: > I renamed it on request. It was such a minor change that I didn't see an > issue especially since the component doesn't have a default assignee. > Obviously that is not the case. No worries :) I may be using the components in a slightly n

Re: [Development] Updating JIRA components relating to events.

Hi, I renamed it on request. It was such a minor change that I didn't see an issue especially since the component doesn't have a default assignee. Obviously that is not the case. Paul, you have to rename your filter again. Filtering on the name string is rather stupid but that's what jira doe

Re: [Development] Question about Qt's future

Hi, while (at least for me) it is not really clear where exactly the boundary between declarative and functional programming lies, we could/should at least rule out control flow statements and anything with side effects in bindings. The statement "width: Math.floor(height)" could be considered

Re: [Development] Updating JIRA components relating to events.

On Friday 25 April 2014 17:27:23 Thiago Macieira wrote: > I've just noticed that the "GUI: Input methods" component in JIRA has got > an update now saying "(Non-Latin languages)". That is, it seems the > purpose of that component has changed to mean complex input methods only. > > I've been reass

[Development] new Qt5.3 RC snapshot available

Hi all, We have new snapshot available in http://download.qt-project.org/snapshots/qt/5.3/5.3.0-RC/2014-04-28_77/ These packages aren't yet official RC candidate packages but pretty close so please test these & verify your fixes! We are trying to put RC out during this week so please inform me

Re: [Development] Question about Qt's future

On 28 Apr 2014, at 07:53, Peter Kümmel wrote: > ... > ATM the problem is to get started because I don't know much about the > current architecture of the graphic stack. http://qt-project.org/doc/qt-5/qtquick-visualcanvas-scenegraph.html http://qt-project.org/doc/qt-5/qtquick-visualcanvas-scene

Re: [Development] Question about Qt's future

Em seg 28 abr 2014, às 08:00:56, Peter Kümmel escreveu: > On 27.04.2014 22:41, Thiago Macieira wrote: > > Em dom 27 abr 2014, às 13:31:33, Peter Kümmel escreveu: > >> Then adding 100MB just to run QML really hurts, and you start > >> looking for alternatives, like using only QWidgets with very > >>

Re: [Development] Question about Qt's future

Em seg 28 abr 2014, às 08:33:23, Peter Kümmel escreveu: > >> ATM the problem is to get started because I don't know much about the > >> current architecture of the graphic stack. > >> Any hints where to start for a first hello world? > > > > Maybe a translation from QML to a .ui file could be a fi

Re: [Development] Question about Qt's future

Em seg 28 abr 2014, às 07:35:10, Robert Iakobashvili escreveu: > Sorry, but the above is not helpful. > > I'd never jump to conclusions and statements without > in-hands knowledge of the subject to talk about. You asked for my personal opinion the moment that you emailed me directly without the