Hi Lorn,
On Nov 20, 2012, at 1:42 AM, Lorn Potter lorn.pot...@gmail.com wrote:
On 20/11/2012, at 6:09 AM, Knoll Lars lars.kn...@digia.com wrote:
The beta2 is a very good milestone towards Qt 5. We now have packages that
include the full content of what we agreed to ship, including Qt
Hi,
[snip]
Does anyone have any further feedback on QML tool renaming before
these get implemented?
+1 from me, but I don't mind if qmlbundle stays where it is as an
undocumented, internal, no guarantees, tool, just because it's less effort.
Cheers,
Chris.
Sorry, can't reproduce your issue on 10.6.8. The default compiler on 10.6.8 +
xcode 3.2.6 should be g++ 4.2, not clang++. Apple doesn't provide it. So maybe
you are asking for the support of clang++ on 10.6, I guess.
And I think it's better to talk this kind of issue in interest mailing list,
So what? Me wait for an answer?
Best regards,
Denis
16.11.2012, 13:10, Denis Shienkov scap...@yandex.ru:
Hello all.
Please tell me, is it possible to somehow put the documentation for custom
add-on (eg QtSerialPort) of Qt Playground
on http://qt-project.org/doc/ or somewhere else?
For
On Monday 19. November 2012 21.09.35 Knoll Lars wrote:
The package creation time is currently being addressed, and hopefully we'll
soon be able to get that time down to around 2-3 hours (from 7-8
currently). In addition, I'd like to ask anybody to be careful with
changes that might affect
On 11/20/2012 10:01 AM, Jedrzej Nowacki wrote:
On Monday 19. November 2012 21.09.35 Knoll Lars wrote:
The package creation time is currently being addressed, and hopefully we'll
soon be able to get that time down to around 2-3 hours (from 7-8
currently). In addition, I'd like to ask anybody to
On 20/11/2012, at 6:20 PM, Knoll Lars lars.kn...@digia.com wrote:
Hi Lorn,
On Nov 20, 2012, at 1:42 AM, Lorn Potter lorn.pot...@gmail.com wrote:
On 20/11/2012, at 6:09 AM, Knoll Lars lars.kn...@digia.com wrote:
The beta2 is a very good milestone towards Qt 5. We now have packages
2012/11/19 Koehne Kai kai.koe...@digia.com
Hi,
Even if you're not using QML, you might look into using it's debugging
infrastructure. All you'll probably have to do is create a dummy QQmlEngine
at the start of your app: Since breakpoints, stepping are global for v8,
you should be able to
Jerome, thanks for the information.
Besr regards,
Denis
20.11.2012, 15:03, Pasion Jerome jerome.pas...@digia.com:
Hello,
Our intention is to include most of the Qt modules (in Qt Project) to our
snapshot: http://doc-snapshot.qt-project.org/
The site replacement, which has the links to the
On Tuesday, 2012-11-20, Michal Dorner wrote:
qmlRegisterTypeTest(MyModule, 1, 0, Test);
engine = new QQmlEngine();
component = new QQmlComponent(engine,
QUrl::fromLocalFile(module.qml));
if (!component-isLoading()) {
I think you can just call component-isError()
-Original Message-
From: development-bounces+kai.koehne=digia@qt-project.org
[mailto:development-bounces+kai.koehne=digia@qt-project.org] On
Behalf Of Alan Alpert
Sent: Tuesday, November 20, 2012 1:41 AM
To: development@qt-project.org
Cc: Thiago Macieira
Subject:
On Nov 19, 2012, at 4:42 PM, Thiago Macieira thiago.macie...@intel.com wrote:
On segunda-feira, 19 de novembro de 2012 14.03.17, Konstantin Tokarev wrote:
- The core of a concurrency engine should be a work-stealing data
structure/scheduler. Qt Concurrent has simple work-stealing
Hi,
I would like to propose that we establish the mailing list:
qt-l...@qt-project.org, to take over for the previous qt-l10n list.
We believe there are people who are interested in localization, that do not
follow the developer mailing list.
Br,
Sinan
Hello Qt developers.
When trying to build documentation for custom addon with qdoc for qt5-beta2 on
Windows:
$nmake docs
I get the following error:
g:\Qt\Qt5.0.0beta2\5.0.0-beta2\msvc2010\bin\qdoc.exe
-outputdir
Op 20-11-2012 16:04, Tanilkan Sinan schreef:
Hi,
I would like to propose that we establish the mailing list:
qt-l...@qt-project.org, to take over for the previous qt-l10n list.
We believe there are people who are interested in localization, that do not
follow the developer mailing list.
Hi
I am excited to inform you all that we are discussing to open up web
development for http://qt-project.org towards open governance for our community.
Right now we use IRC for discussion but now there is a clear need for mailing
list so our discussion can reach to all people in all time zone.
To summarize QML tool naming discussion so far:
In qtquick1 repo
qmlviewer - qml1viewer
qmlplugindump - qml1plugindump
That's already the name, isn't it?
In qtdeclarative repo
qmlscene - qml2scene
qmlplugindump - qml2plugindump
qmlbundle - move to playground
qmlmin - qmlmin
On Tue, Nov 20, 2012 at 8:00 AM, Jana Aurindam aurindam.j...@digia.com wrote:
To summarize QML tool naming discussion so far:
In qtquick1 repo
qmlviewer - qml1viewer
qmlplugindump - qml1plugindump
That's already the name, isn't it?
In qtdeclarative repo
qmlscene - qml2scene
On Tue, Nov 20, 2012 at 8:05 AM, Alan Alpert 4163654...@gmail.com wrote:
On Tue, Nov 20, 2012 at 8:00 AM, Jana Aurindam aurindam.j...@digia.com
wrote:
To summarize QML tool naming discussion so far:
In qtquick1 repo
qmlviewer - qml1viewer
qmlplugindump - qml1plugindump
That's already
On Tue, Nov 20, 2012 at 4:53 AM, Koehne Kai kai.koe...@digia.com wrote:
-Original Message-
...
Secondly qmleasing and
easingcurveeditor really should be merged. They both generate custom
easing curve strings for QtQuick 2 animations, just from different
parameters. I'll start that
On Tuesday, November 20, 2012 04:32:04 PM André Somers wrote:
Op 20-11-2012 16:04, Tanilkan Sinan schreef:
Hi,
I would like to propose that we establish the mailing list:
qt-l...@qt-project.org, to take over for the previous qt-l10n list.
We believe there are people who are
On terça-feira, 20 de novembro de 2012 13.15.47, Sorvig Morten wrote:
Let me give you an example of a thread pool used differently: the DNS
resolver code in QtNetwork. It uses 5 threads, regardless of how many
CPU cores you have. It involves a blocking call. And as such, it must not
use
On Tue, Nov 20, 2012 at 4:19 PM, Mitch Curtis mitch.cur...@digia.comwrote:
On Tuesday, November 20, 2012 04:32:04 PM André Somers wrote:
Op 20-11-2012 16:04, Tanilkan Sinan schreef:
Hi,
I would like to propose that we establish the mailing list:
qt-l...@qt-project.org, to take over
Hi,
There are two points I'd like to add to the discussion. Firstly qmlbundle
isn't
really useful yet, I'd advocate moving it to the playground or somewhere
outside the qtdeclarative module until it's done.
I've been wondering about this too. There's zero documentation of it right
now,
On Tue, Nov 20, 2012 at 4:04 PM, Chris Adams chris.ad...@qinetic.com.au wrote:
Hi,
There are two points I'd like to add to the discussion. Firstly
qmlbundle isn't
really useful yet, I'd advocate moving it to the playground or somewhere
outside the qtdeclarative module until it's done.
Last week in Berlin, Ossi, some others and I finally got together and hashed
out what remained to be discussed. We concluded the following for the co-
installation of tools:
Principle: Qt installs by themselves do not support co-installation of any
binaries to the same prefix's bindir. Instead,
Thanks for your reply. When I run configure with -developer-build, the
issue disappears, seems a bit stupid:(
On Tue, Nov 20, 2012 at 4:47 PM, Qi Liang liang...@digia.com wrote:
Sorry, can't reproduce your issue on 10.6.8. The default compiler on
10.6.8 + xcode 3.2.6 should be g++ 4.2, not
On 11/20/2012 05:05 PM, Alan Alpert wrote:
On Tue, Nov 20, 2012 at 8:00 AM, Jana Aurindam aurindam.j...@digia.com
wrote:
To summarize QML tool naming discussion so far:
In qtquick1 repo
qmlviewer - qml1viewer
qmlplugindump - qml1plugindump
That's already the name, isn't it?
In
28 matches
Mail list logo
