A slightly longer paste:
#ifdef MESA_EGL_NO_X11_HEADERS
typedef void*EGLNativeDisplayType;
typedef khronos_uint32_t EGLNativePixmapType;
typedef khronos_uint32_t EGLNativeWindowType;
#else
/* X11 (tentative) */
#include X11/Xlib.h
#include X11/Xutil.h
typedef Display
Hi,
On 03/25/2013 01:09 AM, Alexander Rössler wrote:
On Sunday 24 March 2013 16:32:38 Thiago Macieira wrote:
But I'm not sure your idea belongs to Qt. You're describing a build
server.
Maybe you should contact one of the cloud organisations. You'll also
need to
explain why your idea
A slightly longer paste:
#ifdef MESA_EGL_NO_X11_HEADERS
typedef void*EGLNativeDisplayType;
typedef khronos_uint32_t EGLNativePixmapType;
typedef khronos_uint32_t EGLNativeWindowType;
#else
/* X11 (tentative) */
#include X11/Xlib.h
#include X11/Xutil.h
typedef Display
On Mar 22, 2013, at 3:21 PM, Jake Thomas Petroules
jake.petrou...@petroules.com wrote:
Not the only way...
There's [NSApplicationDelegate applicationDockMenu:], and dock tile plugins
(we should look into bundling a default dock tile plugin in Qt apps!).
Fixed now (again):
On Mar 23, 2013, at 1:51 AM, Jake Thomas Petroules
jake.petrou...@petroules.com wrote:
I'd like to suggest that we add a new Q_OS_ define.
Currently, for Apple platforms, we have:
Q_OS_DARWIN
Q_OS_DARWIN32
Q_OS_DARWIN64
Q_OS_IOS
Q_OS_MAC
Q_OS_MAC32
Q_OS_MAC64
Q_OS_MACX
The first
Hi,
All merges from dev into stable needed for 5.1 have gone through now.
- qtactiveqt
- qtbase
- qtdeclarative
- qtdoc
- qtgraphicaleffects
- qtimageformats
- qtjsbackend
- qtmultimedia
- qtquick1
- qtquickcontrols
- qtscript
- qtsensors
- qtsvg
- qttools
- qttranslations
- qtwebkit
-
I was able to correctoly configure make make install QT5 for my Tegra2
device.
However, when I try to launch a simple hello world application written in
qml/qtquick2 I got the following error:
root@colibri-t20:~/helloworld-build-tegra2-Debug# ./helloworld
QIconvCodec::convertFromUnicode:
On segunda-feira, 25 de março de 2013 10.46.50, Sergio Ahumada wrote:
Next step is to get qt5.git updated and add qtquickcontrols, qtsensors,
qtserialport and qtx11extras to it.
Shouldn't we do an API review on those before we add them? Or is it ok to drop
them from beta (after alpha) if we
On Mar 25, 2013, at 5:11 AM, Sorvig Morten morten.sor...@digia.com wrote:
On Mar 23, 2013, at 1:51 AM, Jake Thomas Petroules
jake.petrou...@petroules.com wrote:
I'd like to suggest that we add a new Q_OS_ define.
Currently, for Apple platforms, we have:
Q_OS_DARWIN
Q_OS_DARWIN32
Mandag 25. mars 2013 08.30.45 skrev Thiago Macieira:
On segunda-feira, 25 de março de 2013 10.46.50, Sergio Ahumada wrote:
Next step is to get qt5.git updated and add qtquickcontrols, qtsensors,
qtserialport and qtx11extras to it.
Shouldn't we do an API review on those before we add them?
On Mar 25, 2013, at 5:11 AM, Sorvig Morten morten.sor...@digia.com wrote:
On Mar 23, 2013, at 1:51 AM, Jake Thomas Petroules
jake.petrou...@petroules.com wrote:
I'd like to suggest that we add a new Q_OS_ define.
Currently, for Apple platforms, we have:
Q_OS_DARWIN
Q_OS_DARWIN32
On 25 March 2013 15:30, Thiago Macieira thiago.macie...@intel.com wrote:
On segunda-feira, 25 de março de 2013 10.46.50, Sergio Ahumada wrote:
Next step is to get qt5.git updated and add qtquickcontrols, qtsensors,
qtserialport and qtx11extras to it.
Shouldn't we do an API review on those
On Sun, Mar 24, 2013 at 9:57 AM, Thiago Macieira
thiago.macie...@intel.com wrote:
On sexta-feira, 22 de março de 2013 14.57.11, Alan Alpert wrote:
There are a few questions left on the QFileSelectors API addition,
https://codereview.qt-project.org/#change,48334 :
1) Did it miss the feature
On Sat, Mar 23, 2013 at 8:50 PM, Konstantin Ritt ritt...@gmail.com wrote:
Can't it be a private API in 5.1?
That's a good idea. Why didn't I think of that? That also provides
more flexibility while working towards unification.
If it goes in as private API, does it still fall subject to the
qtx11extras and qtserialport didn't need a merge, since they didn't have
dev/stable branches.
We got that sorted out a couple of days ago, but it does not require any
work for the moment as stable got branched off master. Then, we just began
to follow the Qt branching model.
On 25 March 2013
On Monday, March 25, 2013 10:46:37 Alan Alpert wrote:
On Sat, Mar 23, 2013 at 8:50 PM, Konstantin Ritt ritt...@gmail.com wrote:
Can't it be a private API in 5.1?
That's a good idea. Why didn't I think of that? That also provides
more flexibility while working towards unification.
If it
On Mon, Mar 25, 2013 at 11:32 AM, Stephen Kelly stephen.ke...@kdab.com wrote:
On Monday, March 25, 2013 10:46:37 Alan Alpert wrote:
On Sat, Mar 23, 2013 at 8:50 PM, Konstantin Ritt ritt...@gmail.com wrote:
Can't it be a private API in 5.1?
That's a good idea. Why didn't I think of that? That
Hello,
I would like to backport QPlatformIntegration::styleHint(StyleHint hint) to
Qt4, but that would involve adding a virtual method to the class. Is it
acceptable to do is at this poing in Qt 4.8? I know it breaks ABI but since
QPlatformIntegration is a private class, I was wondering if that
On Mon, Mar 25, 2013 at 03:47:22PM -0300, Rafael Roquetto wrote:
Hello,
I would like to backport QPlatformIntegration::styleHint(StyleHint hint) to
Qt4, but that would involve adding a virtual method to the class. Is it
acceptable to do is at this poing in Qt 4.8? I know it breaks ABI but
Hi,
A this point in time, I think it is better to plan for dropping those parts
from Beta we for some reason do not want to include to release. That said,
reviews can be done already now if some part still needs it. We are just so
close to Alpha that there is not time any more to do much
On segunda-feira, 25 de março de 2013 10.46.37, Alan Alpert wrote:
On Sat, Mar 23, 2013 at 8:50 PM, Konstantin Ritt ritt...@gmail.com wrote:
Can't it be a private API in 5.1?
That's a good idea. Why didn't I think of that? That also provides
more flexibility while working towards
On 3/25/13 7:13 PM, Laszlo Papp lp...@kde.org wrote:
qtx11extras and qtserialport didn't need a merge, since they didn't have
dev/stable branches.
We got that sorted out a couple of days ago, but it does not require any
work for the moment as stable got branched off master. Then, we just
began
On segunda-feira, 25 de março de 2013 17.05.12, Frederik Gladhorn wrote:
Mandag 25. mars 2013 08.30.45 skrev Thiago Macieira:
On segunda-feira, 25 de março de 2013 10.46.50, Sergio Ahumada wrote:
Next step is to get qt5.git updated and add qtquickcontrols, qtsensors,
qtserialport and
Hi,
I've just pushed another set of patches for the QTimeZone and QDateTime
changes. The current status is I think the code is now stable enough for a
final review and decision on whether to include in 5.1 or not.
The QDateTime changes for OffsetFromUTC and the formatter improvements can
On Monday, February 25, 2013 17:12:02 Stephen Kelly wrote:
On Monday, February 25, 2013 08:07:48 Thiago Macieira wrote:
It was a matter of timing. Since GCC 4.8 is not released yet, I can't make
the case for it being a P1.
I fully disagree with that :). I think compile fixes for compilers
tl;dr - This is a step in a good direction. I don't think it is usable as-is
for Plasma, but it could mature into such a thing. I'm unconvinced this is
ready for 5.1, particularly not as public API, but could be polished into
something shiny for 5.2
and now I will ramble on below ;)
(as I
On segunda-feira, 25 de março de 2013 22.46.36, Stephen Kelly wrote:
On Monday, February 25, 2013 17:12:02 Stephen Kelly wrote:
On Monday, February 25, 2013 08:07:48 Thiago Macieira wrote:
It was a matter of timing. Since GCC 4.8 is not released yet, I can't
make
the case for it being
I have built a qt4.8 for the Freescale i.mx6 ART board and I have
successfully integrated the qt4.8 qmake into qtcreator. However, when I try
to view my qml scripts with the designer tab in qtcreator, the designer tab
is always grayed out. I learned that the problem is the qmldesigner plugin
did
On Mon, Mar 25, 2013 at 4:23 PM, Aaron J. Seigo ase...@kde.org wrote:
tl;dr - This is a step in a good direction. I don't think it is usable as-is
for Plasma, but it could mature into such a thing. I'm unconvinced this is
ready for 5.1, particularly not as public API, but could be polished into
29 matches
Mail list logo
