Hi
We will update Jenkins to hopefully a more stable version. We have tried it
already on dev side and the update process went fine.
The update will happen after the current qt5 release integration build, which
will occur around noon, i.e. in 3 hours or so.
Cheers,
-Tony
Tony Sarajärvi
CI
Thiago Macieira wrote:
Em qua 23 abr 2014, às 16:50:45, Andrey Ponomarenko escreveu:
I've created the ABI compatibility report between 5.2.1 and 5.3.0-beta
versions:
http://upstream-tracker.org/compat_reports/qt/5.2.1_to_5.3.0-beta/abi_compat
_report.html
Thanks Andrey! I'll take a look at
Hi
We will update Jenkins to hopefully a more stable version. We have tried it
already on dev side and the update process went fine.
The update will happen after the current qt5 release integration build, which
will occur around noon, i.e. in 3 hours or so.
We already began the update
On Monday 21. April 2014 10.41.52 Christoph Feck wrote:
On Monday 21 April 2014 05:27:33 Joshua Kolden wrote:
I’m curious why you are not interested in QML.
[...]
I see no reason to stay with Qt Widgets at all other than legacy
application support. So what is your concern?
[...]
Not
On 2014-04-23, Andrey Ponomarenko aponomare...@rosalab.ru wrote:
I've created the ABI compatibility report between 5.2.1 and 5.3.0-beta
versions:
http://upstream-tracker.org/compat_reports/qt/5.2.1_to_5.3.0-beta/abi_compat_report.html
Hope it may be helpful to analyse changes in headers.
Sune Vuorela wrote:
On 2014-04-23, Andrey Ponomarenko aponomare...@rosalab.ru wrote:
I've created the ABI compatibility report between 5.2.1 and 5.3.0-beta
versions:
http://upstream-tracker.org/compat_reports/qt/5.2.1_to_5.3.0-beta/abi_compat_report.html
Hope it may be helpful to analyse
Hi list,
we discussed the topic whether non-QObject types can be used in QML or not
several times. The last time is only a few days ago as part of the Qt
future discussions. So I had some thoughts what needs to happen to solve
this issue.
I can remember someone told me there are plans to add
On Thursday 24. April 2014 11.55.07 Roland Winklmeier wrote:
Hi list,
we discussed the topic whether non-QObject types can be used in QML or not
several times. The last time is only a few days ago as part of the Qt
future discussions. So I had some thoughts what needs to happen to solve
On Thu, Apr 24, 2014 at 09:47:50AM +0200, Simon Hausmann wrote:
Let's turn this from a blame game into something more productive.
I will simply assume this includes the readiness to re-consider some
of the non-technical decisions of the past.
The nature of the beast is that we do have two
I’m sorry I intended to respond to this in the other thread, but super busy.
Nevertheless I think it’s important for people to know there are answers to
this now without waiting for any new APIs so I stole the time to write our
process out.
We have a solution that works very well for us using
On 24 Apr 2014, at 00:57, Alex Montgomery
apmontgom...@gmail.commailto:apmontgom...@gmail.com wrote:
Hello,
While trying to style a ComboBox such that its text didn't elide and it didn't
have inexplicably large margins, I was surprised to learn that these two items
would be displayed
On Thursday 24. April 2014 14.08.03 André Pönitz wrote:
On Thu, Apr 24, 2014 at 09:47:50AM +0200, Simon Hausmann wrote:
Let's turn this from a blame game into something more productive.
I will simply assume this includes the readiness to re-consider some
of the non-technical decisions of
I edited and updated the controls related change log here:
https://codereview.qt-project.org/#change,84066
On a somewhat related note, I would suggest that for future updates we
standardize on putting the bug-id after each item entry rather than in front
as that would make the document a bit
On Tuesday 22 April 2014 23:11:59 Kleint Friedemann wrote:
Hi Christoph,
Christoph Feck wrote: Not speaking for Michael, but let me add
that C++ is much easier to debug compared to QML, if you get a
crash. We have nearly hundred backtraces in the Plasma bug
tracker that point back to
Em qui 24 abr 2014, às 16:25:41, Bache-Wiig Jens escreveu:
On a somewhat related note, I would suggest that for future updates we
standardize on putting the bug-id after each item entry rather than in front
as that would make the document a bit more readable in my opinion. I don’t
really see
Hi Marius,
On 23 April 2014 23:07, cincirin cinci...@gmail.com wrote:
On 4/23/2014 5:50 PM, Sze Howe Koh wrote:
With QML, the general idea is to use QML for the GUI and use C++ for core
logic.
Well from I understand QML is used in a lot of other aspects than GUI: Qt
WebKit 2 is QML ( only
On 24 April 2014 00:35, André Pönitz apoen...@t-online.de wrote:
On Wed, Apr 23, 2014 at 10:50:23PM +0800, Sze Howe Koh wrote:
QML is a declarative language
Are you considering sequences of JavaScript statements, especially control
flow statements, as declarative?
Andre'
Of course not. :-)
On 25 April 2014 10:20, Sze Howe Koh szehowe@gmail.com wrote:
On 23 April 2014 23:07, cincirin cinci...@gmail.com wrote:
Well from I understand QML is used in a lot of other aspects than GUI: Qt
WebKit 2 is QML ( only ? ), also QML is used in multimedia, position modules
and so on ...
Hi all,
I've been tracking QDoc errors in an Excel spreadsheet. It takes some
manual labour to convert the QDoc output into spreadsheet form, and
copy my existing notes into a new build.
So, in true hacker spirit, I made a tool to automate all that for me.
I've polished the code and published it
Cristian Pallarés te ha dejado un mensaje
Este mensaje es personal. Solo tú y su remitente tenéis acceso a él y te
recordamos que lo puedes eliminar en cualquier momento. Si quieres responder
puedes hacerlo desde el chat. Para leer tu mensaje, haz clic en el siguiente
enlace:
20 matches
Mail list logo
