Re: [Development] wmf backend dxva

good ... the qml angle / dxva will be fine for low end computer :) I hopes it will be the same for gstreamer / Linux backend (libvaapi) for custom : I mean that if I need to reimplement a more custom decoder using dxva, I hopes there will be a public access to directx surface thru angle to allow

Re: [Development] How to release critical fixes?

On Friday 05 October 2012 14:41:10 Rafael Roquetto wrote: > Hi Tuukka, > > Is this listed anywhere, or are you planning to publish this once it is in > place? Is this the same thing Rich is referring to? > > Btw, thanks for the 4.8.4, much appreciated. > > Kind regards, > Rafael I assume he mea

Re: [Development] How to release critical fixes?

Hi Tuukka, Is this listed anywhere, or are you planning to publish this once it is in place? Is this the same thing Rich is referring to? Btw, thanks for the 4.8.4, much appreciated. Kind regards, Rafael On Fri, Oct 05, 2012 at 03:21:09PM +, Turunen Tuukka wrote: > > > The new release pro

Re: [Development] How to release critical fixes?

On sexta-feira, 5 de outubro de 2012 15.13.22, shane.kea...@accenture.com wrote: > Since the major/minor/patch release is encoded into QT_VERSION, critical > releases should increment the patch number. I suggest to use a short lived > branch for just this release. > > e.g. > check out previous pa

Re: [Development] How to release critical fixes?

On 5 October 2012 15:32, Rafael Roquetto wrote: > Hello all, > > Following the discussion concerning 4.8.3-1 vs 4.8.4, I think an important > gap on the workflow has been exposed: how to release critical patches? I am > not sure if this makes sense, since I am entirely not acquitanted to the > ent

Re: [Development] QThread usage/guidance

On Friday 05 October 2012 15:24:40 Tony Van Eerd wrote: > So that is the 'recommended' style then? Depends what you want to do. If your task is CPU bounded, you can use QtConcurrent. If you don't need to event loop, you can reimplement the run() function. I'd use this appreach only if your task m

Re: [Development] QThread usage/guidance

So that is the 'recommended' style then? > -Original Message- > From: Olivier Goffart [mailto:oliv...@woboq.com] > Sent: Friday, October 05, 2012 10:54 AM > To: development@qt-project.org > Cc: Tony Van Eerd > Subject: Re: [Development] QThread usage/guidance > > On Friday 05 October 201

Re: [Development] How to release critical fixes?

The new release process already addresses this. After we have it in place, it will be straightforward. It is ok to discuss, but very much has already been planned and agreed. We just need to take it into use. However the fact that Qt is a cross-platform toolkit still remains an item we need

Re: [Development] How to release critical fixes?

Since the major/minor/patch release is encoded into QT_VERSION, critical releases should increment the patch number. I suggest to use a short lived branch for just this release. e.g. check out previous patch release tag (e.g. v4.8.3) create a branch from it cherry pick the critical fix(es) onto t

Re: [Development] QThread usage/guidance

On Friday 05 October 2012 14:31:51 Tony Van Eerd wrote: > What was the final resolution (if any) of the email thread > "QThread::finished() race → fixing QThread" > http://lists.qt-project.org/pipermail/development/2011-November/000284.html > > > In particular as seen in > http://mayaposch.wordp

[Development] How to release critical fixes?

Hello all, Following the discussion concerning 4.8.3-1 vs 4.8.4, I think an important gap on the workflow has been exposed: how to release critical patches? I am not sure if this makes sense, since I am entirely not acquitanted to the entire release process, but would anyone have any suggestion or

[Development] QThread usage/guidance

What was the final resolution (if any) of the email thread "QThread::finished() race → fixing QThread" http://lists.qt-project.org/pipermail/development/2011-November/000284.html In particular as seen in http://mayaposch.wordpress.com/2011/11/01/how-to-really-truly-use-qthreads-the-full-explan

Re: [Development] Antialiasing

On Fri, October 05, 2012 02:51:09 PM Samuel Rødal wrote: > On 10/05/2012 02:28 PM, Wehmer, Matthias wrote: > > Hi Samuel, > > > > I will try to make myself clearer, sorry for that unclear information. > > > > The shaders I’m talking about are those, that I implemented in my custom > > Qml plugin

Re: [Development] Preparing to release repackaged version of Qt 4.8.3 with Digia copyrights

On sexta-feira, 5 de outubro de 2012 11.43.39, Olivier Goffart wrote: > Just to add some noise: > There was a Qt 3.3.8b (also for copyright change) > So to be consistant, it should be Qt 4.8.3b Qt 3.3.8b was a license change, when Qt was relicensed to include the GPLv3. After that, we had the

Re: [Development] Preparing Qt 4.8.4 release

On Fri, Oct 5, 2012 at 2:17 PM, Taipale Juhani wrote: > -Original Message- >> From: Mark [mailto:mark...@gmail.com] >> Sent: 5. lokakuuta 2012 13:39 >> To: Taipale Juhani >> Cc: releas...@qt-project.org; development@qt-project.org >> Subject: Re: [Development] Preparing Qt 4.8.4 release >

Re: [Development] Antialiasing

On 10/05/2012 02:28 PM, Wehmer, Matthias wrote: > Hi Samuel, > > I will try to make myself clearer, sorry for that unclear information. > > The shaders I’m talking about are those, that I implemented in my custom > Qml plugin via the QSGSimpleMaterial class. There I have implemented two > custom ve

Re: [Development] Preparing to release repackaged version of Qt 4.8.3 with Digia copyrights

On Friday, October 05, 2012 08:11:25 Turunen Tuukka wrote: > On 4.10.2012 17.42, "Rafael Roquetto" wrote: > >On Thu, Oct 04, 2012 at 01:11:19PM +, Turunen Tuukka wrote: > >> My preference is towards releasing now and making proper 4.8.4 (with > >> > >>more > >> > >> content) later. It is true

Re: [Development] New branch in qtdoc for Qt 5.0 documentation brush-up

On Friday, October 05, 2012 09:15:48 Eskil Abrahamsen Blomfeldt wrote: > On 10/04/2012 05:21 PM, Stephen Kelly wrote: > > On Thursday, October 04, 2012 17:06:08 Eskil Abrahamsen Blomfeldt wrote: > >> If > >> you are working on changes to the qtdoc repository, could you please > >> move it over to "

Re: [Development] Antialiasing

Hi Samuel, I will try to make myself clearer, sorry for that unclear information. The shaders I'm talking about are those, that I implemented in my custom Qml plugin via the QSGSimpleMaterial class. There I have implemented two custom versions of the vertex and the fragment shader, whereby the l

Re: [Development] Preparing Qt 4.8.4 release

-Original Message- > From: Mark [mailto:mark...@gmail.com] > Sent: 5. lokakuuta 2012 13:39 > To: Taipale Juhani > Cc: releas...@qt-project.org; development@qt-project.org > Subject: Re: [Development] Preparing Qt 4.8.4 release > Just out of curiosity, can't the 4.8.3 repackaged release b

Re: [Development] Qt desktop components project

On Fri, Oct 5, 2012 at 1:26 PM, Aleix Pol wrote: > On Fri, Oct 5, 2012 at 11:58 AM, Mark wrote: >> On Fri, Oct 5, 2012 at 11:04 AM, Laszlo Papp wrote: >>> Daker was also working on the Plasma Components project under the GSoC >>> umbrella, so I think he is familiar with the topic. :-) I believe

Re: [Development] Antiaaliasing

On 10/05/2012 11:57 AM, Wehmer, Matthias wrote: > Hi everybody, > > I need some information regarding the antialiasing functionality in Qt > 5. I have implemented a custom widget which basically draws a lot of > lines (also uses custom materials). Unfortunately they are not at all > AA. Anyway, via

Re: [Development] Qt desktop components project

On Fri, Oct 5, 2012 at 11:58 AM, Mark wrote: > On Fri, Oct 5, 2012 at 11:04 AM, Laszlo Papp wrote: >> Daker was also working on the Plasma Components project under the GSoC >> umbrella, so I think he is familiar with the topic. :-) I believe this >> is one of your best bets (and similar blog post

Re: [Development] QFontMetrics and QScriptLine height calculation

Yes, backporting QAccessibleTextWidget::characterRect() implementation from 5.0 is seems to be safe. I don't know for sure if this won't break some other tests, though. You'll probably need to discuss this with Eskil Abrahamsen Blomfeldt and/or Jan Arve Sæther first (eskil and jan-arve at IRC, resp

Re: [Development] Preparing Qt 4.8.4 release

On Fri, Oct 5, 2012 at 11:39 AM, Taipale Juhani wrote: > Hello everyone, > > > > It is time to create new Qt 4.8.4 release. We will have over 80 new fixes > there, some of them urgently requested. > > We will freeze the content next week and create first release candidates for > testing. > > If Yo

Re: [Development] QFontMetrics and QScriptLine height calculation

Hi there, Thanks for the prompty reply. I am indeed talking about 4.8. Should I maybe then backport the 5.0 implementation of QAccessibleTextWidget, should this ever be possible or make sense? Or even better, fix the test to use QFontMetrics::lineSpacing()? Any other suggestions? As I said, this

Re: [Development] Qt desktop components project

On Fri, Oct 5, 2012 at 11:04 AM, Laszlo Papp wrote: > Daker was also working on the Plasma Components project under the GSoC > umbrella, so I think he is familiar with the topic. :-) I believe this > is one of your best bets (and similar blog posts there): > > http://codecereal.blogspot.ie/2012/05

[Development] Antiaaliasing

Hi everybody, I need some information regarding the antialiasing functionality in Qt 5. I have implemented a custom widget which basically draws a lot of lines (also uses custom materials). Unfortunately they are not at all AA. Anyway, via setAntialiasing() I turned AA on, but nothing happens.

Re: [Development] Preparing to release repackaged version of Qt 4.8.3 with Digia copyrights

On Friday 05 October 2012 09:14:08 Turunen Tuukka wrote: > The idea was to release as quickly as possible a version with correct > copyrights. And since the MinGW fix has been requested to include that as > well. > > We have a large number of platforms to test in, many more than the CI > systems c

[Development] Preparing Qt 4.8.4 release

Hello everyone, It is time to create new Qt 4.8.4 release. We will have over 80 new fixes there, some of them urgently requested. We will freeze the content next week and create first release candidates for testing. If You are doing development which requires additional commits, please take thi

Re: [Development] Preparing to release repackaged version of Qt 4.8.3 with Digia copyrights

> From: Oleg Shparber mailto:troll...@gmail.com>> > Date: perjantaina 5. lokakuuta 2012 11.57 > To: Tuukka Turunen mailto:tuukka.turu...@digia.com>> > Cc: Rafael Roquetto > mailto:rafael.roque...@kdab.com>>, > "development@qt-project.org" > mailto:development@

Re: [Development] Qt desktop components project

Daker was also working on the Plasma Components project under the GSoC umbrella, so I think he is familiar with the topic. :-) I believe this is one of your best bets (and similar blog posts there): http://codecereal.blogspot.ie/2012/05/qml-themingstyling-update.html Laszlo On Fri, Oct 5, 2012 a

Re: [Development] Preparing to release repackaged version of Qt 4.8.3 with Digia copyrights

Being a 3rd party observer and thoroughly reading all messages by Tuukkla I anyway cannot understand the logic behind having 4.8.3-1 version instead of suggested 4.8.4 with new copyrights, MinGW and SSL fixes. What is wrong with releasing it right now and then process all the new commits since 4.8.

Re: [Development] Preparing to release repackaged version of Qt 4.8.3 with Digia copyrights

On 4.10.2012 17.42, "Rafael Roquetto" wrote: >On Thu, Oct 04, 2012 at 01:11:19PM +, Turunen Tuukka wrote: >> >> >> My preference is towards releasing now and making proper 4.8.4 (with >>more >> content) later. It is true that getting the security fix in is also >> valuable and then we cert

Re: [Development] Qt desktop components project

On Fri, Oct 5, 2012 at 12:42 AM, Bache-Wiig Jens wrote: >>Anyway, what is the plan right now? Don't do anything for the desktop >>components till Qt 5 is released then developing the desktop >>components further till they are perfect and ready to be released with >>Qt 5.1? > > That is a reasonable

Re: [Development] New branch in qtdoc for Qt 5.0 documentation brush-up

On 10/04/2012 05:21 PM, Stephen Kelly wrote: > On Thursday, October 04, 2012 17:06:08 Eskil Abrahamsen Blomfeldt wrote: >> If >> you are working on changes to the qtdoc repository, could you please >> move it over to "newdocs" branch so we can minimize conflicts? > Excuse my circular logic, but if

Re: [Development] wmf backend dxva

Hi, > I have read recently that qt5 will be available thru angle/Directx and > there is work in progress about a wmf backend dxva. when will it be > available in git ? > Will it be possible to have a public access to directx surface to For the next beta we hope to have ANGLE properly integrat