On 05/02/15 09:31, Bo Thorsen b...@vikingsoft.eu wrote:
Den 04-02-2015 kl. 15:56 skrev Olivier Goffart:
On Wednesday 04 February 2015 09:23:12 Knoll Lars wrote:
On 04/02/15 10:20, Olivier Goffart oliv...@woboq.com wrote:
Also, is it not time to decide which platform are we going to stop
+1 for dropping VS2008. For those with thin wallets it's easier to
upgrade nowadays anyway to the VS2013 Community Edition.
/Rgrds Henry
On 2015-02-05 08:31, Bo Thorsen wrote:
Den 04-02-2015 kl. 15:56 skrev Olivier Goffart:
On Wednesday 04 February 2015 09:23:12 Knoll Lars wrote:
On 04/02/15
Hello,
please keep in mind that in the enterprise environment Windows CE /
Windows Embedded Compact is still an important platform!
Kind regards,
Nico Wallmeier
+1 for dropping VS2008. For those with thin wallets it's easier to
upgrade nowadays anyway to the VS2013 Community Edition.
On Thursday 5. February 2015 23.08.03 Jaroslaw Staniek wrote:
On 5 February 2015 at 16:44, Simon Hausmann
simon.hausm...@theqtcompany.com wrote:
On Thursday 5. February 2015 16.32.08 Jaroslaw Staniek wrote:
On 3 February 2015 at 09:50, Hausmann Simon
simon.hausm...@theqtcompany.com
Knoll Lars schreef op 5-2-2015 om 16:28:
But we don’t have much of a choice, if we want to deliver an up to date
web engine.
Perhaps it is time to ask the question then: do we want to do that? Do
we really need to?
It seems to me, that it isn't really possible to do. Not in a way that
doesn't
Did something like that happen before? Sounds strange to me to ship only parts
of a framework.
I imagine that this would also be a support nightmare... Qt5 is installed, but
some other packages
don't work or are not installable because they have a dependency to
QtWebEngine. In a way it
Hi all,
I wonder if you can help me for something. An easy thing to do in QML which
is not working for me...
I have a ColumnLayout an inside it, a RowLayout and a Repeater (within
another RowLayout).
It looks like this:
ColumnLayout
{
RowLayout {}
ColumnLayout {
Knoll Lars wrote:
But we don’t really have a choice, as there is no upstream for Qt WebKit
anymore. This implies that we’d have to fully develop that fork on our own
to support is. That in turn requires a team far larger than what we have.
So it’s simply not doable.
The thing is, QtWebEngine
On 05/02/15 15:19, Kevin Kofler kevin.kof...@chello.at wrote:
Knoll Lars wrote:
But we don’t really have a choice, as there is no upstream for Qt WebKit
anymore. This implies that we’d have to fully develop that fork on our
own
to support is. That in turn requires a team far larger than what
On 3 February 2015 at 09:50, Hausmann Simon
simon.hausm...@theqtcompany.com wrote:
Hi,
Functionality wise, what type of class do you wrap with QScriptClass?
Examples (you can guess from what project by looking at my footer):
- Light data types (anything you see in databases and isn't mapping
Knoll Lars wrote:
Yes, and I am sure, they have huge issues keeping up with the development
of competing web technologies. I’ve been there and done that with first
KHTML, then Qt WebKit for many years. The fact is that HTML5 these days is
a huge pig, and supporting all of it using WebKit and
On Thursday 05 February 2015 08:48:20 Knoll Lars wrote:
Yes, it’s not possible to drop 2008 currently without dropping Windows
Embedded support. So not something we can do until we have a solution for
Windows Embedded.
Microsoft will not add support to an old Windows Embedded to a new VS. The
On Thursday 22. January 2015 06.52.56 Blasche Alexander wrote:
I'd like to nominate Timur Pocheptsov for approver status.
+1 from me too :)
- Paul
___
Development mailing list
Development@qt-project.org
On Thursday 5. February 2015 16.32.08 Jaroslaw Staniek wrote:
On 3 February 2015 at 09:50, Hausmann Simon
simon.hausm...@theqtcompany.com wrote:
Hi,
Functionality wise, what type of class do you wrap with QScriptClass?
Examples (you can guess from what project by looking at my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 04.02.2015 um 16:51 schrieb Cristian Adam:
On 04.02.2015 10:23, Knoll Lars wrote:
In principle I agree. The problem with 2008 is that this is
currently the only compiler supporting Windows Embedded 7, so we
can’t easily get rid of it. Dropping
On Thursday 05 February 2015 15:55:52 Lisandro Damián Nicanor Pérez Meyer
wrote:
- Using V8 means we need to drop support for arm64 (aka AArch64), powerpc,
powerpc64 and s390x. I understand this *might* be a minor side effect for
the Qt project, but still important for us.
I'm pretty sure
This would be the same as dropping the Windows Embedded Compact support.
So its a clear no from my side.
--
Björn Breitmeyer | bjoern.breitme...@kdab.com | Software Engineer
KDAB (Deutschland) GmbHCo KG, a KDAB Group company
Germany: +49-30-521325470, Sweden (HQ): +46-563-540090
KDAB - Qt
Yes, it’s not possible to drop 2008 currently without dropping Windows
Embedded support. So not something we can do until we have a solution for
Windows Embedded.
Cheers,
Lars
On 05/02/15 09:32, Björn Breitmeyer bjoern.breitme...@kdab.com wrote:
This would be the same as dropping the Windows
Hi all,
We have new snapshot available in
Windows: http://download.qt.io/snapshots/qt/5.4/5.4.1/2015-02-05_107/
(http://download.qt.io/snapshots/qt/5.4/5.4.1/2015-02-05_108 coming with same
content but hopefully with all installers)
Linux:
On 5 February 2015 at 16:44, Simon Hausmann
simon.hausm...@theqtcompany.com wrote:
On Thursday 5. February 2015 16.32.08 Jaroslaw Staniek wrote:
On 3 February 2015 at 09:50, Hausmann Simon
simon.hausm...@theqtcompany.com wrote:
Hi,
Functionality wise, what type of class do you wrap with
Hello,
Certificate is not yet repaired... 10 days?
Can you imagine the trouble for someone who choosed to rely on ministro
to deploy a commercial app?
[mode=upsetMood]
Possibly it might happen again anytime and we just have to live with it?
Someone takes care it won't happen again?
[/mode]
Anyone?
On Tue, Feb 3, 2015 at 2:32 PM, Mandeep Sandhu
mandeepsandhu@gmail.com wrote:
Hi All,
Sometime back I implemented a feature in QtNetwork -
QNetworkAccessManager: Support HTTP redirection.
https://codereview.qt-project.org/#/c/83058/
This review request has been pending in
On Thursday 05 February 2015 21:39:16 Allan Sandfeld Jensen wrote:
[snip]
[0] https://www.debian.org/security/2015/dsa-3148
It would have been the same problem with WebKit. Neither Google nor Apple
cares about supporting any build environment more than 1-2 years old. When
we still was part
On Friday 06 February 2015, Lisandro Damián Nicanor Pérez Meyer wrote:
On Thursday 05 February 2015 21:39:16 Allan Sandfeld Jensen wrote:
[snip]
[0] https://www.debian.org/security/2015/dsa-3148
It would have been the same problem with WebKit. Neither Google nor Apple
cares about
On Thursday 05 February 2015 14:33:13 Rutledge Shawn wrote:
[snip]
I agree. For every kind of documentation in every app which has a help
system, and in other use cases where people use real web browsers without
needing all the features, it would be great to have a lightweight
alternative
On Thursday 05 February 2015 09:55:33 Andreas Holzammer wrote:
Am 04.02.2015 um 16:51 schrieb Cristian Adam:
On 04.02.2015 10:23, Knoll Lars wrote:
In principle I agree. The problem with 2008 is that this is
currently the only compiler supporting Windows Embedded 7, so we
can’t easily get
On Thursday 05 February 2015 11:07:29 Koehne Kai wrote:
-Original Message-
From: development-bounces+kai.koehne=theqtcompany.com@qt-
project.org [mailto:development-
bounces+kai.koehne=theqtcompany@qt-project.org] On Behalf Of
Thiago Macieira
Sent: Tuesday, February 03,
On Friday 06 February 2015 01:19:17 Allan Sandfeld Jensen wrote:
On Friday 06 February 2015, Lisandro Damián Nicanor Pérez Meyer wrote:
On Friday 06 February 2015 00:15:48 you wrote:
About QtWebEngine, do you know what system libraries you have problems
with it duplicating? I think we can
(Resending as I replied to Allan in private by mistake))
On Friday 06 February 2015 00:15:48 you wrote:
[snip]
But at least there we could just disable JIT, which is what we did. When
we
had V8 around (if I remember correctly it was used for QML, but my memory
might be failing me) we
On Tuesday 03 February 2015 11:59:11 André Somers wrote:
Knoll Lars schreef op 3-2-2015 om 10:51:
So Qt 5.6 can drop mingw support?
There are currently no plans in dropping mingw. But webengine is currently
not supported on that compiler.
So I guess that does mean that it will no longer
On Wednesday 04 Feb 2015 16:15:09 Federico J. Fernández wrote:
Then,
What is the latest Qt version that I can use to compile Qt3D?
You need to build qtbase, qtsvg, qtimageformats, qtxmlpatterns and qt3d from
the dev branch in git.
Cheers,
Sean
Thanks.
--
fede
On Fri, Jan 23,
-Original Message-
From: development-bounces+kai.koehne=theqtcompany.com@qt-
project.org [mailto:development-
bounces+kai.koehne=theqtcompany@qt-project.org] On Behalf Of
Thiago Macieira
Sent: Tuesday, February 03, 2015 6:18 PM
To: development@qt-project.org
Subject: Re:
I'll try to summarize my POV on this issue in this mail:
- I agree with Lars that HTML5 is a huge pig ;)
- Bundling so many stuff in that package is definitely a non go for Debian.
- I do also understand they require a competitive product. But on the same
line I do also think the level of
Am 05.02.2015 um 17:13 schrieb Thiago Macieira:
On Thursday 05 February 2015 09:55:33 Andreas Holzammer wrote:
Am 04.02.2015 um 16:51 schrieb Cristian Adam:
On 04.02.2015 10:23, Knoll Lars wrote:
In principle I agree. The problem with 2008 is that this is
currently the only compiler
On Thursday 05 February 2015, Lisandro Damián Nicanor Pérez Meyer wrote:
I'll try to summarize my POV on this issue in this mail:
- I agree with Lars that HTML5 is a huge pig ;)
- Bundling so many stuff in that package is definitely a non go for Debian.
- I do also understand they
35 matches
Mail list logo
