[Development] New Qt 5.5 snapshot available
Hi, New 5.5 snapshot available, Windows: http://download.qt.io/snapshots/qt/5.5/5.5.0-beta/2015-05-25_65/ Linux: http://download.qt.io/snapshots/qt/5.5/5.5.0-beta/2015-05-25_93/ Mac: http://download.qt.io/snapshots/qt/5.5/5.5.0-beta/2015-05-25_76/ Qt5 changes in this snapshot: https://codereview.qt-project.org/#/c/112430/ : Patch Set 9: * qt3d 4b42d21...c09b9c5 (5): > Remove FBO complete debug > Allow to have different clearColor per RenderView > Register TextureRectangle and TextureBuffer to QML > RenderTexture: handle the unique flag and append the node id to the dna when > set to true which makes the texture unique > QAbstractTextureProvider add unique property * qtbase 7d3f353...009b11c (16): > QStateMachine: fix RestorableId exception specification > Fix GLES3 functions on iOS > Let MSVC treat warnings as errors > WinRT/Winphone: Fix warnings in qtbase > Fix typo and formatting in QWidget font documentation. > Doc: added doc to undocumented functions > Doc: added doc for non-documented functions > Fix QtPrivate::IsQEnumHelper > WinRT: fix namespaced build > QStyle debug helpers: refactor dead code > QMenuBar: honor the left widget size hint > Fix exclusion for legacy Open GL examples. > xcode generator: dont change output_dir when opening a pbx file directly > QFileSystemModel: remove useless check > tst_QDialog::snapToDefaultButton - tune the test for OS X > Tests: Remove EXPECT_FAIL in tst_QWidget::widgetAt() * qtcanvas3d ea4d771...f7ef801 (4): > Fix Canvas3D_conformance_gl_get_calls related conformance issues > Improved example UIs > Fix uniform1iv when using javascript arrays > Fixes getUniform() method return values and types. * qtconnectivity 193ed20...2928c9d (1): > Remove some Tech preview remnants from Bluetooth documentation * qtdeclarative 30aa0a1...2cb2c8f (1): > MSVC: Fix compiler warning * qtmultimedia f61c89a...9faaf42 (2): > Fix documentation for Camera flash mode enum. > Fix typo in QCameraViewfinderSettingsControl documentation * qtqa 96360b9...3fdc5e3 (1): > Add sync.profile for qtqa * qtquick1 7bf5bb1...79aff17 (1): > Remove duplicated Qt Designer plugin from tools. * qtquickcontrols 1f0daa7...68cb823 (1): > FontDialog: support i18n for the display names of font.weight enums * qttools 5dbd90b...ab5d643 (1): > Qt Designer: Update widget box labels * qtwayland 007d73e...f15384f (2): > Fix the build error in public headers > Add safety check in QWaylandInputDevice::Keyboard::modifiers() * qtwebkit 0f68b45...90d5224 (2): > Merge "Merge remote-tracking branch origin/5.4 into 5.5" into refs/staging/5.5 > Fix potential crash on exit ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Support for custom Diffie-Hellman parameters in QSslSocket
Hi, I've been working on adding the ability to set custom DH parameters for QSslSocket and I want to start discussing an API for the feature, rather than jumping directly to a code review. I have a preliminary patch that adds a sketch of the API I'm envisioning: https://gist.github.com/mkrautz/699f3c7fb22f48b7059c (It's untested, but it builds...) Basically, what I'm envisioning is - An opaque (for the user) QSslDiffieHellmanParameters class. - It loads DH parameters either as PEM or DER via a constructor that takes a QByteArray or a QIODevice (like QSslKey). - After loading, isNull() can be used to check if the DH parameters were loaded, and were valid (OpenSSL backend uses DH_check -- not sure what should be done on SecureTransport, if anything?). - Internally, the QSslDiffieHellmanParameters object stores a DER-encoded version of the parameters. (This makes it easily loadable in both OpenSSL and SecureTransport) - A public QSslConfiguration::setDiffieHellmanParameters() to set the DH parameters. - A public (but not in the public headers) QSslConfiguration::diffieHellmanParameters() for internal use by the backends. - QSslDiffieHellmanParametersPrivate will befriend QSslContext (for OpenSSL) and an equivalent for SecureTransport to allow the implementations to access the DER encoded data of the QSslDiffieHellmanParameters. I did a cursory web search for the ability to set DH parameters for WinRT listeners, but I don't think that's possible -- so I haven't considered that, for now... Let me know what you think. Thanks, Mikkel ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtModeling - the last mile
On 26/05/15 07:18, Sandro Andrade wrote: > On Wed, Apr 29, 2015 at 6:08 PM, Sandro Andrade wrote: >> On Wed, Apr 29, 2015 at 6:01 PM, Konstantin Ritt wrote: >>> Any links/code/docs?) >> >> Yes, sorry :) >> >> Wiki page: http://wiki.qt.io/QtModeling >> Git repository: http://www.gitorious.org/qt/qtmodeling >> DuSE-MT (QtModeling-based tool) website: http://duse.sourceforge.net/ >> DuSE-MT repository: www.gitorious.org/duse-mt/duse-mt >> >> Some posts about QtModeling: >> https://liveblue.wordpress.com/2012/12/11/call-for-arms-qtmofqtuml/ >> https://liveblue.wordpress.com/2013/01/21/qtmofqtuml-xmi-serialization-and-metamodel-plugins/ >> https://liveblue.wordpress.com/2013/11/18/how-cute-can-modeling-be/ >> >> Cheers, >> Sandro > > So, anyone ? Let's put this baby out :) > I'll present a talk about QtModeling at Akademy this year. If any of > you guys is also heading there, we might > schedule a chat. BTW, the page at http://duse.sourceforge.net/ has quite a few broken links pointing to http://qt.gitorious/qtplayground/qtmof. Shouldn't they point to https://github.com/qtproject/qtmodeling instead? Krys > > Cheers, > Sandro > >> >>> >>> Konstantin >>> >>> 2015-04-30 0:26 GMT+04:00 Sandro Andrade : Hi there, Some time ago, I started the development of QtModeling : a qt add-on aimed at providing metamodeling features and the basic infrastructure for dealing with software models. It already has a lot of interesting features and now I have the available time to making it good enough to be released. There are, however, some design choices I would like to discuss and get some feedback from some of you guys. Implementing the UML metamodel, for example, requires a considerable time investiment. Part of this is already done, but I would like to set up a plan to incrementally release such features. So, would anyone be willing to provide some guidance and keep up with QtModeling to its release ? Thanks in advance, -- Sandro ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development >>> >>> > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtModeling - the last mile
On Wed, Apr 29, 2015 at 6:08 PM, Sandro Andrade wrote: > On Wed, Apr 29, 2015 at 6:01 PM, Konstantin Ritt wrote: >> Any links/code/docs?) > > Yes, sorry :) > > Wiki page: http://wiki.qt.io/QtModeling > Git repository: http://www.gitorious.org/qt/qtmodeling > DuSE-MT (QtModeling-based tool) website: http://duse.sourceforge.net/ > DuSE-MT repository: www.gitorious.org/duse-mt/duse-mt > > Some posts about QtModeling: > https://liveblue.wordpress.com/2012/12/11/call-for-arms-qtmofqtuml/ > https://liveblue.wordpress.com/2013/01/21/qtmofqtuml-xmi-serialization-and-metamodel-plugins/ > https://liveblue.wordpress.com/2013/11/18/how-cute-can-modeling-be/ > > Cheers, > Sandro So, anyone ? Let's put this baby out :) I'll present a talk about QtModeling at Akademy this year. If any of you guys is also heading there, we might schedule a chat. Cheers, Sandro > >> >> Konstantin >> >> 2015-04-30 0:26 GMT+04:00 Sandro Andrade : >>> >>> Hi there, >>> >>> Some time ago, I started the development of QtModeling : a qt add-on >>> aimed at providing metamodeling features and the basic infrastructure >>> for dealing with software models. It already has a lot of interesting >>> features and now I have the available time to making it good enough to >>> be released. >>> >>> There are, however, some design choices I would like to discuss and >>> get some feedback from some of you guys. Implementing the UML >>> metamodel, for example, requires a considerable time investiment. Part >>> of this is already done, but I would like to set up a plan to >>> incrementally release such features. >>> >>> So, would anyone be willing to provide some guidance and keep up with >>> QtModeling to its release ? >>> >>> Thanks in advance, >>> -- >>> Sandro >>> ___ >>> Development mailing list >>> Development@qt-project.org >>> http://lists.qt-project.org/mailman/listinfo/development >> >> ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt Quick Controls 2.0
> On 25 May 2015, at 13:04, manish sharma <83.man...@gmail.com> wrote: > > Thanks J-P for your reply. > > I was under assumption that my entire code will just work out of the box, I > need to just replace import statement from 1.* to 2.0. But looks like i need > to move my code from style code to individual control properties. Unfortunately, the level of performance improvements we’re aiming for, it’s not possible to achieve whilst maintaining backwards compatibility. Radical architectural and conceptual changes were needed. Thus the proposal of giving it a new major version number. -- J-P Nurmi ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt Quick Controls 2.0
Thanks J-P for your reply.
I was under assumption that my entire code will just work out of the box, I
need to just replace import statement from 1.* to 2.0. But looks like i
need to move my code from style code to individual control properties.
Thanks,
Manish
On Mon, May 25, 2015 at 2:33 PM, Nurmi J-P wrote:
> > On 25 May 2015, at 08:56, manish sharma <83.man...@gmail.com> wrote:
> >
> > Hi,
> >
> > I was reading
> https://blog.qt.io/blog/2015/03/31/qt-quick-controls-for-embedded/ and it
> looks very promising.
> >
> > Currently I am using QtQuickControls 1.3 and I am customizing look and
> feel by extending QtQuick.Controls.Styles.
> >
> > I just browsed through qtquickcontrols2 code and i could not find Style
> hooks. Is it by design Or something which is coming up?
>
> Hi Manish,
>
> This is what the “styles” section in the blog post talks about:
>
> > The concept of styling is changing in a way that styles no longer
> provide components
> > that are dynamically instantiated by controls, but controls themselves
> consist of delegates
> > that can be replaced without dynamic instantiation.
>
> In fact, any visual part of any control can be replaced by your own.
> Here’s an example of a Button with a custom background. The background is a
> simplified version Qt Quick Controls 1 Base style’s Button background.
>
> Button {
> id: control
> text: "Button"
> Theme.selectedTextColor: "black" // WIP! This will change...
> background: Rectangle {
> radius: 3
> border.color: control.activeFocus ? "#47b" : "#999"
> gradient: Gradient {
> GradientStop { color: control.pressed ? "#aaa" :
> "#fefefe"; position: 0 }
> GradientStop { color: control.pressed ? "#ccc" :
> "#e3e3e3"; position: control.pressed ? 0.1 : 1 }
> }
> Rectangle {
> radius: 3
> anchors.fill: parent
> color: control.activeFocus ? "#194477bb" :
> "transparent"
> Behavior on color { ColorAnimation { duration: 100 } }
> }
> }
> }
>
> Disclaimer: these things are still heavily work in progress.
>
> --
> J-P Nurmi
>
>
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt Quick Controls 2.0
> On 25 May 2015, at 08:56, manish sharma <83.man...@gmail.com> wrote:
>
> Hi,
>
> I was reading
> https://blog.qt.io/blog/2015/03/31/qt-quick-controls-for-embedded/ and it
> looks very promising.
>
> Currently I am using QtQuickControls 1.3 and I am customizing look and feel
> by extending QtQuick.Controls.Styles.
>
> I just browsed through qtquickcontrols2 code and i could not find Style
> hooks. Is it by design Or something which is coming up?
Hi Manish,
This is what the “styles” section in the blog post talks about:
> The concept of styling is changing in a way that styles no longer provide
> components
> that are dynamically instantiated by controls, but controls themselves
> consist of delegates
> that can be replaced without dynamic instantiation.
In fact, any visual part of any control can be replaced by your own. Here’s an
example of a Button with a custom background. The background is a simplified
version Qt Quick Controls 1 Base style’s Button background.
Button {
id: control
text: "Button"
Theme.selectedTextColor: "black" // WIP! This will change...
background: Rectangle {
radius: 3
border.color: control.activeFocus ? "#47b" : "#999"
gradient: Gradient {
GradientStop { color: control.pressed ? "#aaa" : "#fefefe";
position: 0 }
GradientStop { color: control.pressed ? "#ccc" : "#e3e3e3";
position: control.pressed ? 0.1 : 1 }
}
Rectangle {
radius: 3
anchors.fill: parent
color: control.activeFocus ? "#194477bb" : "transparent"
Behavior on color { ColorAnimation { duration: 100 } }
}
}
}
Disclaimer: these things are still heavily work in progress.
--
J-P Nurmi
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
[Development] Branching '5.5.0' from '5.5' started
Hi all, Branching '5.5.0' from '5.5' is ongoing. '5.5.0' branch is created & you should start using it for changes targeted to Qt 5.5.0 release. Downmerge from '5.5' to '5.5.0' will be done next Monday (1st June) so there should be enough time to finalize ongoing changes in '5.5' & start using '5.5.0'. After downmerge next Monday '5.5' branch will be for '5.5.1' release. As usual Ossi is taking re-targeting requests from '5.5' to '5.5.0' as well. Please remember: no any nice-to-have changes in anymore! br, Jani ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
