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, wher
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 re
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 thin
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, Embe
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 s
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 platforms will change as times go
> > by, so t
2011/11/7 Thiago Macieira :
> On Monday, 7 de November de 2011 11:44:56 Chris Meyer wrote:
>> I don't know the history of the endian test; but it seems to make more
>> sense to use something direct like:
>>
>> int num = 1;
>> if(*(char *)&num == 1)
>> {
>> printf("Little-Endian\n");
>> }
>> els
On Monday, 7 de November de 2011 11:44:56 Chris Meyer wrote:
> I don't know the history of the endian test; but it seems to make more
> sense to use something direct like:
>
> int num = 1;
> if(*(char *)&num == 1)
> {
> printf("Little-Endian\n");
> }
> else
> {
> printf("Big-Endian\n");
> }
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 Sun, Nov 6, 2011 at 2:09 PM, Rohan McGovern 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 -qt-libpng
>> -qt
Thank you for your support in the creation of a new mailing lists for
marketing & community specific discussion.
Enhancement request filed at
https://bugreports.qt.nokia.com/browse/QTWEBSITE-311 for better tracking.
Feel free to comment further there.
--
Quim
__
On Sun, Nov 6, 2011 at 2:09 PM, Rohan McGovern 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 -qt-libpng
>> -qt
On Sun, Nov 6, 2011 at 2:09 PM, Rohan McGovern 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 -qt-libpng
>> -qt
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 platforms will change as times go by,
> so the list will need to be updated by some criteria (it might cause
>
Abecasis Joao (Nokia-MP-Qt/Oslo) wrote on 2011-11-07:
> Hi,
>
> Time and again there is some (not-so-recent) language or compiler
> feature (e.g. C99 variadic macros, TR1, , ...) that someone
> would like to use in Qt. We usually go it the safe way out: either the
> feature is used inside feature
Joerg Bornemann wrote:
> On 07/11/11 17:36, ext Thiago Macieira wrote:
>> The list I had on IRC was similar to yours above, but it called for MSVC
>> 2005.
>> And the reason why was to try and get 90% to 99% of the current users of Qt.
>> But I wasn't calling for supporting them, it was just the
Thiago Macieira wrote:
> On Monday, 7 de November de 2011 15:31:27 João Abecasis wrote:
>> For the time being, I'm interested in the most basic level of support:
>> ensuring the code compiles, keeping language and compiler feature #ifdef's
>> at a maintainable (minimum) level, while still allowing
On 07/11/11 17:36, ext Thiago Macieira wrote:
> The list I had on IRC was similar to yours above, but it called for MSVC 2005.
> And the reason why was to try and get 90% to 99% of the current users of Qt.
> But I wasn't calling for supporting them, it was just the beginning of the
> discussion.
On Monday, 7 de November de 2011 10:24:03 Keith Gardner wrote:
> Hi,
>
> When specifying Visual Studio, could you specify the support for x86, IA64,
> and AMD64 architectures? I know that supporting a compiler is one thing,
> but supporting an architecture is another.
x86 and x86-64 definitely. T
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 t
Hi,
When specifying Visual Studio, could you specify the support for x86, IA64, and
AMD64 architectures? I know that supporting a compiler is one thing, but
supporting an architecture is another.
Keith
-Original Message-
From: development-bounces+kgardner=zebraimaging@qt-project.o
Hi,
> Hi,
>
> >It'd be nice to have a list of reference platforms and even better if such
> >platforms had maintainers who'd provide testing results, help fix issues
> >and>generally ensure the platforms are in a working state. Supporting a
> >platform may also have implications on the release
On Thursday, November 03, 2011 16:34:21 Stephen Kelly wrote:
> On Thursday, November 03, 2011 01:05:49 Stephen Kelly wrote:
> > I think ossi still has some feedback on it that we can work on later,
> > but
> > I've tested it, and it works just as the shell script version worked.
> > Additionally,
Hi,
Time and again there is some (not-so-recent) language or compiler feature (e.g.
C99 variadic macros, TR1, , ...) that someone would like to use in Qt.
We usually go it the safe way out: either the feature is used inside
feature-specific #ifdefs or its use is ditched altogether and we work a
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 bee
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, so configuration cannot be deduced."
The issue is that a "make inst
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 QML
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 it
28 matches
Mail list logo
