Hi,
Den 30. mai 2012 15:23, skrev ext Diego Iastrubni:
On Wed, May 30, 2012 at 4:11 PM, Olivier Goffart oliv...@woboq.com
mailto:oliv...@woboq.com wrote:
On Saturday 26 May 2012 12:51:23 Stephen Kelly wrote:
Hi,
There is a discussion on a kde list touching on whether
Hi Stephen,
Den 26. mai 2012 12:51, skrev ext Stephen Kelly:
Hi,
There is a discussion on a kde list touching on whether there is a replacement
for QtScript in Qt 5.
http://thread.gmane.org/gmane.comp.kde.devel.kwrite/32993/focus=75079
Is the QJSEngine the start of public API providing a
Den 25. mai 2012 02:35, skrev ext christopher.ad...@nokia.com:
Hi,
In QtQuick 2.0 (ie, Qt 5.0), we are thinking about using property var
more often in the implementation (eg, of qobject-derived-type
properties) to avoid some of those edge-cases, and providing more
consistent (and useful)
Hi,
Den 23. mai 2012 09:02, skrev ext Simon Hausmann:
Hi,
I would like to nominate Peter for approver status.
As part of the team in the University of Szeged he has completed the past few
rebases of V8 in the qtjsbackend module, a task that is anything but easy,
with a fast moving upstream
Hi,
The const char *-based API is now gone
(https://codereview.qt-project.org/#change,24426).
Thanks to all who helped get the qt5 submodule porting changes through.
Best regards,
Kent
Den 30. april 2012 14:14, skrev ext Kent Hansen:
Hi all,
Quick links: https://bugreports.qt-project.org
Hi,
It's removed now.
Kent
Den 11. mai 2012 09:50, skrev ext Kent Hansen:
Hi,
See https://codereview.qt-project.org/#change,25891
In short, QT += declarative and the QtDeclarative headers/classnames
will no longer work (i.e., code that use them won't compile).
I went through the qt5.git
Hi Holger,
Den 08. mai 2012 23:04, skrev ext Holger Hans Peter Freyther:
Hi,
I am looking into why QtV8 stopped working for MIPS (the obvious candidate is
that there is lithium support now). While doing this I noted that in
FullCodeGenerator::EmitResolvePossiblyDirectEval the following is
qtdeclarative/api_changes got merged, and now several others after that.
qtpim, qtsensors and qtsystems still remaining (merge attempts are all
in progress).
Best regards,
Kent
Den 18. april 2012 00:29, skrev ext Donald Carr:
yetch, and again, sorry Kent
Were I but a beautiful woman, I
Den 12. mars 2012 23:45, skrev ext Rohan McGovern:
Richard Moore said:
On 12 March 2012 17:56,kent.han...@nokia.com wrote:
Besides flaky tests, we also have the general/recurring problem of changes
going into qtbase that break qtdeclarative (and possibly/likely other
modules). While I
Den 13. mars 2012 12:08, skrev ext Kent Hansen:
It's difficult to know which type of changes can break stuff in other
modules, but things like
- QtCore/Gui event/timer handling
- Gui text/font changes
- Network changes (declarative uses networking extensively)
- Changing the semantics
Hi,
qtdeclarative needs to be adapted to some recent changes in qtbase.
While we try to get that done
(http://codereview.qt-project.org/#change,18941), staging of unrelated
changes to qtdeclarative has been blocked.
Best regards,
Kent
___
Development
Yes, please! Welcome back, Girish!
Kent
Den 06. mars 2012 10:06, skrev ext lars.kn...@nokia.com:
Hi,
I'd like to nominate Girish for Approver status. He's been around Qt for a
pretty long time, working for Trolltech a couple of years ago, then having
his own consultancy company doing Qt
Den 15. feb. 2012 08:38, skrev ext gunnar.sle...@nokia.com:
For some time we have wanted to unify the behavior of qreal on desktop and
embedded. Currently, qreal is defined to be double on desktop and to a float
on embedded.
The reasons for unifying are:
- Using double is pure waste for
Hi,
As part of http://codereview.qt-project.org/#change,14763 (new
meta-object data format) it would be good to change the return type of
QMetaMethod::signature() from const char * to QByteArray.
In the new meta-data format, the raw, 0-terminated signature string is
no longer stored; the
Yep. https://bugreports.qt-project.org/browse/QTBUG-24154
Kent
Den 08. feb. 2012 13:40, skrev Knoll Lars (Nokia-MP/Oslo):
Ok, this one makes sense to finish IMO.
Can you please add a Jira task for it, and make it a subtask for 20885?
Lars
On 2/8/12 1:20 PM, ext Kent
Den 02. feb. 2012 14:39, skrev ext Caio Marcelo de Oliveira Filho:
Hello,
I didn't have time to provide a patch this week, but I would like to
get this in Qt 5.0 if possible -- I'm willing to write the necessary
changes and tests for it.
QTBUG-9380: It would be useful if QStateMachine had a
Hi,
It would be useful to have a QByteArrayRef class, similar to QStringRef
-- a thin wrapper that doesn't copy the data.
Did anyone implement it already? If not, I can take a stab at it.
Kent
___
Development mailing list
Development@qt-project.org
Den 01. feb. 2012 09:47, skrev ext Olivier Goffart:
Facts:
1) QMetaObjectBuilder is private, its API may still change from minor version
to minor version
That's fine. It's still better (lower maintenance) than having
home-grown / incompatible generators floating around, IMO.
2) Qt maintain
Den 01. feb. 2012 12:48, skrev ext Robin Burchell:
2012/2/1 Jedrzej Nowackijedrzej.nowa...@nokia.com:
Yes, and by updating QMetaObjectBuilder we will update data generated by
ActiveQt. ActiveQt would use the newest meta object version (faster
tested).
As (I think) was raised on Gerrit - this
Hi,
Does anyone care about the ActiveQt module for Qt5?
A problem with this module is that it doesn't have any autotests. I can
run some on the examples, but I don't really know what they're supposed
to do, or how to use them to exercise relevant codepaths.
The main reason I'm asking is
Den 30. jan. 2012 06:03, skrev Rohan McGovern:
As Joao mentioned, this relates to a dry run of the CI feature.
I think that we need a method of requesting that some test procedure is
run over your change in gerrit, without also testing some set of everyone
else's changes at the same time, and
Hi,
Sometimes there are changes to qtbase that the author and/or reviewers
strongly suspect will break one or more modules on top of it (e.g. in
qt5.git). For example, source-incompatible changes (removing
QEventLoop::DeferredDeletion), or changes to the meta-type/QObject
internals (which
Den 27. jan. 2012 09:20, skrev Alan Alpert:
On Fri, 27 Jan 2012 18:09:46 ext Kent Hansen wrote:
Hi,
Sometimes there are changes to qtbase that the author and/or reviewers
strongly suspect will break one or more modules on top of it (e.g. in
qt5.git). For example, source-incompatible changes
Den 27. jan. 2012 14:07, skrev ext Olivier Goffart:
On Friday 27 January 2012 09:09:46 Kent Hansen wrote:
[...]
If there is no quick fix, the last resort is to pin one or
more of the dependencies' to a particular SHA1 (e.g. from the qt5.git
submodule) in the sync.profile until the issue has
Den 03. jan. 2012 22:07, skrev ext lars.kn...@nokia.com:
On 1/3/12 5:45 PM, ext Oswald Buddenhagenoswald.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
Hi,
See https://bugreports.qt.nokia.com/browse/QTBUG-22889
Once http://codereview.qt-project.org/#change,9948 goes through CI,
QtQuick will be a separate module (AKA library). This is where all the
QtQuick (2.0) types will live, and QtQuick-specific C++ APIs, like
QQuickItem and scenegraph.
Den 02. des. 2011 09:59, skrev Kent Hansen:
Den 02. des. 2011 09:33, skrev ext Kent Hansen:
Hi,
See https://bugreports.qt.nokia.com/browse/QTBUG-22889
Once http://codereview.qt-project.org/#change,9948 goes through CI,
Since the commit is so huge, there's a high likelyhood of conflicts
Den 02. des. 2011 16:13, skrev ext Charley Bay:
snip, Kent upcoming patch changes
Den 02. des. 2011 09:33, skrev ext Kent Hansen:
Hi,
See https://bugreports.qt.nokia.com/browse/QTBUG-22889
Once http://codereview.qt-project.org/#change,9948 goes through CI,
This seems
One thing we just remembered is that we want to have v8 snapshot support
when cross-compiling.
So we'll have a mkv8snapshot tool that must run on the host.
How can that be achieved if we move v8 out of qtbase? Currently
makefiles for host tool are handled in configure, see this line:
Hi,
bcd16f9453e543ba819385d87bd7061a4caeb325 bumps the sha1 for the V8
submodule, and introduces some build changes to src/v8. You'll need to
do git submodule update to be able to build libQtV8 again.
Thiago, I missed the previous discussion on V8's location. Since
everyone seems to agree that
30 matches
Mail list logo
