Based on the output below, I think there might be a path invariance between
prefix and QTDIR, if you have that set.
So, make sure that $$QTDIR is the same as $$[QT_HOST_PREFIX]. If you have QTDIR
set, then qmake will pass '-qtdir path' to syncqt on invocation. Check that
against what 'qmake
On 05/18/2012 07:36 AM, Иван Комиссаров wrote:
Btw, you're saying that painter technology is outdated?
Well it is also the API for rendering PDF ( and other paint devices )
documents. Having common code for screen and PDF rendering is absolutely
not outdated - and is possible using
Sounds like marketing?
It might be a 'constant' in the grand scheme of big-O notations. However,
if the result is that you can only get 24 fps on low-end HW with large
power footprint vs. 60 fps with HW acceleration, lower power footprint and
leaving the main CPU to do more important tasks, what
Hi Quim,
I can (and would be happy to) arrange a session about QtPim APIs
(Contacts, Organizer, Versit) in 5.0 and changes / evolution of those APIs
from the QtMobility ones.
Gerrit / Git history for qtpim repo shows that the number of contributors
has been quite limited so far, so definitely a
On 5/18/12 8:22 AM, ext Uwe Rathmann uwe.rathm...@tigertal.de wrote:
I would be careful with terms like outdated. In the end the desktop is
the concept of the 90s ( widget are much older ) and the current
desktops are the part that doesn't work on smartphones alike devices.
But are keyboard and
On 5/15/12, BRM bm_witn...@yahoo.com wrote:
It would probably be good for a statistically significant poll to be
officially done.
I'd expect that it would probably have a 50/50 split, or may be a 60/40
split in favor of QML
as I do expect there is still a lot of momentum behind the QWidgets
Hi,
on QtCS, we will have a session on Qt and Qt SDK packaging. The exact details
are can be found at
http://qt-project.org/groups/qt-contributors-summit-2012/wiki/Packaging-Qt. If
you want to attend or
have any addition to the program, feel free to amend the wiki page. If you have
questions.
On sexta-feira, 18 de maio de 2012 05.54.10, marius.storm-ol...@nokia.com
wrote:
This probably means we should keep the old repo there for backwards
compatibility, and with documentation stating that the module is old and
out-of-date, and where and how they can get a more recent version.
I
On Thu, May 17, 2012 at 1:35 PM, Atlant Schmidt
aschm...@dekaresearch.com wrote:
Peter, et al.:
We don't wanna use obsolete stuff with a architecture from
the 90s in times where graphical technology has moved on (Thiago).
Computer architectures don't necessarily become obsolete.
Oh,
On 5/18/12 10:14 AM, ext Thiago Macieira thi...@kde.org wrote:
On sexta-feira, 18 de maio de 2012 05.54.10, marius.storm-ol...@nokia.com
wrote:
This probably means we should keep the old repo there for backwards
compatibility, and with documentation stating that the module is old and
On Wed, May 16, 2012 at 03:55:41PM -0700, ext Quim Gil wrote:
- How valuable is to have an efficient tool for handling translations
between teams - as opposed to whatever process we have now? Are we happy
with the current system? Do we believe we would improve significantly
with a tool like
What is the time to merge the origin/buildsystem into origin/master?
When it's ready? or have a plan?
I am do not set the QTDIR env value as the wiki says.
The mean the 'QTDIR' env does not exist.
The configure command on Windows:
%QTSOURCE%\configure -opensource -prefix %CD%\qtbase
Just try to do
%QTSOURCE%\configure -opensource -prefix
D:/qpSOFT/Projects/BuildQt5-x86-tdm/qtbase -confirm-license -platform win32-g++
-debug-and-release -fast -nomake examples config.log 21
Instead, and see if that helps.
--
.marius
On 5/18/12 11:37 AM, ext Loaden
On Friday, May 18, 2012 08:41:13 marius.storm-ol...@nokia.com wrote:
Until the Phonon maintainers speak up and let us know what their plans
for Qt
5 are, we should consider our qtphonon.git module a disservice to
everyone. If
none of them speak up, I recommend removing the module from the
You need users who will use Qt to survive. And those are desktop developers.
Show me lot of not hello world apps writte using qml. Where are they? On
symbian? Maybe in MeeGo? I don't see any on the desktop. But i see Guitar Pro
right now which is based on QWidgets.
About O-notations. Article i
On 5/18/12 12:02 PM, ext Stephen Kelly
stephen.ke...@kdab.commailto:stephen.ke...@kdab.com wrote:
On Friday, May 18, 2012 08:41:13
marius.storm-ol...@nokia.commailto:marius.storm-ol...@nokia.com wrote:
We did promise a minimal migration path from Qt 4 to Qt 5, and removing
the phonon
Kate:
Often, the proponents arguing for new and improved are
simply arguing for the position they think will be most fun
to work on; after all, it's always more fun to break exciting
new ground than it is to have trod the same old sod yet again.
But many of these new approaches are
On 05/18/2012 09:07 AM, marius.storm-ol...@nokia.com wrote:
Often it's hard to beat the performance of the main CPU(s for most people
these days) filling in a polygon directly, rather than handing it off to a
GPU.
Guess this is the reason behind the decision why in Qt 4.8 raster has
become
On Friday, May 18, 2012 10:43:18 you wrote:
Right, no attention from us and no attention from the phonon developers, at
least with respect for Qt 5 end-users. So, by it receiving 'attention' from
us now by simply removing the old fork from the repo, it would only hurt
the end-user, making it
Hi there,
The issue raised in this thread:
http://thread.gmane.org/gmane.comp.lib.qt.user/1880
Can be simplified to this example:
QWindow window;
QWidget widget;
window.show();
widget.show();
// This should not quit the application, because
// the QWindow is still
Hi Laszlo,
On Tue, May 15, 2012 at 10:45 PM, Laszlo Agocs laszlo.p.ag...@nokia.com wrote:
Hi,
Because windowing systems will usually provide absolute coordinates in
their pointer events, hiding all the cursor management, raw event
translation, etc. hassle from the clients. Also the Qt
On 05/18/2012 05:22 PM, ext Girish Ramakrishnan wrote:
Related: eglfs currently is just a graphical plugin and has no input
support out of the box. eglfs (from it's background as a reference for
qpa) has however become the gold standard for practically all devices
using Qt5 in the absence of
Hi all,
I also neglected to introduce myself -- I'm the chief ninja at
Transifex and its original developer. I'd be happy to answer any
questions.
## More information to help create a better picture
Using the common instance on Transifex.net allows you to re-use
existing open-source
Hello,
I've been following this thread since it started. My impression is that Qt
people believes we (users-devs) want to force you into further developing a
C++ toolkit (which might or might not be outdated). But I understand that
you will do work on what are *ordered* to work on, by your boss.
On sexta-feira, 18 de maio de 2012 20.34.51, Thiago Macieira wrote:
(P1) expand the size of QBasicMutex and QMutex to accommodate more data,
for Mac and Windows. On Windows, the extra data required is one pointer (a
HANDLE), whereas on Mac it's a semaphore_t. Depending on the next task, we
On Friday 18 May 2012 20:34:51 Thiago Macieira wrote:
Hello
I've just completed a review of the QMutex family internals, as well as
the Intel optimisation manuals about threading, data sharing, locking and
the Transactional Memory extensions.
Short story: I recommend de-inlining QMutex
https://bugreports.qt-project.org/browse/QTBUG-25817
I tried both MacPort clang 3.1 and Apple's so-called LLVM 4.0 to build
Qt and create apps with C++11 turned on. Both failed with constexpr errors.
On the other hand, compiling using gcc 4.7 is successful. I am not sure
if gcc is more lex on
On sexta-feira, 18 de maio de 2012 22.45.22, Olivier Goffart wrote:
On Friday 18 May 2012 20:34:51 Thiago Macieira wrote:
Hello
I've just completed a review of the QMutex family internals, as well as
the Intel optimisation manuals about threading, data sharing, locking and
the
Wayland with shared memory:
http://qt-project.org/wiki/RaspberryPi
and you are golden. If you are seriously a QWS user, you are a
thousand times better off now than you ever were before, Qt/Embedded
has an order of magnitude more visibility/resources working on it now.
Qt for resource
This; Widgets is stable API and we will not break your code if you
rely on it. Rejoice!
Qt 4.6 was a performance release; From Qt 4.5 - Qt 4.6 we focused on
making Qt as performant as possible rather than introducing new
functionality. We reached the point of diminishing returns, QWidget is
very
QML may be revolutionary, but it does not target the right camp. It
targets the designer/amateur-coder audience. Awww, poor baby. C++ too
hard for you? Here's some meta-descriptive-GUI language where you can
use simple javascript statements/code to implement all your back-end
(and
Just look at what can be done on the Raspberry Pi with scene graph +
wayland, and tell me you can do the same with QPainter + X11 through the
Pi's main CPU!
http://www.youtube.com/watch?v=HItv4HX5r3k - Qt 5 and Wayland on the
Raspberry Pi
This succinctly summarizes our sentiments; We can
Hey,
On Fri, May 18, 2012 at 3:40 AM, Иван Комиссаров abba...@gmail.com wrote:
And what about KDE? It is all based on QWidgets. And it took them many years
to make stable release for KDE 4 (KDE 4.4 was the first release i could
use). You want them to reimplement whole KDE using QML?
I thought
On Friday 18 May 2012 23:25:47 Thiago Macieira wrote:
QBasicMutex is an internal POD class that offers non-recursive locking.
It's incredibly efficient for Linux, where the single pointer-sized
member variable is enough to execute the futex operations, in all cases.
For other
I thought the KDE dudes were already testing it against Qt 5. Anyone
on this list in a position to comment as to the current state of
things?
Well, we have been using Harmattan, Plasma Components and so forth for
experiments. QML and the component theory are way immature for using
this KDE
35 matches
Mail list logo
