On Jul 11, 2014, at 6:21 AM, Christian Gagneraud wrote:
> On 11/07/2014 11:22 a.m., Thiago Macieira wrote:
>> On Friday 11 July 2014 10:05:03 Christian Gagneraud wrote:
>>> Boot To Qt for Embedded Linux (Not talking about android here), is based
>>> on Yocto (which is open-source), there exists
On Thursday 10 July 2014 23:53:20 Lisandro Damián Nicanor Pérez Meyer wrote:
> On Thursday 10 July 2014 10:07:56 Thiago Macieira wrote:
> [snip]
>
> > Creator must be able to handle reading from the system log before logging
> > to the system is enabled for that system. On Linux, the code is alrea
On Friday 11 July 2014 07:45:23 Alejandro Exojo wrote:
> It might be even worse if systemd-shim provides that directory. Is it worth
> to try sd_journal_open() and see if it fails? Or check some other way if
> systemd actually launched the application?
No and no.
sd_journal_open might fail beca
El Friday 11 July 2014, Lisandro Damián Nicanor Pérez Meyer escribió:
> AFAIU from this thread, journald support should not be enabled except
> "regular users can read the output". Now what I'm missing here is: if Qt
> is built with journald support, can it be still be used if journald is not
> pr
On 11/07/2014 11:22 a.m., Thiago Macieira wrote:
> On Friday 11 July 2014 10:05:03 Christian Gagneraud wrote:
>> Boot To Qt for Embedded Linux (Not talking about android here), is based
>> on Yocto (which is open-source), there exists a Qt5 layer (Dedicated
>> Yocto sub-project), and I think that D
On Thursday 10 July 2014 10:07:56 Thiago Macieira wrote:
[snip]
> Creator must be able to handle reading from the system log before logging to
> the system is enabled for that system. On Linux, the code is already there,
> so we have to tell distributions *not* to enable journald yet.
AFAIU from t
Hi; I'm trying to better understand what are de limitations of the
bindings when using QObject properties in my QML files, as it seems to
work in a different way depending on the Component used.
Say my app manages several instances of QObject* data items, which
have 3 Q_PROPERTies: text, bool and
On Wed, Jul 9, 2014 at 11:43 PM, Thiago Macieira
wrote:
> == Problematic ==
> Qt 5.3 and dev are currently able to send the output of qDebug, qWarning and
> the rest of the logging framework to somewhere other than stderr. That's done
> on Windows, BlackBerry, Android, and on Linux systems with jo
On Friday 11 July 2014 10:05:03 Christian Gagneraud wrote:
> Boot To Qt for Embedded Linux (Not talking about android here), is based
> on Yocto (which is open-source), there exists a Qt5 layer (Dedicated
> Yocto sub-project), and I think that Digia should be the official
> maintainer of this pr
On Friday 11 July 2014 00:17:48 Alejandro Exojo wrote:
> El Wednesday 09 July 2014, Thiago Macieira escribió:
> > === Log to both ===
> > Aside from the extra overhead, this causes systems that capture both
> > stderr
> > and the system log to record and display the same message twice. That's
> > t
On Friday 11 July 2014 00:27:51 Alejandro Exojo wrote:
> Would it be too problematic to make the environment variable
> (QT_LOGGING_TO_CONSOLE, which already is in use) accept also a "2" for
> logging to both sources?
Problematic, no. It can be easily implemented.
But it's an option we discarde
As you might know Debian has a Hurd port and almost all Qt5 is building there,
except for QtMultimedia.
The problem lies on V4L support. We tested that the rest of the compilation
works by adding a v4l header to the gstreamer test (yes, it's a hammer-like
solution) and thus disabling all gstrea
El Thursday 10 July 2014, Koehne Kai escribió:
> Provide a define QT_LOG_TO_CONSOLE that let QCoreApplication.h record
> whether it should log to console (QT_LOG_TO_CONSOLE=1), to the system
> (QT_LOG_TO_CONSOLE=0), or both (QT_LOG_TO_CONSOLE=2).
Would it be too problematic to make the environme
El Wednesday 09 July 2014, Thiago Macieira escribió:
> === Log to both ===
> Aside from the extra overhead, this causes systems that capture both stderr
> and the system log to record and display the same message twice. That's the
> source of task [3].
>
> This is not an option.
Why not? Task [3]
On 10/07/2014 11:19 p.m., Mitch Curtis wrote:
>
> On 07/10/2014 12:20 PM, Ch'Gans wrote:
>> On 09/07/14 19:53, Andrea Barna wrote:
>>> Hi,
>>>
>>> I am Andrea from Digia Qt, I have recently taken over the Qt
>>> businessin your region.
>> Hi Andrea,
>>
>> All the best for your new position!
>>
>>>
On 10 July 2014 19:17, Thiago Macieira wrote:
> On Thursday 10 July 2014 16:50:22 Shawn Rutledge wrote:
>> What if we use qtlogging.ini (or equivalent on other systems) to
>> control whether the logs go to the system log or not? I agree that
>> every ordinary KDE user doesn't need to have unread
On Thursday 10 July 2014 19:34:59 Oswald Buddenhagen wrote:
> On Thu, Jul 10, 2014 at 10:17:52AM -0700, Thiago Macieira wrote:
> > On Thursday 10 July 2014 16:50:22 Shawn Rutledge wrote:
> > > On Windows I never liked CONFIG += console, because it's never in the
> > > .pro by default (usually not i
On Thu, Jul 10, 2014 at 10:17:52AM -0700, Thiago Macieira wrote:
> On Thursday 10 July 2014 16:50:22 Shawn Rutledge wrote:
> > On Windows I never liked CONFIG += console, because it's never in the
> > .pro by default (usually not in manual tests or examples, and not in
> > Creator-generated pro fil
On Thursday 10 July 2014 07:56:28 Koehne Kai wrote:
> Provide a define QT_LOG_TO_CONSOLE that let QCoreApplication.h record
> whether it should log to console (QT_LOG_TO_CONSOLE=1), to the system
> (QT_LOG_TO_CONSOLE=0), or both (QT_LOG_TO_CONSOLE=2).
>
> Qmake can wrap this into convenience CON
On Thursday 10 July 2014 16:50:22 Shawn Rutledge wrote:
> What if we use qtlogging.ini (or equivalent on other systems) to
> control whether the logs go to the system log or not? I agree that
> every ordinary KDE user doesn't need to have unread logs taking up
> disk space, but maybe developers wo
On Thursday 10 July 2014 11:05:03 Tobias Hunger wrote:
> Hi Thiago,
>
> Basically I agree with your statements, but I do not think we can rely
> on journald at this time.
Agreed.
> The first problem is of course systemd itself: Ubuntu is one of the
> biggest distros out
> there and we can not re
On Thursday 10 July 2014 08:13:09 Koehne Kai wrote:
> > -Original Message-
> > From: development-bounces+kai.koehne=digia@qt-project.org
> > [...]
> > Here's what I propose:
> >
> > Heuristically determine at runtime. On all platforms (including Windows),
> > use only the fact that a t
On Thursday 10 July 2014 07:53:29 Keith Gardner wrote:
> > Currently, the QVersion::compare has an overload to pass a functor that
>
> performs the suffix comparison. Are you suggesting having a "default" in
> the operators that can be overwritten?
No global state, please.
--
Thiago Macieira -
Please do share when you get to the bottom of this.
md
On 7/10/2014 8:55 AM, travik wrote:
> Ok!. That's cool and it is Qml's implementation of VTable, I guess!.
> Thanks a lot again. Let me try it and come back.
>
>
>
> ___
> Development mailing lis
What if we use qtlogging.ini (or equivalent on other systems) to
control whether the logs go to the system log or not? I agree that
every ordinary KDE user doesn't need to have unread logs taking up
disk space, but maybe developers would like to turn on output to the
journal permanently for after-
Hi,
2014-07-10 17:03 GMT+03:00 Zeno Albisser :
> Other than that we had some blog posts earlier this year and we do have a
> wiki page here: http://qt-project.org/wiki/QtWebEngine
> We are currently focusing on getting all the desktop platforms
> (Linux/Mac/Win) up and running.
>
>
http://qt-proj
Hi,
On 03/07/14 13:11, Konstantin Ritt wrote:
Any public documents to read about the Qt WebEngine completeness
state, limitations/know issues, TODOs, and so on?
Sorry for the late reply. We accept bug reports in jira as every other
project or module.
Other than that we had some blog posts ear
Just looking at the topic of that thread, I suggest to name it: QVersionNubmer.
QVersion may suggest some more, like description of the version or provide an
info about different set of features.
From: development-bounces+jaroslaw.kobus=digia@qt-projec
Hi All,
With the current state of QVersion (patchset 35) I see the following issues:
1. operator<() doesn't take the suffix into account (mentioned below)
2. There is no handling of sub version (you cannot differentiate 5.0.0, 5.0 and
5 - they are all equal)
The idea which could resolve these is
On Thu, Jul 10, 2014 at 8:09 AM, Olivier Goffart wrote:
> On Thursday 10 July 2014 07:53:29 Keith Gardner wrote:
> > On Thu, Jul 10, 2014 at 7:31 AM, Olivier Goffart
> wrote:
> > > On Monday 02 June 2014 13:24:55 Richard Moore wrote:
> > > > On 2 June 2014 13:12, Keith Gardner wrote:
> > > > >
On Thursday 10 July 2014 07:53:29 Keith Gardner wrote:
> On Thu, Jul 10, 2014 at 7:31 AM, Olivier Goffart wrote:
> > On Monday 02 June 2014 13:24:55 Richard Moore wrote:
> > > On 2 June 2014 13:12, Keith Gardner wrote:
> > > > On Mon, Jun 2, 2014 at 2:36 AM, Simon Hausmann wrote:
> > > > > I sug
Ok!. That's cool and it is Qml's implementation of VTable, I guess!.
Thanks a lot again. Let me try it and come back.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On Thu, Jul 10, 2014 at 7:31 AM, Olivier Goffart wrote:
> On Monday 02 June 2014 13:24:55 Richard Moore wrote:
> > On 2 June 2014 13:12, Keith Gardner wrote:
> > > On Mon, Jun 2, 2014 at 2:36 AM, Simon Hausmann <
> simon.hausm...@digia.com>
> > >
> > > wrote:
> > >> I suggest a name that is more
On Monday 02 June 2014 13:24:55 Richard Moore wrote:
> On 2 June 2014 13:12, Keith Gardner wrote:
> > On Mon, Jun 2, 2014 at 2:36 AM, Simon Hausmann
> >
> > wrote:
> >> I suggest a name that is more centric towards the _function_ of the
> >> class,
> >> comparison of different software versions.
On Sat, May 31, 2014 at 2:00 PM, Thiago Macieira
wrote:
> Em sex 09 maio 2014, às 11:36:08, Keith Gardner escreveu:
> > I have been working on adding a class to QtCore (QVersion) to support
> > storing version numbers, convert to/from QString, and having comparison
> > operators. My goal was to
On Wednesday 09 July 2014 21:02:32 .. ink .. wrote:
> greetings and hope its acceptable to post what i am about to post here and
> apologies if it is not.
>
> Through my usage of Qt/C++, i came about a nicer way to run a simple tasks
> asynchronously while
> living within Qt and i decided to share
On 07/10/2014 12:20 PM, Ch'Gans wrote:
> On 09/07/14 19:53, Andrea Barna wrote:
>> Hi,
>>
>> I am Andrea from Digia Qt, I have recently taken over the Qt
>> businessin your region.
> Hi Andrea,
>
> All the best for your new position!
>
>> I noticed that you downloaded the trial version of Qt last
On 09/07/14 19:53, Andrea Barna wrote:
> Hi,
>
> I am Andrea from Digia Qt, I have recently taken over the Qt
> businessin your region.
Hi Andrea,
All the best for your new position!
> I noticed that you downloaded the trial version of Qt last year and
> Iwas wondering whether the evaluation wen
Hi,
When running Qt-5 on top of the directfb qpa plugin, some benchmarks are
quite slow.
(http://smashcat.org/av/canvas_test)
I've found that the 2D painting ops are going through the
QBlitterPaintEngine class
that is inheriting the QRasterPaintEngine class, which is doing all the
painting via
Hi Thiago,
Basically I agree with your statements, but I do not think we can rely
on journald
at this time.
The first problem is of course systemd itself: Ubuntu is one of the
biggest distros out
there and we can not reasonably assume that to be running systemd
before 14.04 is
at the end of its l
Perhaps, it makes sense to select an output message sink in runtime?
E.g. before QCoreApplication, by means of specify some QLogging flags, to
override the installMessageHandler and so on?
Maybe make sense to introduce a some pre-defined qInstallMessageHandler's()
or something others functions, li
> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
> [...]
> Here's what I propose:
>
> Heuristically determine at runtime. On all platforms (including Windows), use
> only the fact that a terminal is present. If a terminal is present, write to
> it
> u
Sorry for my vague statements :)
Actually I wasn't talking about logging to file as a default for
Windows. On the contrary I think this has to be done by each
application individually -- someone needs as you rightly say 10 lines
of code just to make sure everything went okay, others need a large
l
> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
> [mailto:development-bounces+kai.koehne=digia@qt-project.org] On
> Behalf Of Thiago Macieira
> Sent: Wednesday, July 09, 2014 11:44 PM
> To: development@qt-project.org
> Subject: [Development] Cake a
44 matches
Mail list logo