> Thiago Macieira kirjoitti 8.5.2015 kello 22.33:
>
>> On Friday 08 May 2015 16:10:27 Hausmann Simon wrote:
>> Hi,
>>
>> Compilation wise I agree, it's low effort. But the situation is different in
>> Jira IMO.
>
> Can we declare the module in Deprecated state and keep bug compatibility with
On Friday May 08 2015 12:31:10 Thiago Macieira wrote:
> On Friday 08 May 2015 18:46:51 René J.V. Bertin wrote:
> > Pushing to ssh://codereview.qt-project.org/qt/qtbase
>
> Wrong port. You need to use port 29418.
>
> Unless your ~/.ssh/config has that setting for you.
Host codereview.qt-project.
On Friday 08 May 2015 16:10:27 Hausmann Simon wrote:
> Hi,
>
> Compilation wise I agree, it's low effort. But the situation is different in
> Jira IMO.
Can we declare the module in Deprecated state and keep bug compatibility with
previous versions? If people are using it to transition from Qt 4,
On Friday 08 May 2015 18:46:51 René J.V. Bertin wrote:
> Pushing to ssh://codereview.qt-project.org/qt/qtbase
Wrong port. You need to use port 29418.
Unless your ~/.ssh/config has that setting for you.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source T
For the specific case of QtQuick1, I'd say that closing any issues that
aren't applicable to QtQuick2 (or won't be done) with a useful message
explaining the situation makes sense. It might also make sense to close
reporting of new issues for that component.
On Fri, May 8, 2015, at 06:10 PM, Hausm
Hi,
On Fri, May 8, 2015, at 02:39 PM, Frederik Gladhorn wrote:
> One question is if there is any reason to maintain Qt Quick 1 in the
> future.
I know of some projects that are still out there using QtQuick1
(unfortunately). I think that moving to remove it now might be a little
too quick, altho
On Friday May 08 2015 19:30:03 Oswald Buddenhagen wrote:
> On Fri, May 08, 2015 at 06:46:51PM +0200, René J.V. Bertin wrote:
> > On Friday May 08 2015 09:05:58 Thiago Macieira wrote:
> >
> > > Can you try pushing over SSH instead of HTTPS?
> >
> > I use https because it seems to be more reliable
On Fri, May 08, 2015 at 06:46:51PM +0200, René J.V. Bertin wrote:
> On Friday May 08 2015 09:05:58 Thiago Macieira wrote:
>
> > Can you try pushing over SSH instead of HTTPS?
>
> I use https because it seems to be more reliable to me, but:
>
> %> ../qtrepotools-git/bin/git-gpush -v
> Pushing HEA
Hi,
If the public API would allow you to implement what the folks at KDAB did at
http://www.kdab.com/creating-pdf-qtquick-2-scene-slideviewer/ , would that
help your use case?
Simon
Original Message
From: André Somers
Sent: Friday, May 8, 2015 14:45
To: development@qt-project.org
Subject:
On Friday May 08 2015 09:05:58 Thiago Macieira wrote:
> Can you try pushing over SSH instead of HTTPS?
I use https because it seems to be more reliable to me, but:
%> ../qtrepotools-git/bin/git-gpush -v
Pushing HEAD for 5.5 on gerrit ...
Pushing to ssh://codereview.qt-project.org/qt/qtbase
X11 f
Hi,
Compilation wise I agree, it's low effort. But the situation is different in
Jira IMO.
Simon
Original Message
From: Thiago Macieira
Sent: Friday, May 8, 2015 17:37
To: development@qt-project.org
Subject: Re: [Development] Future of Qt Quick 1 in Qt 5
On Friday 08 May 2015 14:39:38 Fred
On Friday 08 May 2015 18:00:27 René J.V. Bertin wrote:
> %>../qtrepotools-git/bin/git-gpush -v 5.4.2:
> Pushing 5.4.2 for 5.4.2 on gerrit ...
> Pushing to https://codereview.qt-project.org/p/qt/qtbase
> Username for 'https://codereview.qt-project.org': rjvbertin
> Password for 'https://rjvber...@co
Hello,
I tried to push a patch to gerrit for review, and got this:
%> ../qtrepotools-git/bin/git-gpush -v
Pushing HEAD for 5.5 on gerrit ...
Pushing to https://codereview.qt-project.org/p/qt/qtbase
Username for 'https://codereview.qt-project.org': rjvbertin
Password for 'https://rjvber...@coderev
On Friday 08 May 2015 14:39:38 Frederik Gladhorn wrote:
> Since KDE moved over the Plasma desktop to Qt Quick 2 (on which I'm writing
> this email), I feel confident that the time has come to move everyone over.
> For the no opengl acceleration use case, we provide the Qt Quick 2D Renderer
> as bac
Yes, Luke said in irc he will do a release of speech-dispatcher 0.8.3
this month.
I would definitely like to see QtSpeech in Qt 5.6. I do have a couple
of concerns, but they should be fixable.
1. The tests use timers to check functionality. This seems to be
broken in some cases and not reliable. I
On Friday, May 08, 2015 04:04:46 PM André Somers wrote:
> Albert Astals Cid schreef op 8-5-2015 om 15:58:
> > On Fri, May 8, 2015 at 3:53 PM, Frederik Gladhorn
> >
> > wrote:
> >> Absolutely. But you can migrate to Qt 5.5 which has Qt Quick 1 support
> >> and
> >> later to 5.6 and onwards.
> >
>
On Fri, May 8, 2015 at 9:39 AM, Frederik Gladhorn <
frederik.gladh...@theqtcompany.com> wrote:
>
> Since KDE moved over the Plasma desktop to Qt Quick 2 (on which I'm writing
> this email), I feel confident that the time has come to move everyone over.
> For the no opengl acceleration use case, we
Albert Astals Cid schreef op 8-5-2015 om 15:58:
> On Fri, May 8, 2015 at 3:53 PM, Frederik Gladhorn
> wrote:
>>
>> Absolutely. But you can migrate to Qt 5.5 which has Qt Quick 1 support and
>> later to 5.6 and onwards.
> Not if you're using the Qt that comes with your Linux distribution
> (not sur
On Fri, May 8, 2015 at 3:53 PM, Frederik Gladhorn
wrote:
> On Friday, May 08, 2015 02:44:53 PM André Somers wrote:
>> Frederik Gladhorn schreef op 8-5-2015 om 14:39:
>> > Hi,
>> >
>> > I think the dust has settled quite a bit and the declarative module is
>> > becoming better by the day. We have s
On Friday, May 08, 2015 02:44:53 PM André Somers wrote:
> Frederik Gladhorn schreef op 8-5-2015 om 14:39:
> > Hi,
> >
> > I think the dust has settled quite a bit and the declarative module is
> > becoming better by the day. We have seen it evolve and the new Java Script
> > engine is running smoo
On Friday, May 08, 2015 10:41:04 AM Lisandro Damián Nicanor Pérez Meyer wrote:
> On Friday 08 May 2015 14:59:22 Frederik Gladhorn wrote:
> > Hello,
> >
> > I'd like to propose inclusion of QtSpeech in Qt 5.6.
> >
> > Currently the module implements text to speech on Lin/Win/OS X/Android and
> > t
On Friday 08 May 2015 14:59:22 Frederik Gladhorn wrote:
> Hello,
>
> I'd like to propose inclusion of QtSpeech in Qt 5.6.
>
> Currently the module implements text to speech on Lin/Win/OS X/Android and
> there is a patch for iOS which needs to be re-done but works as proof of
> concept.
> My only
Hi,
Qt 4.8.7 release candidate 2 packages are available at
http://download.qt.io/development_releases/qt/4.8/4.8.7-rc2/ and SHA-1 is
frozen so please test these packages accordingly.
These packages are built against SHA-1:
445d29dbb8135944ff3a9283b7622de75d68e747 * Add Missing Debug Operator
Hello,
I'd like to propose inclusion of QtSpeech in Qt 5.6.
Currently the module implements text to speech on Lin/Win/OS X/Android and
there is a patch for iOS which needs to be re-done but works as proof of
concept.
My only concern is currently the license of speech-dispatcher which is at the
On 8 mai 2015, at 14:32, Frederik Gladhorn
wrote:
> Hello all,
>
> I’ve just looked a bit at the QtXmlPatterns module. The module has a few
> issues and is not actively maintained. I wonder if it should see improvements
> or if there are good alternatives which might be more spec compliant wh
Frederik Gladhorn schreef op 8-5-2015 om 14:32:
> Hello all,
>
> I’ve just looked a bit at the QtXmlPatterns module. The module has a few
> issues and is not actively maintained. I wonder if it should see improvements
> or if there are good alternatives which might be more spec compliant which
> pe
Frederik Gladhorn schreef op 8-5-2015 om 14:39:
> Hi,
>
> I think the dust has settled quite a bit and the declarative module is
> becoming better by the day. We have seen it evolve and the new Java Script
> engine is running smoothly (and actively worked on, sadly it will have one
> known crasher
Hi,
I think the dust has settled quite a bit and the declarative module is
becoming better by the day. We have seen it evolve and the new Java Script
engine is running smoothly (and actively worked on, sadly it will have one
known crasher in the 5.5 beta release which has been fixed in the mean
Hello all,
I’ve just looked a bit at the QtXmlPatterns module. The module has a few
issues and is not actively maintained. I wonder if it should see improvements
or if there are good alternatives which might be more spec compliant which
people end up using. One option in the long term might be
29 matches
Mail list logo
