Greetings all,
Le 31/01/2013 14:10, List for announcements regarding Qt releases and
development a écrit :
> I'm happy to announce that Qt 5.0.1 is now released.
>
> See the blog on http://blog.qt.digia.com/blog/2013/01/31/qt-5-0-1-released/
I've just downloaded and insalled the (huge) bundle "Q
On segunda-feira, 4 de fevereiro de 2013 15.30.24, Knoll Lars wrote:
> > Importing ICU into qtbase is fine with me. Anyhow, I don't particular like
> > hard dependency to ICU from Qt5Core, since it forces everyone deploying a
> > Windows helloworld to also ship icudt49.dll with 17,5 MB (!).
> No, p
On 4 February 2013 21:42, Rafael Brandao wrote:
> I could also reproduce this bug here.
> The question is why MiniBrowser works and Snowshoe doesn't.
>
> MiniBrowser's explicits uses engine()->addImportPath, as you can see on
> webkit/Tools/MiniBrowser/qt/BrowserWindow.cpp.
> This is a quick fix
I could also reproduce this bug here.
The question is why MiniBrowser works and Snowshoe doesn't.
MiniBrowser's explicits uses engine()->addImportPath, as you can see on
webkit/Tools/MiniBrowser/qt/BrowserWindow.cpp.
This is a quick fix for snowshoe, which uses QML_IMPORT_PATH and explicitly
uses
On 02/04/2013 10:30 PM, Richard Moore wrote:
Snowshoe has been imported, but it doesn't actually run against the
dev branch here:
rich@linux-h33o:~/src/snowshoe> ./snowshoe
qrc:///qml/main.qml:53:5: Type TabWidget unavailable
qrc:///qml/TabWidget.qml:20:1: Type PageWidget unavailable
qrc:///qml
Not sure if the wiki was transferred btw :
https://github.com/snowshoe/snowshoe/wiki/Build-Instructions
There are some other pages too.
On Mon, Feb 4, 2013 at 5:42 PM, Alexis Menard wrote:
> You need to set your QML_IMPORT_PATH to load the QML plugins of WebKit.
>
> If you didn't install QtWebK
You need to set your QML_IMPORT_PATH to load the QML plugins of WebKit.
If you didn't install QtWebKit then they will not be put on the
default import path so you need to manually point to them. It's the
imports/ directory somewhere in the build dir of QtWebKit.
Hope that helps, I don't have a bu
Snowshoe has been imported, but it doesn't actually run against the dev
branch here:
rich@linux-h33o:~/src/snowshoe> ./snowshoe
qrc:///qml/main.qml:53:5: Type TabWidget unavailable
qrc:///qml/TabWidget.qml:20:1: Type PageWidget unavailable
qrc:///qml/PageWidget.qml:19:1: module "QtWebKit.experimen
On Mon, Feb 4, 2013 at 6:19 AM, Knoll Lars wrote:
> Alan has been very proactive and is probably the best person we have for the
> job right now. So a +1 from my side.
>
> But the declarative repo is pretty big and very central to Qt moving forward.
> So I believe we will need to split up respon
On Feb 4, 2013, at 3:36 PM, Koehne Kai
wrote:
> Hi,
>
> Importing ICU into qtbase is fine with me. Anyhow, I don't particular like
> hard dependency to ICU from Qt5Core, since it forces everyone deploying a
> Windows helloworld to also ship icudt49.dll with 17,5 MB (!).
No, please not. I do
Hi,
Unfortunately problems continues. After first problem was solved it revealed
another one. Investigations are ongoing so please be patient.
Regards,
Simo
From: development-bounces+simo.falt=digia@qt-project.org
[mailto:development-bounces+simo.falt=digia@qt-project.org] On Behalf Of
> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
>> [..]
> > Importing ICU into qtbase is fine with me. Anyhow, I don't particular like
> hard dependency to ICU from Qt5Core, since it forces everyone deploying a
> Windows helloworld to also ship icudt49
On 02/05/2013 12:36 AM, Koehne Kai wrote:
> Hi,
>
> Importing ICU into qtbase is fine with me. Anyhow, I don't particular like
> hard dependency to ICU from Qt5Core, since it forces everyone deploying a
> Windows helloworld to also ship icudt49.dll with 17,5 MB (!).
I hope that no one would depl
Hi,
Importing ICU into qtbase is fine with me. Anyhow, I don't particular like hard
dependency to ICU from Qt5Core, since it forces everyone deploying a Windows
helloworld to also ship icudt49.dll with 17,5 MB (!).
I know that you can still configure with -no-icu. So how about making the usage
On Fri, 01 Feb 2013 20:15:14 +0100
Andre Somers wrote:
> Op 1-2-2013 17:41, Genghis Khan schreef:
> > On Fri, 1 Feb 2013 09:26:24 +
> > Knoll Lars wrote:
> >
> >> On Jan 31, 2013, at 4:13 PM, Genghis Khan
> >> wrote:
> >>
> >>> Hello,
> >>>
> >>> I would like to initiate a new group
> >>> <
Alan has been very proactive and is probably the best person we have for the
job right now. So a +1 from my side.
But the declarative repo is pretty big and very central to Qt moving forward.
So I believe we will need to split up responsibilities further in the longer
term. I would at the minim
On 4.2.2013, at 12.42, Anttila Janne
mailto:janne.antt...@digia.com>>
wrote:
Simo can you add CI for QtSerialPort repository? I think it would be
beneficial have build-only CI already before virtual loopback serial
ports are enabled.
Yep, I will do that.
Simo
_
Laszlo Papp wrote:
> To summarize the automated testing topic.
>
> 1) QtMock will not reach a usable state any soon, unfortunately.
>
> 2) I am not sure which construction of the aforementioned ones would fit
> the operation of the CI machines. Could anyone please comment on that
> with the rel
Hi all
The CI system is suffering from network configuration problems and is not
working currently. The problem has been fixed, but it will take a moment for
every computer to get updated.
Regards
-Tony
Tony Sarajärvi
Senior Software Designer
Digia, Qt
Digia Plc
Elektroniikkatie 10
FI-90590 O
19 matches
Mail list logo
