Hi,
in a recent conversation on QtDN, we have identified a possible bug in
QML (Qt Quick 1, that is. It's possible that the both issues affect
QtQuick2 too). We have also identified a confusing situation that can
be easily clarified in QDoc. First, a link to the discussion, then a
short recap on
On Mon, Jan 2, 2012 at 8:20 AM, gunnar.sle...@nokia.com wrote:
QIcon is a style concept and belongs together with QStyle and we do not want
QStyle in QtGui. As both the QFileSystemModel and QStandardItemModel relies
on it, they cannot be moved to Gui. At least not without some surgery, and
+1 from me!
Cheers,
Lars
On 12/29/11 3:14 AM, ext Thiago Macieira thiago.macie...@intel.com
wrote:
I'd like to nominate Robin Burchell (a.k.a. w00t on IRC) for approver in
Qt.
He's been around Qt for some time now and has been contributing both in
his
work time and in his personal time. He
On 12/30/11 10:26 PM, ext Thiago Macieira thiago.macie...@intel.com
wrote:
On Thursday, 29 de December de 2011 15.16.19, jason.bar...@nokia.com
wrote:
Hi Thiago,
I can get started, but I need to know: how is this code tested? How
can I
verify that things are working?
The best way to
On 12/29/11 8:48 PM, ext Thiago Macieira thiago.macie...@intel.com
wrote:
I'm thinking the whole architecture might need to change:
gcc $ make .obj/release-shared/qdrawhelper.o | grep -c LOOP\ VECTORIZED
112
icc $ make .obj/release-shared/qdrawhelper.o | grep -c LOOP\ WAS\
VECTORIZED
107
On Tuesday 03 January 2012 12:33:36 Peter Hartmann wrote:
I also like first making the parts still in use private; getting rid of
it completely is a bigger task, as it requires rewriting parts of the
HTTP socket engine and QAuthenticator IIRC.
Peter
On Friday 30 December 2011 14:55:55 Denis Dzyubenko wrote:
Hi guys,
With a qt5 module that we are developing, qtjsondb, we stumbled upon
an issue with moc and our classes that are inside a namespace. Let me
illustrate it with a code:
jsondb-global.h:
#if defined(QT_NAMESPACE)
#
2011/12/29 Thiago Macieira thiago.macie...@intel.com:
I'd like to nominate Robin Burchell (a.k.a. w00t on IRC) for approver in Qt.
He's been around Qt for some time now and has been contributing both in his
work time and in his personal time. He was also my main external sparring
partner when
On Tue, Jan 3, 2012 at 2:01 PM, Denis Dzyubenko de...@ddenis.info wrote:
2011/12/29 Thiago Macieira thiago.macie...@intel.com:
I'd like to nominate Robin Burchell (a.k.a. w00t on IRC) for approver in Qt.
He's been around Qt for some time now and has been contributing both in his
work time and
CONFIG(host, host|target) {
# Do host stuff
} else {
# Do target stuff
}
Might work, if you know the host or target mkspecs. However, for general
purpose we can introduce variables which contain these.
QMAKE_HOST_SPEC=host
QMAKE_TARGET_SPEC=target1 target2
for example..
--
On Tuesday, 3 de January de 2012 15.21.26, lars.kn...@nokia.com wrote:
Not sure how it works currently. But in general it'd be good if we can fix
this once and for all by adding proper cross compilation support to
qmake/configure. Something where you can specify host vs target in the
.pro
On Tue, Jan 03, 2012 at 01:45:27PM -0200, ext Thiago Macieira wrote:
Configure already sets a default mkspec symlink that matches the target
mkspec. Making it also create a symlink for default-host which matches the
host platform would be easy.
The tricky part is using that.
You could
On Tuesday, 3 de January de 2012 16.12.11, kai.koe...@nokia.com wrote:
PS: Was there a similar in Trolltech times, too? I'm getting old , I can't
remember :(
No, it was different. It was the LICENSE.TROLL file's presence that triggered
the troll build.
See:
The Qt Contributors Summit is an event by / for the developers
subscribed to this list. Let's have here the discussion about the big
items and then we can move to the [marketing] list for the
'implementation details'.
It is urgent to book a location! Let's focus the discussion in the
points
Hi Thiago,
2012/1/3 Thiago Macieira thiago.macie...@intel.com:
On Friday, 30 de December de 2011 14.55.55, Denis Dzyubenko wrote:
In qt5 modules we have exactly the same problem as in namespaced-Qt
itself. Hence my suggestion to solve it in the same way - I would like
to be able to re-use
Hi,
Ok, you have caught the attention !
So, two platforms are slightly different (armv5 and armv7),
and one completely different (x86), so all this platforms must have their
own CXXFLAGS and must link to different libs.
Are you saying that all this things are possible using qmake ?
A little
On Tuesday, 3 de January de 2012 18.19.47, Denis Dzyubenko wrote:
That's the thing - it doesn't work in some cases - if you do
in-source-tree build of the attached project. Well now thinking about
it, it is probably a bug in qmake.
Denis.
You said:
This is because qmake decided that
On 03/01/2012 12:01, ext Thiago Macieira wrote:
On Tuesday, 3 de January de 2012 18.19.47, Denis Dzyubenko wrote:
That's the thing - it doesn't work in some cases - if you do
in-source-tree build of the attached project. Well now thinking
about it, it is probably a bug in qmake.
Sounds like
On 03/01/2012 12:20, ext Thiago Macieira wrote:
On Tuesday, 3 de January de 2012 18.16.46,
marius.storm-ol...@nokia.com wrote:
I know that because I had the exactly opposite problem Friday: I
had one .cpp (qdrawhelper.cpp) that I wanted to be compiled on
its own *and* as an #include from
On 03/01/2012 12:25, ext Jonas M. Gastal wrote:
On Tuesday 03 January 2012 18:11:08 marius.storm-ol...@nokia.com
wrote:
On 03/01/2012 11:14, ext Quim Gil wrote:
- When? There have been different opinions and the trend seems to
be that it is better to do it after Qt 5 is released, otherwise
Op 3-1-2012 19:48, marius.storm-ol...@nokia.com schreef:
On 03/01/2012 12:25, ext Jonas M. Gastal wrote:
On Tuesday 03 January 2012 18:11:08 marius.storm-ol...@nokia.com
wrote:
On 03/01/2012 11:14, ext Quim Gil wrote:
- When? There have been different opinions and the trend seems to
be that
Op 3-1-2012 21:14, Richard Moore schreef:
- How many rooms, which capacity? No need to get into details but having
a rough idea would be useful in order to book the right amount of space.
For you this means what type of event do you want: was the event last
year good or would you prefer a
On 1/3/12 5:45 PM, ext Oswald Buddenhagen oswald.buddenha...@nokia.com
wrote:
On Tue, Jan 03, 2012 at 01:45:27PM -0200, ext Thiago Macieira wrote:
Configure already sets a default mkspec symlink that matches the
target
mkspec. Making it also create a symlink for default-host which
matches the
Indeed, that looks elegant :)
Simon
--
Sent from my Nokia N903.01.12 17:46 skrev Buddenhagen Oswald (Nokia-MP/Berlin):
On Tue, Jan 03, 2012 at 01:45:27PM -0200, ext Thiago Macieira wrote:
Configure already sets a default mkspec symlink that matches the target
mkspec. Making it also create a
Starting a signal name with an underscore could be viewed as a violation of the
C++ standard, depending on how you interpret it. Item 17.4.3.1.2 in the
standard reserves names beginning with an underscore as for use only by the
implementation (ie the compiler):
17.4.3.1.2 Global names
Certain
Hi,
I've just been trying some experimental porting of code to Qt5.
It failed because QFormBuilder is no longer available. Then I noticed that the
entire designer library and interface is no longer available.
Why was that done and can it be undone?
Thanks,
--
Stephen Kelly
From the QtDeclarative point of view, apart from having our tests pass, I'd
like to see some comparisons in QML load time, using photoviewer as a test
case, for example.
Looks like performance was an important consideration in the new
implementation, but I'd like to see confirmation :-)
Br,
Hi,
1. The capitalization of the first alpha character after the underscore is
deliberate. Signal handlers are defined as being 'on' followed by a capital
letter. Since underscore has no capital, it must be the first non-underscore
letter.
2. on__PrivateSignal does work in Qt 5.0. We won't
@Craig:
Good to know, thanks. To be honest, I don't think anybody actually
tried double underscores for signal name, in the conversation on QtDN
it just cropped up as a sort of what if scenario.
But, to take it one step further - does that really matter in QML?
MOC, AFAIK, is using signals by
29 matches
Mail list logo
