Dear All:
I have compiled qt5 for wayland and qtwebkit module success! And had a demo
browser running as a wayland client, So I wonder if some HTML5 function such
as fileapi can be supported in qtwebkit as well, but ,sadly when I add
--file-system option, it failed to compile. Can someone tell
On quarta-feira, 22 de fevereiro de 2012 17.23.53, lars.kn...@nokia.com wrote:
> Hi,
>
> also here it looks extremely challenging to disentangle all the code, as
> QSettings is still used in many places.
>
> So my proposal is that we don't do this change and instead simply
> deprecate QSettings as
On quarta-feira, 22 de fevereiro de 2012 17.51.07, Giuseppe D'Angelo wrote:
> The only points where the API isn't a replecement is where the other
> non-Perl QRegExp matchings are used (f.i. wildcard matching; but I saw
> that QRegExp has a nice wc2rx internal method to convert wildcards to
> a Per
On quarta-feira, 22 de fevereiro de 2012 17.11.17, lars.kn...@nokia.com wrote:
> Hi,
>
> this is the first mail where I'd like to go through the remaining features
> for Qt 5.0.
>
> I know that this bug is blocked by not having PCRE in 3rdparty/. But how
> is the status apart from this? Thiago, s
On 22 February 2012 17:11, wrote:
> Hi,
>
> this is the first mail where I'd like to go through the remaining features
> for Qt 5.0.
>
> I know that this bug is blocked by not having PCRE in 3rdparty/. But how
> is the status apart from this?
The "final" reviews (API, code, tests, docs) are miss
This is mostly done. What remains is the renaming of the classes from
QDeclarative to QQuick/QQml. This is ok for me to go into api_changes (you
might need to create that branch in qtdeclarative) with the compat hacks
we have (in moc and qtdeclarative).
Please add Jira tasks for the compat hacks s
These need to get done for 5.0. Most of this is about feature regressions
against 4.x, so the deadline end of next week doesn't apply. Nevertheless
it would be good if you can try to follow the guidelines as much as
possible:
* If you need changes in the QPA interfaces, please synchronize between
This is my own bug. Same rules as for containers branch applies here. Can
go into api_changes as long as it's fully SC. Deadline is end of next week.
Just to mention the current status: I have the new QMap implementation
working (and passing the tests) with the exception of insertMulti(). I
have g
Another one of the remaining features for 5.0
I'm ok for this to go into api_changes as long as it's fully source
compatible with what we have in Qt right now. Deadline is end of next week.
I think most of the work is done, so it should be possible to get it in by
then.
Cheers,
Lars
___
Hi,
also here it looks extremely challenging to disentangle all the code, as
QSettings is still used in many places.
So my proposal is that we don't do this change and instead simply
deprecate QSettings as soon as we have a proper replacement.
Comments?
Lars
___
Hi,
this is the first mail where I'd like to go through the remaining features
for Qt 5.0.
I know that this bug is blocked by not having PCRE in 3rdparty/. But how
is the status apart from this? Thiago, simply tell me if you feel
comfortable with the code and I'll do final review and approval. If
On Wednesday 22 February 2012 22:22:34 liang jian wrote:
> Hi, everyone,
> Recently I pushed two changes to Qt project for Qt5, I want them
> also be pushed to Qt4.8, so I change the code in my qt4 repository
> (cloned from gitorious.org), and try to commit it, To my surprise, the
> commit
Hi, everyone,
Recently I pushed two changes to Qt project for Qt5, I want them
also be pushed to Qt4.8, so I change the code in my qt4 repository
(cloned from gitorious.org), and try to commit it, To my surprise, the
commit message doesn't contain the Change-Id (I have copy the
commit-msg t
Hi everybody,
it's been now a little over two weeks since we announced the feature
freeze. But I am still seeing lots of discussions about refactoring of
code, API additions and other things that I'd count mostly as feature
development. All of these changes are nice in principle, but they do not
On quarta-feira, 22 de fevereiro de 2012 02.37.48, wolfgang.b...@nokia.com
wrote:
> OK,
>
> So we've now 2 options to set the config file.
> 1. QLOG_CONFIG_FILE environment variable
> 2. setDefaultConfigFile function.
>
> What do you mean with:
> ... and to supplying a QIODevice*?
void QLog::load
> -Original Message-
> > So how about adding another QtMsgType called QLogMsg, that qLog()
> uses? In contrast to qDebug/QtDebugMsg, qLog/QtLogMsg messages would
> not be processed by default, unless the configuration file (or an environment
> variable) says so ...
>
> There is no need fo
> -Original Message-
> From: Beck Wolfgang (Nokia-MP/Brisbane)
> Sent: Wednesday, February 22, 2012 1:38 AM
> To: Koehne Kai (Nokia-MP/Berlin); ext David Faure
> Cc: development@qt-project.org
> Subject: RE: [Development] QLog ( Work on qDebug and friends)
>
> Why you want to use the cate
17 matches
Mail list logo
