Re: [Development] [Announce] Qt 5.7.0 Beta released

On 4/25/2016 2:31 AM, Simon Hausmann wrote: Hi, Thank you for your feedback. Could you please elaborate what kind of changes you'd like to see to the QQmlComponent API? It is not clear to me what you mean by "compiling loaded QML from a byte array". Similarly, could you please explain wh

Re: [Development] [Announce] Qt 5.7.0 Beta released

Jani & Tuuka: There is a reference to the upcoming Qt Quick Compiler in 5.8 in the 5.7 beta announcment. http://blog.qt.io/blog/2016/04/21/qt-5-7-beta-released/ Where do we send input to the people in charge of making 5.8 design decisions? Since it looks like this is going to a significant re

Re: [Development] [Qt bugreports] (QTCREATORBUG-15705) Xcode 7.2 IOS 9.2 Simulator Debugging not possible

Eike: Well, that is a bit of news, thank you for looking at this. Thank you for your effort in this regard. md On 3/3/2016 7:47 AM, Eike Ziller (via JIRA) wrote: Message Title Eike Ziller *commented* on Bug QTCREATORBUG-15705

Re: [Development] Qt 5.7 feature freeze postponed, new date to be agreed

Tuuka: I was looking around for "Coin CI" information on google. Can you provide links and additional insight into this CI? We have a thread on the interest list related to CI. md On 12/9/2015 9:58 AM, Turunen Tuukka wrote: Hi, 15th Jan sounds good to me as the new FF time for Qt 5.7. The

Re: [Development] QTBUG-46552 : QUdpsocket bug always present on 5.5.1 RC on Mac

Can you provide a sample project to reproduce this? On 9/24/2015 5:37 PM, qt next wrote: > Hi, > > I have tryed the RC1 for the 5.5.1 and it seems that I can always > reproduce the bug 46552, at least on mac platform. > > > > > ___ > Development mailin

Re: [Development] How to speed up QML for KDE5 without QML compiler

Ulf: Can you explain that a little more. Loaders trade startup delay for runtime cost. What are the units of measure for runtime cost? I am having trouble plotting in my mind how to plot the tradeoff. As startup delay goes up, does runtime cost go down? Thanks, md On 9/16/2015 5:15 AM, Ulf

Re: [Development] [Announce] Qt Creator 3.5.0 released

This may sound stupid but is there an easy way to have the Kits get automatically detected when you run the Qt Creator 3.5.0? I was running Qt Creator 3.4.2 before this from the Qt 5.4.2 installation. Manually adding kits is kind of a pain. md On 8/20/2015 7:03 AM, List for announcements regar

Re: [Development] qqmlengine/qqmlimport access

Simon: I just finished reviewing the QQuickImageProvider framework and that might also be an known interface pattern acceptable to the team. Component { source: "memory://myqmlprovider/myqmlcomponent" } And it may just "fit" nicely into the current "qrc:" pattern. Just my 2 cents... md On 6/9

Re: [Development] qqmlengine/qqmlimport access

Robin: I am fairly new to the process, and just eyeballing the source trees does not give me a working understanding how the render thread and the GUI thread play nice together. So knowing the point at which to add a call to int QQmlEngine::addComponent(QByteArray& gbqml,QString gsimportname)

Re: [Development] qqmlengine/qqmlimport access

On 6/9/2015 1:02 AM, Simon Hausmann wrote: > On Tuesday, June 02, 2015 03:44:59 PM rpzrpz...@gmail.com wrote: >> On 5/29/2015 9:53 AM, mark diener wrote: >>> Hello dev list: >> Maybe after the 5.5 release, I would like to explore adding public >> access member functions to QQmlEngine.h/cpp: >> >> i

Re: [Development] Q_INVOKABLE QAbstractListModel

Konstantin & Olivier: I though this unknown base type might be missing from the meta compiler and thus not the framework recognizing AbstractList* but recognizing many other types. But there is a RegisterType option to make this all go away. Lightbulb going off right now Thanks to you both

Re: [Development] Q_INVOKABLE QAbstractListModel

Konstantin: Maybe you could add some useful guidance to your response. The point of interest is that it must be a QObject derived return. Maybe a pointer to a QObject. Or maybe there is another way to construct QAbstractListModel that will allow for a non-pointer return from Q_INVOKABLE? (But

Re: [Development] 5.4.1 OSX macdeployqt FAIL

: > On Monday 11 May 2015 11:02:47 m...@rpzdesign.com wrote: >> There is a huge amount of code and build infrastructure to learn just to >> get to a minimum level of competence on Qt 5.x. >> >> ---> I nominate you for “most drama in bug report” in this year’s awards. &g

Re: [Development] 5.4.1 OSX macdeployqt FAIL

Sorvig: There is a huge amount of code and build infrastructure to learn just to get to a minimum level of competence on Qt 5.x. ---> I nominate you for “most drama in bug report” in this year’s awards. Well, since you mention it, I nominate Sorvig for “best Qt community builder” in this year’

Re: [Development] How to have equivalent of function over-riding in Qml

Please do share when you get to the bottom of this. md On 7/10/2014 8:55 AM, travik wrote: > Ok!. That's cool and it is Qml's implementation of VTable, I guess!. > Thanks a lot again. Let me try it and come back. > > > > ___ > Development mailing lis

Re: [Development] Request for a sandbox area: Replicant

What we really want to know Charley is whether you drive a F-150 or a Prius. That will decide whether this is a Killer App. md On 6/1/2014 9:43 PM, charleyb123 . wrote: > This cross process stuff is starting to feel like 1996 and > remote procedure RPC calls, now using QT signals and slo

Re: [Development] Request for a sandbox area: Replicant

Bret: I am certainly open to Ford Motor Company sponsoring my flight to wherever this summit is taking place and we can dispose of the problem of my failure to attend. My talk would be titled, "How Bill Gates dreamed of using RPC to court his future yet unseen wife" Hell, that might even be qual

Re: [Development] Request for a sandbox area: Replicant

This cross process stuff is starting to feel like 1996 and remote procedure RPC calls, now using QT signals and slots. "" again for effect. One could review the history of microsoft and the fine RPC mechanisms that turned out to be mostly unusable, or maybe just unused. Keep the optimism in check

Re: [Development] Bringing Qt's high-dpi support to more platforms

eira wrote: > Em seg 26 maio 2014, às 09:04:28, m...@rpzdesign.com escreveu: >> Hopefully you are going to developer days in Berlin this summer. >> >> And Hopefully you are giving a presentation that will be available on >> youtube titled, "Qt Quick Developer Qu

Re: [Development] Bringing Qt's high-dpi support to more platforms

e like the SUPER HDPI Android 8.9 Cheers, marco On 5/26/2014 8:51 AM, Sorvig Morten wrote: > > On 26 May 2014, at 07:59, Ziller Eike wrote: > >> >> On May 23, 2014, at 6:03 PM, m...@rpzdesign.com wrote: >> >>> Sorvig: >>> >>>> F

Re: [Development] Bringing Qt's high-dpi support to more platforms

Sorvig: >From the latest new front: http://bgr.com/2014/03/18/nexus-9-specs-details/ Digitimes on Tuesday cited its own research arm in reporting that Google will launch two new Nexus tablets in 2014. In addition to an updated Nexus 7, Google is reportedly prepping a new 8.9-inch Nexus tablet th

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

Thomas & Tero: There is no way that I can make it to the contributors summit, but Thomas' message might be a important discussion pience when you arrive in Berlin. Related to points 5,6,7 of Thomas' message Below: Is there a class diagram on the current code base? This would help newbies when t

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] Question about Qt's future

014 12:19 PM, Thiago Macieira wrote: > Em seg 21 abr 2014, às 10:59:43, m...@rpzdesign.com escreveu: >> Can Qt Widgets design pattern be brought forward using the same OpenGL >> foundation >> that QML uses to instantiate controls? > > Short answer: no. > > Long answe

Re: [Development] Question about Qt's future

iscussion even if Finland and Norway are on Holiday! Cheers, md On 4/21/2014 9:31 AM, Yves Bailly wrote: > On 21/04/2014 04:53, Thiago Macieira wrote: >> Em dom 20 abr 2014, às 22:37:11, m...@rpzdesign.com escreveu: >>> Isn't Qt Widgets so mature that they are stable?

Re: [Development] Question about Qt's future

Michael: That is a great question. I hope you get answers that focus on the mobile side of things (IOS/Android) With Qt 5.3.0 release just around the corner, will Qt Widgets be able to run stable on IOS and ANdroid? Many comments I have seen on this list refers to Qt Widgets as a desktop orie

[Development] Android / IOS

Hello Development: I am newly arrived on Qt 5.2x scene and wanted to know how to contribute code, fixes, and testing for Qt 5.3.x of IOS and Android. Specifically, I want to focus on QT C++ <-> Objective C/Cocoa bridge and QT C++ <-> Android/Java/JNI. Is the development email list a free flowin