On segunda-feira, 8 de outubro de 2012 18.15.12, Eric Gregory wrote:
> I noticed from this ticket that MNG support had been dropped from QtBase:
> https://bugreports.qt-project.org/browse/QTBUG-21869
Please read carefully what you said: it's dropped from *qtbase* [1].
It's still available in qtim
On Sun, Oct 7, 2012 at 4:55 PM, André Somers wrote:
> I think that there are probably a lot of useful bits and pieces that
> really need to go into the main docs in the docnotes. Would it be a good
> idea to go over them and see what gems are there?
>
> André
>
That's a great idea! Is there a wa
I noticed from this ticket that MNG support had been dropped from QtBase:
https://bugreports.qt-project.org/browse/QTBUG-21869
Is there a replacement format available (such as APNG)? This feature is
useful for animating while the UI thread is blocked, which is useful for
progress spinners and suc
On 08/10/12 22:58, Simon Hausmann wrote:
> Now this has some ugly implications, everyone will have to change the way they
> develop with Qt 5. In this context we have another interesting artifact:
> People who have been developing Qt for a long time as part of company efforts
> such as Trolltech, N
Hi Richard,
many thanks for the insightful mail.
On 8 October 2012 22:49, Richard Moore wrote:
> = Proposed Security Policy =
>
> == Reporting Security Issues ==
>
> * Security issues should not be reported via the normal
>bugreports.qt-project.org tracker, but should instead be sent to
>
I'm including the text inline since I've had a request for that.
Rich.
= Current State =
== How did we do during the recent CRIME attack? ==
* We provided a fix.
* security at qt-project.org was shown to be non-functional (no reply, no
action).
* We were initially unable to send an ema
I stumbled across an interesting discussion from Feb-2008 about using
QTcpSocket and QLocalSocket, which also suggested the design might be
revisited post Qt5:
http://blog.qt.digia.com/2008/02/22/qlocalserver-qlocalsocket/
REVIEW:
- QTcpSocket (derived from QAbstractSocket) is really a
network-
Over the last few weeks, I've been working on a proposal for a
security policy for the Qt Project. I've drawn on the Django security
policy, my own experience, previous Qt security announcements and
feedback from the initial reviewers. I think we now have something
that is worth having a wider revi
On 08.10.2012 18:07, Thiago Macieira wrote:
> On segunda-feira, 8 de outubro de 2012 16.37.46, Peter Kümmel wrote:
>> Currently on Windows private headers are needed when
>> #include is used.
>>
>> \include\QtGui\QtGui
>> \include\QtGui\QPlatformNativeInterface
>>
>> which needs 5.0.0\qpa\qpla
On segunda-feira, 8 de outubro de 2012 02.36.09, d3fault wrote:
> On Mon, Oct 8, 2012 at 12:39 AM, Thiago Macieira
>
> wrote:
> > Full disclosure *after* we've analysed the bug and delivered a fix, if
> > necessary.
>
> Well I think we should change the policy then. Informing application
> devel
On segunda-feira, 8 de outubro de 2012 16.37.46, Peter Kümmel wrote:
> Currently on Windows private headers are needed when
> #include is used.
>
> \include\QtGui\QtGui
>\include\QtGui\QPlatformNativeInterface
>
> which needs 5.0.0\qpa\qplatformnativeinterface.h
>
> Is this by design?
No.
Pl
On Monday, October 08, 2012 02:31:46 PM shane.kea...@accenture.com wrote:
[...]
> Another thing you need to consider is named versions.
> For example I might have "5.0.0" and "5.0.0-blackberry" co-installed.
> I think Qt Creator handles this just fine, but the "qt --5" examples above
> look like it
Currently on Windows private headers are needed when
#include is used.
\include\QtGui\QtGui
\include\QtGui\QPlatformNativeInterface
which needs 5.0.0\qpa\qplatformnativeinterface.h
Is this by design?
Peter
___
Development mailing list
Development@
> We just had a discussion in the Oslo office about this. We suggest to
> basically follow your proposal, with an addon to hide some of the
> uglyness it brings along.
>
> Let me try to summarize very shortly. The base proposal would be to
> include the major Qt version throughout the project:
>
>
On Mon, Oct 8, 2012 at 2:15 PM, Bache-Wiig Jens
wrote:
> Anyway, a theming question. How can the QML Desktop Components
>
> currently be themed? Only by means of QStyle? Would there be a way to
> use kde's plasma themes in the QML Desktop Components? And do the
> desktop components depend on QWidg
On Oct 1, 2012, at 3:09 PM, Stephen Kelly wrote:
> On Monday, October 01, 2012 12:42:36 you wrote:
>> Hi Stephen,
>>
>> Fully agree with you. However this wasn't in any way by intention.
>
> Hi Lars,
>
> That's great. Thanks for the prompt response and clarification.
>
>> Here's
>> what I be
On Friday, September 21, 2012 05:24:16 PM Thiago Macieira wrote:
> On sexta-feira, 21 de setembro de 2012 16.47.11, Thiago Macieira wrote:
> > Include the major version number (5) in all library base names, like on
> > Windows, on all platforms. On Windows we already have QtCore5.dll and
> > QtV85.
Anyway, a theming question. How can the QML Desktop Components
currently be themed? Only by means of QStyle? Would there be a way to
use kde's plasma themes in the QML Desktop Components? And do the
desktop components depend on QWidgets only because of QStyle.
Yes we have already been researching
> p.s. if I need to suck your d!c|< for access to incoming security
> vulns, this "Open Governance" project isn't really open at all.
If you still ask yourself why you are prohibited from participation
you've just aswered your own question.
If you want to be treated like an responsible adult behav
On 8 October 2012 10:36, d3fault wrote:
>
> p.s. if I need to suck your d!c|< for access to incoming security
> vulns, this "Open Governance" project isn't really open at all.
I'm immediately raising this for moderators action.
This behaviour IMO is not acceptable and cannot be not tolerated.
--
On Mon, Oct 8, 2012 at 10:13 AM, Sorvig Morten wrote:
>
>>-- could you please bottom post, that really improves thread readability :) --
>
> Many of the new @digia folks are currently stuck with the Outlook web app
> wich top-posts by default and does not support quoting. We'll figure it out
> e
On Mon, Oct 8, 2012 at 12:39 AM, Thiago Macieira
wrote:
> Full disclosure *after* we've analysed the bug and delivered a fix, if
> necessary.
>
Well I think we should change the policy then. Informing application
developers that their software might be (or definitely is) at risk is
CRUCIAL in app
Much more instantly-readable, thankyou very much :)
--
Bill King
Test Engineer
Nokia, Guidance Team
From: development-bounces+bill.king=nokia@qt-project.org
[mailto:development-bounces+bill.king=nokia@qt-project.org] On Behalf Of
ext Sébastien Fricker
Sent: Sunday, 7 Octobe
>-- could you please bottom post, that really improves thread readability :) --
Many of the new @digia folks are currently stuck with the Outlook web app wich
top-posts by default and does not support quoting. We'll figure it out
eventually.
Morten
_
On 7 Oct 2012, at 16:21, Majid Khan wrote:
> I have tried compiling Qt creator using VS2010 (qt4.8.1) but I am missing
> .
>
> It works alright in linux (but thats because inclusion is under pre-processor
> directive for Q_OS_WIN. I have seen this has been issue for some other
> people too
On domingo, 7 de outubro de 2012 22.48.08, d3fault wrote:
> On Sun, Oct 7, 2012 at 10:00 PM, Thiago Macieira
>
> wrote:
> > For obvious reasons, the security list is not public and is not open for
> > subscription from other people. If you feel you have a reason to be in the
> > security mailing
Thanks Lincoln, libsupc++.a library is the answer !
-Original Message-
From: development-bounces+song.7.liu=nokia@qt-project.org
[mailto:development-bounces+song.7.liu=nokia@qt-project.org] On Behalf Of
Liu Song.7 (Nokia-MP/Beijing)
Sent: Monday, October 08, 2012 2:16 PM
To: thia
27 matches
Mail list logo
