Hello!
Following up on the approver process for Hugues Delorme:
I only got positive feedback about making him an approver during the last 15
workdays, so I just went ahead and made Hugues Delorme a approver in gerrit.
Best Regards,
Tobias
Tobias Hunger
Software Engineer
Nokia, Qt Development
On 11 Nov 2011, at 09:03, ext tobias.hun...@nokia.com wrote:
Hello!
Following up on the approver process for Hugues Delorme:
I only got positive feedback about making him an approver during the last 15
workdays, so I just went ahead and made Hugues Delorme a approver in gerrit.
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:
On Friday 11 November 2011 08:02:38 Kent Hansen wrote:
Thiago, I missed the previous discussion on V8's location. Since
everyone seems to agree that QtCore shouldn't depend on V8, I guess
we're free to move it around again. One idea from Lars is that we move
it back to qtdeclarative and build
On Friday, 11 de November de 2011 11.03.13, Olivier Goffart wrote:
The problem of submodule will be the same within QtDeclarative.
How about making v8 its own module.
That's what I suggested. Having a submodule inside the module you're working
on makes it very hard to keep a handful of
Hi Qt Devs,
I am Zoltan Herczeg, a PCRE and a QtWebKit developer. Stephen Kelly told me
that Qt would like to replace the QRegExp engine with another regex engine
(http://thread.gmane.org/gmane.comp.lib.qt.qt5-feedback/1524/), and he _really_
encouraged me to tell you that we consider adding
Hi Zoltan,
Great to hear from you. UTF16 support would be a basic requirement for us
using it in Qt. We don't really need wchar_t support though.
Our main issue seem to be timing then. We currently have the opportunity
of changing API to some extend before we freeze down things for Qt 5
again.
hi,
On Fri, Nov 11, 2011 at 1:10 PM, lars.kn...@nokia.com wrote:
Our main issue seem to be timing then. We currently have the opportunity
of changing API to some extend before we freeze down things for Qt 5
again. Thus we'd need something relatively soon to be able to use it for
5.0.
hmm,
On Fri, Nov 11, 2011 at 2:45 AM, Alan Alpert alan.alp...@nokia.com wrote:
On Fri, 11 Nov 2011 05:01:32 ext Adriano Rezende wrote:
I think the Window element should not inherit from QQuickItem, since
it's not an element in the render tree; it's basically a window
representation that is not
