Re: [Development] Remove OSX 10.6 Build?
On Jan 21, 2014, at 2:56 PM, Tor Arne Vestbø tor.arne.ves...@digia.com wrote: On 21/01/14 13:36 , Sorvig Morten wrote: I realize that if I’m the only one who want’s to keep supporting 10.6 then that’s not going to work. The most important thing to me is to have a somewhat predictable deprecation plan. For example (and at the risk of making this example “the plan”): 5.3 - Remove support from binary packages. 5.4 - 10.6 support is deprecated. 5.5? - Remove support. 5.3: - Remove support from binary packages - No CI = In practice, deprecated, so let's be explicit about it for 5.3 5.4 - Bump the dev branch to 5.4 - Remove 10.6 code as see fit - Apply 10.6 fixes to 5.3.x (stable) as normal The message is Qt 5.3 deprecates 10.6 support (but is available for source builds for the lifetime of 5.3), and 5.4 will remove it.” I’d support this plan, and additionally throw in: after 5.3 / Qt Creator 3.2: - drop support for compiling running Qt Creator on 10.6 We want to start using C++11 also in Qt Creator, and 10.6 is the only thing preventing that. Since 10.6 is deployment target only for Qt, we don’t necessarily need to keep “its IDE” running there (yes, that’s a Qt-centric way of looking at Qt Creator). Br, Eike -- Eike Ziller, Senior Software Engineer - Digia, Qt Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QML Image aliasing when animating
Interesting. I tried the layer.mipmap previously with no effect, I did’t catch
that one needed to “enable” it too. However, I just tried this, and although
it created a different, marginally smoother result is is still very noticeably
aliasing.
Here is a move of that test:
http://c4.dev.s3.amazonaws.com/QMLImageRenderQuality2.mov
In fact this version is starting to look very similar to the results I was
seeing with the font renders.
On Jan 21, 2014, at 11:50 PM, Gunnar Sletta gunnar.sle...@jolla.com wrote:
This is the expceted result. smooth: true uses bilinear filtering which is
what is supported in hardware. When scaling down, this starts to degrade. The
effect is drastic for high-contrast content like the edges of a font. Once go
get below 0.5x scale factor the sampling starts to ignore pixels and aliasing
become very visible.
The preferred solution is to prepare raster content (images in your case)
close to the size you intend to show them. If you must scale them down, then
use mipmapping. With the image element, you can get this by doing:
Image {
layer.enabled: true
layer.smooth: true
layer.mipmap: true
...
}
However, by enabling the layer you get an extra texture copy of your rather
large image, so it might be preferable to implement a custom QQuickItem which
returns a QSGSimpleTextureNode with a QSGTexture with mipmapping.
cheers,
Gunnar
On 22 Jan 2014, at 04:03, Joshua Kolden jos...@crackcreative.com wrote:
I’m getting boxed in with rendering bugs on two fronts. Originally I tried
to work with fonts for the following animation, but have both render quality
and font ‘subfamily’ selection bugs to deal with there. So I took the effort
to switch a lot of stuff around and use images instead, however I’m getting
aliasing artifacts now. I’m rather stuck at the moment for rendering a good
quality large font design.
This video shows the aliasing I’m talking about. There are 3 images here
one is 2048x512 and two are 512x512 for the Camera4 and C4 text logos. The
movie is captured pixel for pixel, and the images at their largest (in this
example) are smaller then the source resolution.
http://c4.dev.s3.amazonaws.com/QMLImageRenderQuality.mov
Here is an example of one of the Image invocations:
Image {
id: c4CameraImage
fillMode: Image.PreserveAspectFit
source: “path/to/c4camera.png
anchors.left: parent.left
anchors.top: parent.top
anchors.bottom: parent.bottom
smooth : true
opacity: 0.0
}
The animation is created with a number animation on the width and height of
the parent rectangles.
I’ve asked on IRC, and in the [interest] list, but one said it should just
work and the other didn’t reply.
Is this a known issue, a bug, or and I’m I doing it wrong?
Thanks,
j
___
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] QtMultimedia and GStreamer 1.0
2013/10/23 Jim Hodapp jim.hod...@canonical.com: Hello, Based on Ilay’s work [1], I’ve further ported the QtMultimedia code to GStreamer 1.0 and have added support for rendering on the new Ubuntu Touch platform. Right now, this will render to SurfaceFlinger or Mir. I’d like to work to get this QtMultimedia port upstreamed to the QtMultimedia project itself. If there is already another parallel effort going on, we should check for duplicate efforts and merge efforts. [2] So whoever is responsible for QtMultimedia upstream, can you please reply so we can get a discussion going? [1] http://qt-project.org/forums/viewthread/21995/ [2] https://github.com/jhodapp/qtmultimedia Thanks, Jim ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development Hi. Is gstreamer 1.0 integration planned for 5.3? -- regards, Tomasz Olszak ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] How to write a ChangeLog entry
-- Alex -Original Message- From: development-bounces+alexander.blasche=digia@qt-project.org [mailto:development-bounces+alexander.blasche=digia@qt-project.org] On Behalf Of Thiago Macieira Sent: Tuesday, 21 January 2014 17:58 To: development@qt-project.org Subject: Re: [Development] How to write a ChangeLog entry On terça-feira, 21 de janeiro de 2014 08:09:43, Blasche Alexander wrote: Why are you pushing change log items for modules outside of qtbase to qtbase? I'm editing everything in one file so it's easier for me, but I'll split them to each module after we're done. Ok good to know for the next time. QtBluetooth --- - Documentation: * Fix cases where device and service discovery classes emitted an error signal but the human readable error string was not adjusted. How is this a documentation issue? If it's a minor documentation fix, it probably isn't relevant for the changelog. The release branch of the git repo for this module has had the relevant fix for the above issue for some time. You mean in the changes file? It's the first time that I had to provide a changes file for my modules. Obviously I was a bit too ambitious ;) but yes: qt.gitorious.org/qt/qtconnectivity/blobs/release/dist/changes-5.2.1 -- Alex ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] frozen tickets on bugreports.qt-project.org in qt-mobility and qt-components
-Original Message- From: development-bounces+alexander.blasche=digia@qt-project.org [mailto:development-bounces+alexander.blasche=digia@qt-project.org] On Behalf Of Alan Ezust Exactly my point. Why does someone need superpowers in order to edit these tickets? Shouldn't it be possible for developers to reorganize or close or add info to these things? It doesn't serve any purpose to keep them open and frozen like this. Anyway, I am requesting said superpowers so I can help organize and triage these tickets. But I think they should be granted to all devs :-) I don't know why I didn't mention this yesterday, but QTCOMPONENTS and QTMOBILITY are frozen/read-only projects. You cannot edit them anymore. Nobody can. It does serve a purpose. It reflects the exact state when those projects were abandoned and therefore are a point of reference. In addition I see little point in moving a bug from one project to the next as they are close to never applicable. If you do happen to find one then please file a new QTBUG task and link to the task in the closed project. -- Alex ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5.3 Feature freeze is coming quite soon...
On 17 January 2014 19:49, Kurt Pattyn pattyn.k...@gmail.com wrote: So, based on the feedback, can everybody agree on QtWebSockets being an add-on? It keeps the core as is, and provides an opt-in for applications that need it. +1 from me. I think it's a good addition to the framework. Rich. Cheers, Kurt On 17 Jan 2014, at 12:25, Richard Moore richmoor...@gmail.com wrote: On 17 January 2014 07:54, Knoll Lars lars.kn...@digia.com wrote: From a feature point of view it would fit best into Qt Network. But it's a sizeable piece of code added to Qt Network. Do you have any numbers on how this changes the size of Qt Network? Peter and Rich, and comments from your side? Given that the websocket code contains both C++ networking stuff and also QML it cannot all go into qt network as this would introduce a circular dependency on the qtdeclarative module. This would mean splitting it into two one part in qt network and another in qt declarative which I think would be a bit confusing for users. On the other hand as an addon module the dependency problem is gone and it can be available as a single self-contained module (with unified documentation) which I suspect would be easier on those using the module. I don't think adding QT += websockets to the pro file would be a barrier for adoption. Given the above (and ignoring the issue of code-size etc.) my initial feeling is that an addon module is probably a better choice for users of the module. Cheers Rich. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtWebSockets as add-on: current voting status
On Mon, Jan 20, 2014 at 01:15:46PM +0100, Kurt Pattyn wrote: The majority seems to agree that this should NOT go into the QtNetwork module, but should be an add-on. the repository was now moved to qt/qtwebsockets. - you need to adjust your git remotes (just edit .git/config) - when you deem it to be in a reasonable state, you need to integrate the repo into qt5.git ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtMultimedia and GStreamer 1.0
On Jan 22, 2014, at 10:07 AM, Tomasz Olszak wrote: Hi. Is gstreamer 1.0 integration planned for 5.3? Ongoing porting effort is happening in the 'wip/gstreamer-1.0' branch. It most likely won't make it into Qt before 5.4. Yoann Lopes Senior Software Engineer - Digia, Qt Visit us on: http://qt.digia.com ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtWebSockets as add-on: current voting status
Great, thanks for the effort. /Kurt On 22 Jan 2014, at 11:13, Oswald Buddenhagen oswald.buddenha...@digia.com wrote: On Mon, Jan 20, 2014 at 01:15:46PM +0100, Kurt Pattyn wrote: The majority seems to agree that this should NOT go into the QtNetwork module, but should be an add-on. the repository was now moved to qt/qtwebsockets. - you need to adjust your git remotes (just edit .git/config) - when you deem it to be in a reasonable state, you need to integrate the repo into qt5.git ___ 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] QtMultimedia and GStreamer 1.0
Ongoing porting effort is happening in the 'wip/gstreamer-1.0' branch. It most likely won't make it into Qt before 5.4. I noticed that there was no activity in this branch since end of October. Is there any TODO list... what need to be done to merge it with dev? -- regards, Tomasz Olszak ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtMultimedia and GStreamer 1.0
On Jan 22, 2014, at 3:32 PM, Tomasz Olszak wrote: I noticed that there was no activity in this branch since end of October. Is there any TODO list... what need to be done to merge it with dev? Indeed there hasn't been any activity. It currently contains what was started by Ilay and Jim. I haven't had the time to look at what exactly is done and what is not. At least a TODO file should be added to that branch in order to see what's missing (and in case anyone wants to contribute). It also has to be extensively tested before being merged to dev. -- Yoann ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] How to write a ChangeLog entry
Mandag 20. januar 2014 12.59.49 skrev Thiago Macieira: On segunda-feira, 20 de janeiro de 2014 12:39:04, Thiago Macieira wrote: Accessibility - - On Linux action names were returned as empty strings in AT-SPI getActions, now returns the proper names. Should I move this to QtGui? Or to QtWidgets? Or leave? In this case it is part of QtGui. I don't mind gui or leaving it separate. Since it's only one entry maybe gui is the better place. -- Best regards, Frederik Gladhorn Senior Software Engineer - Digia, Qt Visit us on: http://qt.digia.com ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] How to write a ChangeLog entry
On quarta-feira, 22 de janeiro de 2014 09:26:57, Blasche Alexander wrote: It's the first time that I had to provide a changes file for my modules. Obviously I was a bit too ambitious ;) but yes: qt.gitorious.org/qt/qtconnectivity/blobs/release/dist/changes-5.2.1 Thanks Alex I'll split the changelog today. Looks like I've captured the changes that people talked about so far. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [QtSerialPort] Add some set of base auto tests
As mentioned on Gerrit before, I was discussing it with Simo, but the problem is really that we neither had anything integrated, nor instructions how to set it up... Those are necessary to get done before requesting any further steps on the CI side. The short instruction how to setup and configure the com0com software is here: https://codereview.qt-project.org/#change,65431 For this purpose it is enough to have a host with any Windows x32. Windows x64 doesn't suit for this purpose because com0com is delivered with unsigned drivers which won't work there. As a result, the principal thing is the configuring of the CI hosts (setup an ENV variables of QTEST_SERIALPORT_SENDER, QTEST_SERIALPORT_RECEIVER, and etc.). I don't know how to do it on CI, so an help (and some work) from the Digia is necessary, IMHO. Thiago, Oswald, Digia, Others, what do you think about it? IMHO, it is impossible to delays with this issue more (1~2 years it is too long)... If you agree with passes of names of serial ports to tests through ENV, then we can start of implementation a set of the minimal tests (even if CI is yet ready). Can you comment it? Best regards, Denis 16.01.2014 13:26, Laszlo Papp пишет: It had been discussed on this list about 1-2 years ago (if memory serves well), and the common consensus was to use com0com on Windows and some VT alike option on Linux. I do not think the technology changed much, so it is probably still the best option... In my opinion though, the best and easiest option would be socat on Linux. That can elegantly create pseudo terminals for this purpose. I was writing some unit tests last year targeting the replacement of socat internally, but it turned out a bit complex, so I lost motivation. In theory, it would be possible to use an internal socat functionality without requiring external dependencies, so the init and tear down would take over the responsibility for this, but it is not that urgent. It is probably not an issue on Linux to setup socat, but I will leave that the decision with the CI contributors. As mentioned on Gerrit before, I was discussing it with Simo, but the problem is really that we neither had anything integrated, nor instructions how to set it up... Those are necessary to get done before requesting any further steps on the CI side. In the long future, my opinion is to get QtMock up to the speed, preferably using the llvm C++ parser (which was not option back then when I thought abut it), and then we could remove all this workaround with a cross-platform solution which is not only useful for QtSerialPort. On Tue, Jan 14, 2014 at 8:14 AM, Denis Shienkov denis.shien...@gmail.com wrote: Hi developers. I want to bring up a question of possibility of addition of some base tests for QtSerialPort. I understand that it is a complex challenge because for this purpose is desirable existence of at least two serial ports of devices which are connected by a Null-modem cable. But this problem can be bypassed by use of virtual devices which are provided with the software of some vendors, e.g.: * on Windows: - eltima virtual serial port driver: http://www.eltima.com/products/vspdxp/ - hdd free virtual serial ports: http://www.hhdsoftware.com/free-virtual-serial-ports - com0com null modem emulator: http://sourceforge.net/projects/com0com/ and others * on Linux: - tibbo virtual serial port driver: http://tibbo.com/downloads/soi/vspdl.html So, for a covering of the minimum basic tests I would choose com0com the project (because free) for windows and tibbo the project (but I yet didn't use it never) for linux. In this case on CI it is enough to install this software and to configure it. The main feature of tests for QtSerialPort is need of explicit specifying of names of serial ports for their use. So, our team had an idea to pass these names (two names at least) to tests through ENV. Please see an main ideas example with the tests here: https://codereview.qt-project.org/#change,65431 At present behavior of tests such that in case of absence in ENV of the QTEST_SERIALPORT_SENDER and the QTEST_SERIALPORT_RECEIVER variables any tests will be skipped/ignored. Otherwise each test will take necessary device name from the necessary variable and to be executed. It allows to use these tests and to developers (for example for me) to make additional tests that cover the CI tests. Because I can setup as the real physical serial devices and as other software of the virtual serial devices (for example from Eltima and so forth), i.e. I have an more flexibility. Also it will be useful for other users who have other types of serial ports. They can execute these tests with the specific types of devices that have. Also it will be useful to have these tests available even if on CI them still isn't present because it will give the chance for the end users (or for developers) to test changes by means of the
Re: [Development] How long until clang memory model is ready?
There are many people out there that want to use Qt Creator not just for Qt
applications but also for general c++ cross platform development as well.When
you look at the options available in this area there are only a few with the
features set that Qt Creator has. Eclipse comes to mind.
Qt Creator could be, with a few fixed bugs the obvious #1 choice ( if it isn't
already ) for general cross platform c++ but it seems like the devs ignore non
Qt c++ development.
Which is a shame since people who use Qt Creator for general c++, but haven't
coded Qt before would be more likely to pick Qt once they start shopping for a
library. The more people using Qt Creator, the better for Qt.
I brought up the clang memory model because discussions on the irc channels and
old blog entries indicate that there was a plan to use clangs memory model to
support the stl's classes in Qt Creator ( unique_ptr, vector, ect... ), once
clang's memory model was working correctly, and my question is about when to
expect this to happen if ever?
From: development-requ...@qt-project.org
Subject: Development Digest, Vol 28, Issue 82
To: development@qt-project.org
Date: Wed, 22 Jan 2014 09:03:01 +0100
Send Development mailing list submissions to
development@qt-project.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.qt-project.org/mailman/listinfo/development
or, via email, send a message with subject or body 'help' to
development-requ...@qt-project.org
You can reach the person managing the list at
development-ow...@qt-project.org
When replying, please edit your Subject line so it is more specific
than Re: Contents of Development digest...
Today's Topics:
1. Re: How long until clang memory model is ready? (Thiago Macieira)
2. QML Image aliasing when animating (Joshua Kolden)
3. Re: QML Image aliasing when animating (Rutledge Shawn)
4. Re: QML Image aliasing when animating (Joshua Kolden)
5. Re: QML Image aliasing when animating (Gunnar Sletta)
6. Re: Remove OSX 10.6 Build? (Ziller Eike)
7. Re: Remove OSX 10.6 Build? (Ziller Eike)
8. Re: Remove OSX 10.6 Build? (Ziller Eike)
--
Message: 1
Date: Tue, 21 Jan 2014 16:03:21 -0800
From: Thiago Macieira thiago.macie...@intel.com
Subject: Re: [Development] How long until clang memory model is ready?
To: development@qt-project.org
Message-ID: 18596554.AqrLlMcojV@tjmaciei-mobl2
Content-Type: text/plain; charset=iso-8859-1
On ter?a-feira, 21 de janeiro de 2014 17:39:07, Chris L wrote:
With clang getting complete draft c++14 support, is the memory model
sufficient to move to using it by default? Things like unique_ptr and
vector really need this.
What do you mean? We've been officially depending on the C++11 memory model
since sometime in Qt 3. The C++98 memory model is incompatible with threads,
we were out of it. There was quite a bit of work to fix some of the issues
during the Qt 5.0 timeframe.
Also, we can't use std::unique_ptr until much later. The Standard Library
support is much sketchier than the language support from the compiler. I also
don't see a need to use std::unique_ptr at all in Qt code and we don't use
std::vector either.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
Url :
http://lists.qt-project.org/pipermail/development/attachments/20140121/0ee54eb6/attachment-0001.bin
--
Message: 2
Date: Tue, 21 Jan 2014 19:03:18 -0800
From: Joshua Kolden jos...@crackcreative.com
Subject: [Development] QML Image aliasing when animating
To: development@qt-project.org
Message-ID: 57ae9a3a-d962-455f-a41f-cacd8056f...@crackcreative.com
Content-Type: text/plain; charset=windows-1252
I?m getting boxed in with rendering bugs on two fronts. Originally I tried
to work with fonts for the following animation, but have both render quality
and font ?subfamily? selection bugs to deal with there. So I took the effort
to switch a lot of stuff around and use images instead, however I?m getting
aliasing artifacts now. I?m rather stuck at the moment for rendering a good
quality large font design.
This video shows the aliasing I?m talking about. There are 3 images here one
is 2048x512 and two are 512x512 for the Camera4 and C4 text logos. The movie
is captured pixel for pixel, and the images at their largest (in this
example) are smaller then the source resolution.
http://c4.dev.s3.amazonaws.com/QMLImageRenderQuality.mov
Here is an example of one of the Image invocations:
Image {
id: c4CameraImage
fillMode: Image.PreserveAspectFit
Re: [Development] QtQuick: Drag pixmap
On Wed, Jan 22, 2014 at 12:11 AM, Fabien Castan fabcas...@gmail.com wrote: Hi, Qt 5.2 adds the possibility to use dragdrop from/to external applications. To allows to drag an item from QML to an external application, we can't simply set a target item, because we want to see this item ouside of the qml window. In Qt, we could set a pixmap on drag events: http://qt-project.org/doc/qt-4.8/qdrag.html#setPixmap I don't see something like that in QtQuick (Qt 5.2): http://qt-project.org/doc/qt-5/qml-qtquick-drag.html Is there a solution to do such thing in pure QML? Regards, Fabien While browsing through the code (qquickdrag.cpp) i found these two commented lines: // TODO: how to handle drag image? // drag-setPixmap(iconPixmap); Along with that no more function for setPixmap that is exposed to QML. That makes me fear that the setPixmap property is not there anymore. Odd, since it would be an API break which i can't really imagine from Qt. I hope someone else more knowledgeable in this area can chime in? ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] How long until clang memory model is ready?
On quarta-feira, 22 de janeiro de 2014 19:35:42, Olivier Goffart wrote: Hi Chris, You mean code model not memory model. And you meant to post to the qt-crea...@qt-project.org mailing list. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] How long until clang memory model is ready?
On 22.01.2014 19:35, ext Olivier Goffart wrote: Regarding the use of libclang for the code model in Qt creator, there was no progress in a long time. I think the clang code model branch has been merged into master: http://lists.qt-project.org/pipermail/qt-creator/2013-December/003028.html The next version of Qt Creator should have the clang code model as a plugin. Cheers, Cristian. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [QtSerialPort] Add some set of base auto tests
On Wednesday 22. January 2014 22.06.03 Denis Shienkov wrote: As mentioned on Gerrit before, I was discussing it with Simo, but the problem is really that we neither had anything integrated, nor instructions how to set it up... Those are necessary to get done before requesting any further steps on the CI side. The short instruction how to setup and configure the com0com software is here: https://codereview.qt-project.org/#change,65431 For this purpose it is enough to have a host with any Windows x32. Windows x64 doesn't suit for this purpose because com0com is delivered with unsigned drivers which won't work there. As a result, the principal thing is the configuring of the CI hosts (setup an ENV variables of QTEST_SERIALPORT_SENDER, QTEST_SERIALPORT_RECEIVER, and etc.). I don't know how to do it on CI, so an help (and some work) from the Digia is necessary, IMHO. Thiago, Oswald, Digia, Others, what do you think about it? IMHO, it is impossible to delays with this issue more (1~2 years it is too long)... If you agree with passes of names of serial ports to tests through ENV, then we can start of implementation a set of the minimal tests (even if CI is yet ready). Can you comment it? I think writing tests is a great idea in any case, so please go ahead. To get the CI to run the tests we should track this in jira, please file an issue on the Qt bug tracker under Qt Quality Assurance Infrastructure. As for how to pass the names of the serial ports, it would be best for Tony and Simo to comment. I would recommend you write a few tests (I see there is currently not much relevant stuff in tests/auto) as if you had the virtual serial ports installed. Make sure the tests are skipped for platforms where these are not available. You can then discuss in the jira task about how to solve the installation and naming of the serial ports. I'm sure Tony and Simo will set up the needed infrastructure for you (with your help). Greetings, Frederik Best regards, Denis 16.01.2014 13:26, Laszlo Papp пишет: It had been discussed on this list about 1-2 years ago (if memory serves well), and the common consensus was to use com0com on Windows and some VT alike option on Linux. I do not think the technology changed much, so it is probably still the best option... In my opinion though, the best and easiest option would be socat on Linux. That can elegantly create pseudo terminals for this purpose. I was writing some unit tests last year targeting the replacement of socat internally, but it turned out a bit complex, so I lost motivation. In theory, it would be possible to use an internal socat functionality without requiring external dependencies, so the init and tear down would take over the responsibility for this, but it is not that urgent. It is probably not an issue on Linux to setup socat, but I will leave that the decision with the CI contributors. As mentioned on Gerrit before, I was discussing it with Simo, but the problem is really that we neither had anything integrated, nor instructions how to set it up... Those are necessary to get done before requesting any further steps on the CI side. In the long future, my opinion is to get QtMock up to the speed, preferably using the llvm C++ parser (which was not option back then when I thought abut it), and then we could remove all this workaround with a cross-platform solution which is not only useful for QtSerialPort. On Tue, Jan 14, 2014 at 8:14 AM, Denis Shienkov denis.shien...@gmail.com wrote: Hi developers. I want to bring up a question of possibility of addition of some base tests for QtSerialPort. I understand that it is a complex challenge because for this purpose is desirable existence of at least two serial ports of devices which are connected by a Null-modem cable. But this problem can be bypassed by use of virtual devices which are provided with the software of some vendors, e.g.: * on Windows: - eltima virtual serial port driver: http://www.eltima.com/products/vspdxp/ - hdd free virtual serial ports: http://www.hhdsoftware.com/free-virtual-serial-ports - com0com null modem emulator: http://sourceforge.net/projects/com0com/ and others * on Linux: - tibbo virtual serial port driver: http://tibbo.com/downloads/soi/vspdl.html So, for a covering of the minimum basic tests I would choose com0com the project (because free) for windows and tibbo the project (but I yet didn't use it never) for linux. In this case on CI it is enough to install this software and to configure it. The main feature of tests for QtSerialPort is need of explicit specifying of names of serial ports for their use. So, our team had an idea to pass these names (two names at least) to tests through ENV. Please see an main ideas example with the tests here:
[Development] Status of Qt3D?
Qt3D looks appetizing for my next project, but I'm not having much luck with finding out what's going on. So I thought I'd ask. Following instruction on http://qt-project.org/wiki/Qt3D-Installation (for Windows/MinGW) gives you a Qt3D that builds OK but doesn't even run it's own tutorial examples. All other info from the forum relates to older versions. This list has no real mentions of Qt3D for the last months. The dedicated Qt3D list seems to have fallen off the net. (It was hosted at Nokia) The official repo at https://qt.gitorious.org/qt/qt3d has very little activity the last months. Hopefully I'm wrong, but the project looks rather dead from this point of view??? ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Proposing Valerio Valerio (VDVsx) for Approver rights to messagingframework
Hello, I'd like to propose Approver rights for Valerio on messaging framework. Justification: Valerio has worked on ( with) QMF for a long time, on both the Nokia N9 and now with us at Jolla on QMF-on-Sailfish. QMF also doesn't exactly have an abundance of approvers, so especially now that I'm doing some work at the moment, having an 'extra pair of hands' able to review would be handy. Dashboard link: https://codereview.qt-project.org/#dashboard,1001065 (+ the git history for his time before the Gerrit import) Fulll disclosure: I work with Valerio at Jolla. BR, Robin ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Proposing Valerio Valerio (VDVsx) for Approver rights to messagingframework
On quarta-feira, 22 de janeiro de 2014 22:50:49, Robin Burchell wrote: Hello, I'd like to propose Approver rights for Valerio on messaging framework. Justification: Valerio has worked on ( with) QMF for a long time, on both the Nokia N9 and now with us at Jolla on QMF-on-Sailfish. QMF also doesn't exactly have an abundance of approvers, so especially now that I'm doing some work at the moment, having an 'extra pair of hands' able to review would be handy. Dashboard link: https://codereview.qt-project.org/#dashboard,1001065 (+ the git history for his time before the Gerrit import) +1 on that. The question is whether he should be given approver rights throughout or just in QMF, considering he hasn't done any Qt contribution outside of QMF. However, knowing Valerio from the past, I would be ok with giving him approver rights throughout. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QML Image aliasing when animating
Upon further experimentation I find that turning layer.mipmap on and off, has
no effect. While smooth on a layer vs. smooth on the image does effect the
image differently. This makes sense if one is being filtered against the
original image size and the other against the Item’s layer texture size. We
should have a mipmap option on images themselves not just an Item layer since
layer size != image size. It appears to me mipmaping is not working at all and
I’d hesitate to go to any trouble with QSGTexture as that may be where it’s
broken if thats the base for Image.
Enabling bilinear filtering without enabling mipmaping is not an intuitive
choice. In effect it means images can only be displayed properly at their
original size or larger then their original size. I would not consider this
expected behavior. You do not have this problem in web page rendering for
example. Given the wide verity of devices and resolutions QML is targeted for
I would expect mipmaping to be default behavior, as well as exposing the filter
setting or simply hardcoding `anisotropic` when smooth is enabled..
I just tested and indeed, it appears that even static images are not being
rendered properly when they are displayed at a resolution lower then their
original resolution, and
layer.enabled: true
layer.smooth: true
layer.mipmap: true
has no effect on images that are displayed larger their there original
resolution.
Thanks,
j
On Jan 22, 2014, at 12:04 AM, Joshua Kolden jos...@crackcreative.com wrote:
Interesting. I tried the layer.mipmap previously with no effect, I did’t
catch that one needed to “enable” it too. However, I just tried this, and
although it created a different, marginally smoother result is is still very
noticeably aliasing.
Here is a move of that test:
http://c4.dev.s3.amazonaws.com/QMLImageRenderQuality2.mov
In fact this version is starting to look very similar to the results I was
seeing with the font renders.
On Jan 21, 2014, at 11:50 PM, Gunnar Sletta gunnar.sle...@jolla.com wrote:
This is the expceted result. smooth: true uses bilinear filtering which is
what is supported in hardware. When scaling down, this starts to degrade.
The effect is drastic for high-contrast content like the edges of a font.
Once go get below 0.5x scale factor the sampling starts to ignore pixels and
aliasing become very visible.
The preferred solution is to prepare raster content (images in your case)
close to the size you intend to show them. If you must scale them down, then
use mipmapping. With the image element, you can get this by doing:
Image {
layer.enabled: true
layer.smooth: true
layer.mipmap: true
...
}
However, by enabling the layer you get an extra texture copy of your rather
large image, so it might be preferable to implement a custom QQuickItem
which returns a QSGSimpleTextureNode with a QSGTexture with mipmapping.
cheers,
Gunnar
On 22 Jan 2014, at 04:03, Joshua Kolden jos...@crackcreative.com wrote:
I’m getting boxed in with rendering bugs on two fronts. Originally I tried
to work with fonts for the following animation, but have both render
quality and font ‘subfamily’ selection bugs to deal with there. So I took
the effort to switch a lot of stuff around and use images instead, however
I’m getting aliasing artifacts now. I’m rather stuck at the moment for
rendering a good quality large font design.
This video shows the aliasing I’m talking about. There are 3 images here
one is 2048x512 and two are 512x512 for the Camera4 and C4 text logos. The
movie is captured pixel for pixel, and the images at their largest (in this
example) are smaller then the source resolution.
http://c4.dev.s3.amazonaws.com/QMLImageRenderQuality.mov
Here is an example of one of the Image invocations:
Image {
id: c4CameraImage
fillMode: Image.PreserveAspectFit
source: “path/to/c4camera.png
anchors.left: parent.left
anchors.top: parent.top
anchors.bottom: parent.bottom
smooth : true
opacity: 0.0
}
The animation is created with a number animation on the width and height of
the parent rectangles.
I’ve asked on IRC, and in the [interest] list, but one said it should just
work and the other didn’t reply.
Is this a known issue, a bug, or and I’m I doing it wrong?
Thanks,
j
___
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] QML Image aliasing when animating
On 23 Jan 2014, at 03:49, Joshua Kolden jos...@crackcreative.com wrote:
Upon further experimentation I find that turning layer.mipmap on and off, has
no effect. While smooth on a layer vs. smooth on the image does effect the
image differently.
This is strange. I see a big difference here when I scale down an image, and I
get the expected visual results as well when I enable layer, smooth and
mipmapping. Both with 5.1.1, 5.2.0 and the upcoming 5.2.1 branch.
This makes sense if one is being filtered against the original image size
and the other against the Item’s layer texture size. We should have a mipmap
option on images themselves not just an Item layer since layer size != image
size. It appears to me mipmaping is not working at all and I’d hesitate to
go to any trouble with QSGTexture as that may be where it’s broken if thats
the base for Image
Adding mipmapping to Image is certainly an option. We've talked about that in
the past, but it just hasn't been done :)
Enabling bilinear filtering without enabling mipmaping is not an intuitive
choice. In effect it means images can only be displayed properly at their
original size or larger then their original size. I would not consider this
expected behavior. You do not have this problem in web page rendering for
example. Given the wide verity of devices and resolutions QML is targeted
for I would expect mipmaping to be default behavior, as well as exposing the
filter setting or simply hardcoding `anisotropic` when smooth is enabled..
I just tested and indeed, it appears that even static images are not being
rendered properly when they are displayed at a resolution lower then their
original resolution, and
layer.enabled: true
layer.smooth: true
layer.mipmap: true
has no effect on images that are displayed larger their there original
resolution.
Nor should it. Smooth makes a difference when scaling up, but not mipmapping.
Thanks,
j
On Jan 22, 2014, at 12:04 AM, Joshua Kolden jos...@crackcreative.com wrote:
Interesting. I tried the layer.mipmap previously with no effect, I did’t
catch that one needed to “enable” it too. However, I just tried this, and
although it created a different, marginally smoother result is is still very
noticeably aliasing.
Here is a move of that test:
http://c4.dev.s3.amazonaws.com/QMLImageRenderQuality2.mov
In fact this version is starting to look very similar to the results I was
seeing with the font renders.
On Jan 21, 2014, at 11:50 PM, Gunnar Sletta gunnar.sle...@jolla.com wrote:
This is the expceted result. smooth: true uses bilinear filtering which is
what is supported in hardware. When scaling down, this starts to degrade.
The effect is drastic for high-contrast content like the edges of a font.
Once go get below 0.5x scale factor the sampling starts to ignore pixels
and aliasing become very visible.
The preferred solution is to prepare raster content (images in your case)
close to the size you intend to show them. If you must scale them down,
then use mipmapping. With the image element, you can get this by doing:
Image {
layer.enabled: true
layer.smooth: true
layer.mipmap: true
...
}
However, by enabling the layer you get an extra texture copy of your rather
large image, so it might be preferable to implement a custom QQuickItem
which returns a QSGSimpleTextureNode with a QSGTexture with mipmapping.
cheers,
Gunnar
On 22 Jan 2014, at 04:03, Joshua Kolden jos...@crackcreative.com wrote:
I’m getting boxed in with rendering bugs on two fronts. Originally I
tried to work with fonts for the following animation, but have both render
quality and font ‘subfamily’ selection bugs to deal with there. So I took
the effort to switch a lot of stuff around and use images instead, however
I’m getting aliasing artifacts now. I’m rather stuck at the moment for
rendering a good quality large font design.
This video shows the aliasing I’m talking about. There are 3 images here
one is 2048x512 and two are 512x512 for the Camera4 and C4 text logos.
The movie is captured pixel for pixel, and the images at their largest (in
this example) are smaller then the source resolution.
http://c4.dev.s3.amazonaws.com/QMLImageRenderQuality.mov
Here is an example of one of the Image invocations:
Image {
id: c4CameraImage
fillMode: Image.PreserveAspectFit
source: “path/to/c4camera.png
anchors.left: parent.left
anchors.top: parent.top
anchors.bottom: parent.bottom
smooth : true
opacity: 0.0
}
The animation is created with a number animation on the width and height
of the parent rectangles.
I’ve asked on IRC, and in the [interest] list, but one said it should just
work and the other didn’t reply.
Is this a known issue, a bug, or and I’m I doing it wrong?
Thanks,
j
___
Development mailing list
Re: [Development] [QtSerialPort] Add some set of base auto tests
-Original Message- From: Gladhorn Frederik Sent: 22. tammikuuta 2014 22:19 To: Denis Shienkov; development@qt-project.org Cc: Sarajärvi Tony; Fält Simo Subject: RE: [Development] [QtSerialPort] Add some set of base auto tests On Wednesday 22. January 2014 22.06.03 Denis Shienkov wrote: As mentioned on Gerrit before, I was discussing it with Simo, but the problem is really that we neither had anything integrated, nor instructions how to set it up... Those are necessary to get done before requesting any further steps on the CI side. The short instruction how to setup and configure the com0com software is here: https://codereview.qt-project.org/#change,65431 For this purpose it is enough to have a host with any Windows x32. Windows x64 doesn't suit for this purpose because com0com is delivered with unsigned drivers which won't work there. As a result, the principal thing is the configuring of the CI hosts (setup an ENV variables of QTEST_SERIALPORT_SENDER, QTEST_SERIALPORT_RECEIVER, and etc.). I don't know how to do it on CI, so an help (and some work) from the Digia is necessary, IMHO. Thiago, Oswald, Digia, Others, what do you think about it? IMHO, it is impossible to delays with this issue more (1~2 years it is too long)... If you agree with passes of names of serial ports to tests through ENV, then we can start of implementation a set of the minimal tests (even if CI is yet ready). Can you comment it? I think writing tests is a great idea in any case, so please go ahead. To get the CI to run the tests we should track this in jira, please file an issue on the Qt bug tracker under Qt Quality Assurance Infrastructure. You can use this https://bugreports.qt-project.org/browse/QTQAINFRA-682 As for how to pass the names of the serial ports, it would be best for Tony and Simo to comment. I would recommend you write a few tests (I see there is currently not much relevant stuff in tests/auto) as if you had the virtual serial ports installed. This would help so that we can verify that the setup works. Configuring the tests trough ENV variables is quite easy in CI, it is just yet another parameter in submodule's testconfig. All we need to know are the proper values to export. Simo Make sure the tests are skipped for platforms where these are not available. You can then discuss in the jira task about how to solve the installation and naming of the serial ports. I'm sure Tony and Simo will set up the needed infrastructure for you (with your help). Greetings, Frederik Best regards, Denis 16.01.2014 13:26, Laszlo Papp пишет: It had been discussed on this list about 1-2 years ago (if memory serves well), and the common consensus was to use com0com on Windows and some VT alike option on Linux. I do not think the technology changed much, so it is probably still the best option... In my opinion though, the best and easiest option would be socat on Linux. That can elegantly create pseudo terminals for this purpose. I was writing some unit tests last year targeting the replacement of socat internally, but it turned out a bit complex, so I lost motivation. In theory, it would be possible to use an internal socat functionality without requiring external dependencies, so the init and tear down would take over the responsibility for this, but it is not that urgent. It is probably not an issue on Linux to setup socat, but I will leave that the decision with the CI contributors. As mentioned on Gerrit before, I was discussing it with Simo, but the problem is really that we neither had anything integrated, nor instructions how to set it up... Those are necessary to get done before requesting any further steps on the CI side. In the long future, my opinion is to get QtMock up to the speed, preferably using the llvm C++ parser (which was not option back then when I thought abut it), and then we could remove all this workaround with a cross-platform solution which is not only useful for QtSerialPort. On Tue, Jan 14, 2014 at 8:14 AM, Denis Shienkov denis.shien...@gmail.com wrote: Hi developers. I want to bring up a question of possibility of addition of some base tests for QtSerialPort. I understand that it is a complex challenge because for this purpose is desirable existence of at least two serial ports of devices which are connected by a Null-modem cable. But this problem can be bypassed by use of virtual devices which are provided with the software of some vendors, e.g.: * on Windows: - eltima virtual serial port driver: http://www.eltima.com/products/vspdxp/ - hdd free virtual serial ports: http://www.hhdsoftware.com/free-virtual-serial-ports - com0com null modem emulator: http://sourceforge.net/projects/com0com/ and others * on Linux: -
Re: [Development] Proposing Valerio Valerio (VDVsx) for Approver rights to messagingframework
On 23/01/14 00:32, Thiago Macieira thiago.macie...@intel.com wrote: On quarta-feira, 22 de janeiro de 2014 22:50:49, Robin Burchell wrote: Hello, I'd like to propose Approver rights for Valerio on messaging framework. Justification: Valerio has worked on ( with) QMF for a long time, on both the Nokia N9 and now with us at Jolla on QMF-on-Sailfish. QMF also doesn't exactly have an abundance of approvers, so especially now that I'm doing some work at the moment, having an 'extra pair of hands' able to review would be handy. Dashboard link: https://codereview.qt-project.org/#dashboard,1001065 (+ the git history for his time before the Gerrit import) +1 on that. The question is whether he should be given approver rights throughout or just in QMF, considering he hasn't done any Qt contribution outside of QMF. However, knowing Valerio from the past, I would be ok with giving him approver rights throughout. +1 (including the last sentence). Cheers, Lars ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Proposing Valerio Valerio (VDVsx) for Approver rights to messagingframework
On quinta-feira, 23 de janeiro de 2014 07:37:14, Knoll Lars wrote: On 23/01/14 00:32, Thiago Macieira thiago.macie...@intel.com wrote: However, knowing Valerio from the past, I would be ok with giving him approver rights throughout. +1 (including the last sentence). Ok, so Valerio is now on the regular 3-week period for approvership. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] How long until clang memory model is ready?
On Jan 22, 2014, at 8:31 PM, Cristian Adam cristian.a...@here.com wrote: On 22.01.2014 19:35, ext Olivier Goffart wrote: Regarding the use of libclang for the code model in Qt creator, there was no progress in a long time. I think the clang code model branch has been merged into master: http://lists.qt-project.org/pipermail/qt-creator/2013-December/003028.html The next version of Qt Creator should have the clang code model as a plugin. That’s correct. In Qt Creator master branch (i.e. 3.1 series) you can choose the code model of different languages to use clang as a code model backend, or Qt Creator’s built-in. (If you pointed Qt Creator to libclang (and dev headers) at Qt Creator compile time.) Br, Eike -- Eike Ziller, Senior Software Engineer - Digia, Qt Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [QtSerialPort] Add some set of base auto tests
Hi Simo, Guys. Many thanks for your involvement. You can use this https://bugreports.qt-project.org/browse/QTQAINFRA-682 I added there some instruction for com0com installation. So, what additional info still it is necessary for you? Best regards, Denis 2014/1/23 Fält Simo simo.f...@digia.com -Original Message- From: Gladhorn Frederik Sent: 22. tammikuuta 2014 22:19 To: Denis Shienkov; development@qt-project.org Cc: Sarajärvi Tony; Fält Simo Subject: RE: [Development] [QtSerialPort] Add some set of base auto tests On Wednesday 22. January 2014 22.06.03 Denis Shienkov wrote: As mentioned on Gerrit before, I was discussing it with Simo, but the problem is really that we neither had anything integrated, nor instructions how to set it up... Those are necessary to get done before requesting any further steps on the CI side. The short instruction how to setup and configure the com0com software is here: https://codereview.qt-project.org/#change,65431 For this purpose it is enough to have a host with any Windows x32. Windows x64 doesn't suit for this purpose because com0com is delivered with unsigned drivers which won't work there. As a result, the principal thing is the configuring of the CI hosts (setup an ENV variables of QTEST_SERIALPORT_SENDER, QTEST_SERIALPORT_RECEIVER, and etc.). I don't know how to do it on CI, so an help (and some work) from the Digia is necessary, IMHO. Thiago, Oswald, Digia, Others, what do you think about it? IMHO, it is impossible to delays with this issue more (1~2 years it is too long)... If you agree with passes of names of serial ports to tests through ENV, then we can start of implementation a set of the minimal tests (even if CI is yet ready). Can you comment it? I think writing tests is a great idea in any case, so please go ahead. To get the CI to run the tests we should track this in jira, please file an issue on the Qt bug tracker under Qt Quality Assurance Infrastructure. You can use this https://bugreports.qt-project.org/browse/QTQAINFRA-682 As for how to pass the names of the serial ports, it would be best for Tony and Simo to comment. I would recommend you write a few tests (I see there is currently not much relevant stuff in tests/auto) as if you had the virtual serial ports installed. This would help so that we can verify that the setup works. Configuring the tests trough ENV variables is quite easy in CI, it is just yet another parameter in submodule's testconfig. All we need to know are the proper values to export. Simo Make sure the tests are skipped for platforms where these are not available. You can then discuss in the jira task about how to solve the installation and naming of the serial ports. I'm sure Tony and Simo will set up the needed infrastructure for you (with your help). Greetings, Frederik Best regards, Denis 16.01.2014 13:26, Laszlo Papp пишет: It had been discussed on this list about 1-2 years ago (if memory serves well), and the common consensus was to use com0com on Windows and some VT alike option on Linux. I do not think the technology changed much, so it is probably still the best option... In my opinion though, the best and easiest option would be socat on Linux. That can elegantly create pseudo terminals for this purpose. I was writing some unit tests last year targeting the replacement of socat internally, but it turned out a bit complex, so I lost motivation. In theory, it would be possible to use an internal socat functionality without requiring external dependencies, so the init and tear down would take over the responsibility for this, but it is not that urgent. It is probably not an issue on Linux to setup socat, but I will leave that the decision with the CI contributors. As mentioned on Gerrit before, I was discussing it with Simo, but the problem is really that we neither had anything integrated, nor instructions how to set it up... Those are necessary to get done before requesting any further steps on the CI side. In the long future, my opinion is to get QtMock up to the speed, preferably using the llvm C++ parser (which was not option back then when I thought abut it), and then we could remove all this workaround with a cross-platform solution which is not only useful for QtSerialPort. On Tue, Jan 14, 2014 at 8:14 AM, Denis Shienkov denis.shien...@gmail.com wrote: Hi developers. I want to bring up a question of possibility of addition of some base tests for QtSerialPort. I understand that it is a complex challenge because for this purpose is desirable existence of at least two serial ports of devices which are connected by a Null-modem cable. But this problem can be bypassed by
