On Wed, 2 Nov 2011 18:03:21 ext Samuel Rødal wrote:
Hello,
I'm one of the guys who have been working on the Lighthouse API changes
for Qt 5 and new Qt 5 APIs like QWindow and QScreen. For those who are
not familiar, QWindow is the low-level Qt abstraction of a native window
that has its own
Samuel's mail about exposing QScreen API mentions that a Window element might
be useful to have in QML, and I concur. One area where you cannot really avoid
splitting your UI across multiple windows is for multiple screens (e.g. an
external display), and without a basic window abstraction in
On Monday, 7 de November de 2011 14:56:57 Johannes Zellner wrote:
Hi,
I have problems building Qt5 these days, when trying to set a different
prefix other than described in the README $PWD/qtbase
qtbase builds fine, but any other module/add-on wont build due to:
QMAKESPEC has not been set,
On Monday, 7 de November de 2011 15:31:27 João Abecasis wrote:
To bootstrap the discussion I started a wiki page with a short list of
suggested supported compilers and platforms for Qt 5:
http://wiki.qt-project.org/Supported_Platforms
At the bare minimum, I think we should strive to
On Sun, Nov 6, 2011 at 2:09 PM, Rohan McGovern rohan.mcgov...@nokia.com wrote:
Chris Meyer said:
I'm configuring qtbase (Mac OS 10.6.8, Xcode 4.2, and qtbase/master)
using the following command:
export QTDIR=/some/path/for/installation
./configure -prefix $QTDIR -opensource -no-sql-mysql
Reading Alan's post a couple times, I *think* this summarizes to:
(a)- A new Window{} element is being proposed for QML that is different
from the current QML components. Specifically, the new Window{} is a
top-level concept, where you could have more-than-one, such as one for
each monitor.
On 08/11/2011, at 8:40 AM, Olivier Goffart wrote:
On Monday 07 November 2011 19:52:37 Thiago Macieira wrote:
On Monday, 7 de November de 2011 17:42:22 jan-arve.saet...@nokia.com wrote:
Don't we need to agree on what criteria a platform needs to fulfill in
order to be supported? The supported
On 08/11/2011, at 1:31 AM, João Abecasis wrote:
At the bare minimum, I think we should strive to support these compilers:
- GCC 4.2 and up
- MSVC 2008 and later
- Clang (trunk)
On the page above I also put in a list of platforms, splitting them between
Desktop, Embedded and
On Tuesday 08 November 2011 08:50:14 craig.sc...@csiro.au wrote:
On 08/11/2011, at 8:40 AM, Olivier Goffart wrote:
In that case, #ifdef are going to be added around that kind of API that
cannot be used with that compiler.
This is one reason rvct did not have QtConcurrent.
I think we
On Monday, 7 de November de 2011 23:10:03 Olivier Goffart wrote:
I know the difference.
But still, that API can be disabled for compiler not supporting that
feature (as this was the case wth QtConcurrent on symbian, or as this was
the case with QObject::findChildren on VC6)
We should really
On Tue, 8 Nov 2011 05:45:01 ext Charley Bay wrote:
Reading Alan's post a couple times, I *think* this summarizes to:
(a)- A new Window{} element is being proposed for QML that is different
from the current QML components. Specifically, the new Window{} is a
top-level concept, where you
11 matches
Mail list logo
