Re: [Interest] Medical device companies using Qt

2022-10-29 Thread ich



Am 29. Oktober 2022 18:38:35 UTC schrieb Stan Morris :
>I cannot get that time back.

"sad but true"
(Metallica, James Hetfield, Lars Ulrich)
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] "Activate your 10-day Qt 6 evaluation now"

2021-08-30 Thread ich
Am 30. August 2021 11:22:52 UTC schrieb Nuno Santos :
>Hi,
>
>What do you do with a 10 days evaluation of Qt 6?
>
>I would say that taking into account the fact that Qt has a new building 
>system and qmake is not available anymore, porting an existing project takes 
>much more than 10 days.
>
>Any feedback from users that have already tried Qt 6 and are porting their 
>apps to it?
>
>Best regards,
>
>Nuno
>
>
>___
>Interest mailing list
>Interest@qt-project.org
>https://lists.qt-project.org/listinfo/interest

I'd like to rephrase:
Why not, in which cases, use lgpl license?

Alex
-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] Learning solutions survey

2021-06-17 Thread ich
Am June 17, 2021 6:48:07 AM UTC schrieb Tino Pyssysalo :
>The EDU license is targeted at instructor-led classroom teaching rather
>than scientific research work. 
>In the latter case, open-source license is working better or even
>commercial one, if the work 
>will result to a commercial product. 
>--
>Tino
>
>
>> On 16.6.2021, 23.33, "Interest on behalf of Bernhard Lindner"
>priv...@bernhard-lindner.de> wrote:
>>
>> Never heard about that license. I was very interested until I
>read the FAQ:
>>
>> "Under the educational license, limitations apply. Applications
>and/or devices may not be
>> distributed to third parties and must be used for internal use
>only. Subcontracting in any
>> direction is not allowed under this license. Professional support
>of Qt is not included
>> either."
>>
>> This means that as soon as the students use the software in the
>practical part of their
>>studies and have to publish the software as part of their
>scientific work or as part of
>> their degree, they are forced to go back to the OSS license.
>That's ridiculous. For me,
>> that means avoiding Qt altogether in our curriculum or, if at
>all, relying exclusively on
>> the OSS license.
>> It seems like there is an internal company rule that requires all
>license terms to be
>> written in such a way that licensees are annoyed under all
>circumstances. 
>
>
>
>___
>Interest mailing list
>Interest@qt-project.org
>https://lists.qt-project.org/listinfo/interest

No need to go with commercial license when doing commercial product...
-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] QStringBuilder buffer overflow with string litteral?

2021-01-25 Thread ich
Am January 25, 2021 2:47:28 PM UTC schrieb "Olivier B." 
:
>Oh, you are right, thanks. I thought the + operator was on a QString
>and
>adding a char would be faster than adding a 1-char string, but it just
>changed the char* pointer address instead.
>
>Le lun. 25 janv. 2021 à 15:32, Giuseppe D'Angelo via Interest <
>interest@qt-project.org> a écrit :
>
>> Hi,
>>
>> Il 25/01/21 13:56, Olivier B. ha scritto:
>> >  fields += (fields.isEmpty() ? "" : ", ") + '"' + field +
>'"';
>>
>> QStringBuilder usage is a red herring, pay close attention at what
>> you're doing in the first +: you're summing a const char * (result of
>> the ternary operator) with a char; that does not do string
>concatenation...
>>
>> > Passing one/both of the operands of the ternary operator as
>QStrings
>> makes the problem disappear.
>>
>> That however kills the advantage of QStringBuilder. Use QStringView /
>> QLatin1String instead.
>>
>> Tip: always define QT_NO_CAST_FROM_ASCII (or the more lenient
>> QT_RESTRICTED_CAST_FROM_ASCII) in any Qt project.
>>
>> HTH,
>> --
>> Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software
>Engineer
>> KDAB (France) S.A.S., a KDAB Group company
>> Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
>> KDAB - The Qt, C++ and OpenGL Experts
>>
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> https://lists.qt-project.org/listinfo/interest
>>

we're coming closer to Bobby Tables;' now xD
-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] QStringBuilder buffer overflow with string litteral?

2021-01-25 Thread ich
Am January 25, 2021 12:56:45 PM UTC schrieb "Olivier B." 
:
>Compiling with QT 5.11.1 &  QT_USE_QSTRINGBUILDER, i get an error with
>the
>following code block:
>
>  QString generateQuery(const QString& tableName, const QStringList&
>columns, int count)
>  {
>QString fields = "*";
>if (!columns.isEmpty())
>{
>  fields.clear();
>  for (const QString& field : columns)
>  {
>fields += (fields.isEmpty() ? "" : ", ") + '"' + field + '"';
>  }
>}
>...
>
>I just want to build a comma separated list of the items in 'columns',
>surrounded by quotes.
>But instead of giving "A", "B", "C", this gives UNIQUE (%1)"A"UNIQUE
>(%1)"B"UNIQUE (%1)"C"
>
>That UNIQUE (%1) is only found in another cpp file of the same DLL
>project,
>in strings ", UNIQUE (%1)" passed to QString constructors. So not only
>is
>it using the wrong string litteral, it does not read it from the string
>start.
>
>Passing one/both of the operands of the ternary operator as QStrings
>makes
>the problem disappear.
>
>Are there things i should be aware of when using QStringBuilder, such
>as
>'do not put expressions on operators, because of macros that will
>evaluate
>them multiple times', or something like that?
>String pooling (/GF of visual studio) is not used, if that matters

https://xkcd.com/327/

Greetings;)
Alex
-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] qml: opengl failure

2021-01-06 Thread ich
Am January 6, 2021 5:54:02 AM UTC schrieb Alexander Dyagilev 
:
>Hello,
>
>I've tried to use this code:
>
>if(!qEnvironmentVariableIsSet("QT_OPENGL"))
>
>{
>
>//OnWindows,useANGLEsowedon'thavetoloadOpenGL
>
>//user-modedriversintoourapp.OGLdrivers(especiallyIntel)
>
>//seemtocrashtheappfarmoreoftenthanDirectX.
>
>qputenv("QT_OPENGL","angle");
>
>}
>
>It works fine in Windows 10. But in Windows 7 I'm getting the following
>
>message:
>
>libEGL.dll, libGLESV2.dll, d3dcompiler_47.dll does exist inside of our 
>app's directory.
>
>Why is this happening?

Hi,

i've no idea about the explicit issue, but to check the top most errors:
You have all this libs, including dependencies?
Have you checked them e.g. dependency walker, for loading issues?

Alex
-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] Converting QStrings to const char *

2020-07-21 Thread ich
Pay attention:

::toUtf8() returns a QBytearray. After your complete call, the constData() is 
invalid.
You must copy the pointer before the QBytearray gets out of scope.


Am July 21, 2020 4:58:54 PM UTC schrieb Doogster :
>My program uses both Qt and a C API that takes, as parameters, UTF-8
>const char * strings.
>
>Is this the correct way to convert a QString containing a UTF8 string
>to that format?
>
>qString.toUtf8().constData()
>___
>Interest mailing list
>Interest@qt-project.org
>https://lists.qt-project.org/listinfo/interest

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] List on moderation

2020-07-16 Thread ich
+1

Am July 16, 2020 11:49:26 AM UTC schrieb Christian Gagneraud :
>On Thu, 16 Jul 2020, 23:28 Cristián Maureira-Fredes, <
>cristian.maureira-fre...@qt.io> wrote:
>
>>
>> Mails on uncontroversial topics will be let through,
>> but please understand that moderation will induce some delay.
>>
>
>Is there an uncontroversial definition of 'controversial topic'? Has it
>been breached recently?
>
>I am no trying to defend anyone here, but this decision looks like
>censorship to me.
>
>There are alternatives to silence some one if you don't like the topics
>brought forward (eg. Filter: to, from or cc contains xyz)
>
>If the recent events haven't breached the code of conduct that was
>reminded
>to us all, please lift this unilaterally taken decision that imped the
>whole community.
>
>Chris
>
>Ps: I usually don't read emails from xyz fully, but every now and then,
>I
>like the critical approach, I just wish that these emails were straight
>to
>the point.
>
>
>
>> Cheers
>>
>>
>> --
>> Dr. Cristian Maureira-Fredes
>> R Manager
>>
>> The Qt Company GmbH
>> Erich-Thilo-Str. 10
>> D-12489 Berlin
>>
>> Geschäftsführer: Mika Pälsi,
>> Juha Varelius, Mika Harjuaho
>> Sitz der Gesellschaft: Berlin,
>> Registergericht: Amtsgericht
>> Charlottenburg, HRB 144331 B
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> https://lists.qt-project.org/listinfo/interest
>>

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] Fwd: vs. Flutter

2019-02-21 Thread ich
Well, this was my question here.
What makes you think, you violate the LGPL in this case?

>You *cannot* publish (for free or at a cost) Qt based proprietary SW
>on Google play store w/o a Qt license. It would violate the LGPL. The
>Qt license is a (costly) LGPL substitute.

>
>Chris
>
>
>
>>
>> /René
>>
>>
>> On Thu, 21 Feb 2019 at 14:50 Sylvain Pointeau
> wrote:
>>>
>>> On Tue, Feb 19, 2019 at 8:30 PM Sylvain Pointeau
> wrote:
>>>>
>>>> Qt is free on desktop, but it is not free on mobile, which is a
>real showstopper for me and many others.
>>>>
>>>> Le mar. 19 févr. 2019 à 20:12, ich  a écrit :
>>>>>
>>>>> Qt is free, too.
>>>
>>>
>>> I received few personal emails to ask me why am I writing that Qt is
>not free on mobile.
>>>
>>> I am sorry but this is the message from the Qt company, please show
>me one official statement that Qt is free to use on mobile.
>>> I would be really glad and finally use Qt instead of looking for
>alternatives.
>>>
>>> Best regards,
>>> Sylvain
>>>
>>>
>>> ___
>>> Interest mailing list
>>> Interest@qt-project.org
>>> https://lists.qt-project.org/listinfo/interest
>>
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> https://lists.qt-project.org/listinfo/interest
>___
>Interest mailing list
>Interest@qt-project.org
>https://lists.qt-project.org/listinfo/interest

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] Fwd: vs. Flutter

2019-02-21 Thread ich
Thou shall not use sellers opinion as legal correct advice:)
qt.io tends to hide facts and even post wrong "facts"...

Am February 21, 2019 1:49:21 PM UTC schrieb Sylvain Pointeau 
:
>On Tue, Feb 19, 2019 at 8:30 PM Sylvain Pointeau
>
>wrote:
>
>> Qt is free on desktop, but it is not free on mobile, which is a real
>> showstopper for me and many others.
>>
>> Le mar. 19 févr. 2019 à 20:12, ich  a écrit :
>>
>>> Qt is free, too.
>>>
>>
>I received few personal emails to ask me why am I writing that Qt is
>not
>free on mobile.
>
>I am sorry but this is the message from the Qt company, please show me
>one
>official statement that Qt is free to use on mobile.
>I would be really glad and finally use Qt instead of looking for
>alternatives.
>
>Best regards,
>Sylvain

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] Fwd: vs. Flutter

2019-02-21 Thread ich
As you said, look at the license:)

You may git clone qt, read the LGPL license, accept it, and deploy your Android 
app.
Just as you do with other LGPL code.

What else official do you need?

Yesterday i found worth reading:
https://wiki.qt.io/Licensing-talk-about-mobile-platforms

Am February 21, 2019 1:49:21 PM UTC schrieb Sylvain Pointeau 
:
>On Tue, Feb 19, 2019 at 8:30 PM Sylvain Pointeau
>
>wrote:
>
>> Qt is free on desktop, but it is not free on mobile, which is a real
>> showstopper for me and many others.
>>
>> Le mar. 19 févr. 2019 à 20:12, ich  a écrit :
>>
>>> Qt is free, too.
>>>
>>
>I received few personal emails to ask me why am I writing that Qt is
>not
>free on mobile.
>
>I am sorry but this is the message from the Qt company, please show me
>one
>official statement that Qt is free to use on mobile.
>I would be really glad and finally use Qt instead of looking for
>alternatives.
>
>Best regards,
>Sylvain

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] Fwd: vs. Flutter

2019-02-19 Thread ich
OK, i've no idea about how to deploy to mobile devices,
but what makes you think its not free?

Am February 19, 2019 7:30:23 PM UTC schrieb Sylvain Pointeau 
:
>Qt is free on desktop, but it is not free on mobile, which is a real
>showstopper for me and many others.
>
>Le mar. 19 févr. 2019 à 20:12, ich  a écrit :
>
>> Qt is free, too.
>>
>> Am February 19, 2019 7:04:03 PM UTC schrieb Sylvain Pointeau <
>> sylvain.point...@gmail.com>:
>>>
>>> I cannot get it copied in the email, but the code in the section get
>>> started has no "new" but I agree with you that it is not
>"declarative"
>>>
>>> The positive points about flutter is that it is free, and intellij
>(IDEA)
>>> is so great.
>>> However, it feels too young, and limited to mobile (some are saying
>that
>>> the desktop is coming, but nothing concrete yet)
>>>
>>> react native (via react xp) seems to be a better alternative for
>now.
>>>
>>> Best regards,
>>> Sylvain
>>>
>>>
>>> Le mar. 19 févr. 2019 à 19:43, Jason H  a écrit :
>>>
>>>> It's still on the home page: https://flutter.io/ "Fast Development"
>>>> I operate on the "read at least the first page" premise. That
>whatever
>>>> they think is most important should be found there.
>>>>
>>>> But losing new doesn't really change my opinion of if it's
>declarative
>>>> or not.
>>>>
>>>> Thanks for the update/correction though.
>>>>
>>>>
>>>> *Sent:* Tuesday, February 19, 2019 at 1:34 PM
>>>> *From:* "Sylvain Pointeau" 
>>>> *To:* "Qt Project" 
>>>> *Subject:* [Interest] Fwd: vs. Flutter
>>>> the "new" is now removed in dart 2.0 so you example is outdated.
>>>>
>>>>
>>>> -- Message transféré -
>>>> De : Jason H 
>>>> Date : mar. 19 févr. 2019 à 19:25
>>>> Objet : Re: [Interest] vs. Flutter
>>>> À : Bernhard B 
>>>> CC : 
>>>>
>>>> I'm in your offtopic camp.
>>>> Everything is going Declarative. I really hate that web
>devevlopment
>>>> requires the use of HTML/CSS/JS (that's just client side) and some
>>>> Framework of the Month. The JavaScript kiddies love inventing
>frameworks
>>>> for fame and profit rather than picking one and making it better.
>>>> Fragmentation is rampant. On top of that JS is slow to change, it
>just
>>>> becomes a runtime that your flavor-of-the-month framework compiles
>down to,
>>>> well until WebAssembly.
>>>>
>>>> Rene, I don't understand why you don't declare Flutter Declarative?
>From
>>>> the Flutter home page:
>>>> Widget build(BuildContext context) {
>>>>   return new Scaffold (
>>>>  appBar: new AppBar ( title: new Text (widget.title), ),
>>>>  body: new Center (
>>>> child: new Text( "Button clicked" ...
>>>>  ),
>>>>  ),
>>>> }
>>>>
>>>> Good luck typing 'new' and 'return' a lot. At least QML manages
>that for
>>>> you. QML is the sleekest of all the declarative languages.
>>>>
>>>>
>>>> *Sent:* Tuesday, February 19, 2019 at 12:55 PM
>>>> *From:* "Bernhard B" 
>>>> *To:* "Bob Hood" 
>>>> *Cc:* "René Hansen" , "Jason H" ,
>>>> inter...@lists.qt-project.org
>>>>
>>>> *Subject:* Re: [Interest] vs. Flutter
>>>> > I've been studying it for a while now, and I've decided that it
>will
>>>> likely be
>>>> my mobile development language.  I love Qt to death for desktop,
>but I've
>>>> never been able to take to it's declarative approach.  I know
>others
>>>> swear by
>>>> it, but it just never fit my brain waves for some reason.
>>>>
>>>> 
>>>> I guess I am one of those persons, who absolutely LOVE Qt's
>declarative
>>>> language.
>>>> I like QML so much, that I even started looking for QML -> HTML/CSS
>>>> translators. While I really like QML,
>>>> I absolutely hate HTML and CSS (never got used to its quirks). I
>mean
>>>> there are some attempts like
>>>> qmlcore (https://github.com/pureqml/qmlcore), but I haven't tried
>tho

Re: [Interest] Fwd: vs. Flutter

2019-02-19 Thread ich
Qt is free, too. 

Am February 19, 2019 7:04:03 PM UTC schrieb Sylvain Pointeau 
:
>I cannot get it copied in the email, but the code in the section get
>started has no "new" but I agree with you that it is not "declarative"
>
>The positive points about flutter is that it is free, and intellij
>(IDEA)
>is so great.
>However, it feels too young, and limited to mobile (some are saying
>that
>the desktop is coming, but nothing concrete yet)
>
>react native (via react xp) seems to be a better alternative for now.
>
>Best regards,
>Sylvain
>
>
>Le mar. 19 févr. 2019 à 19:43, Jason H  a écrit :
>
>> It's still on the home page: https://flutter.io/ "Fast Development"
>> I operate on the "read at least the first page" premise. That
>whatever
>> they think is most important should be found there.
>>
>> But losing new doesn't really change my opinion of if it's
>declarative or
>> not.
>>
>> Thanks for the update/correction though.
>>
>>
>> *Sent:* Tuesday, February 19, 2019 at 1:34 PM
>> *From:* "Sylvain Pointeau" 
>> *To:* "Qt Project" 
>> *Subject:* [Interest] Fwd: vs. Flutter
>> the "new" is now removed in dart 2.0 so you example is outdated.
>>
>>
>> -- Message transféré -
>> De : Jason H 
>> Date : mar. 19 févr. 2019 à 19:25
>> Objet : Re: [Interest] vs. Flutter
>> À : Bernhard B 
>> CC : 
>>
>> I'm in your offtopic camp.
>> Everything is going Declarative. I really hate that web devevlopment
>> requires the use of HTML/CSS/JS (that's just client side) and some
>> Framework of the Month. The JavaScript kiddies love inventing
>frameworks
>> for fame and profit rather than picking one and making it better.
>> Fragmentation is rampant. On top of that JS is slow to change, it
>just
>> becomes a runtime that your flavor-of-the-month framework compiles
>down to,
>> well until WebAssembly.
>>
>> Rene, I don't understand why you don't declare Flutter Declarative?
>From
>> the Flutter home page:
>> Widget build(BuildContext context) {
>>   return new Scaffold (
>>  appBar: new AppBar ( title: new Text (widget.title), ),
>>  body: new Center (
>> child: new Text( "Button clicked" ...
>>  ),
>>  ),
>> }
>>
>> Good luck typing 'new' and 'return' a lot. At least QML manages that
>for
>> you. QML is the sleekest of all the declarative languages.
>>
>>
>> *Sent:* Tuesday, February 19, 2019 at 12:55 PM
>> *From:* "Bernhard B" 
>> *To:* "Bob Hood" 
>> *Cc:* "René Hansen" , "Jason H" ,
>> inter...@lists.qt-project.org
>>
>> *Subject:* Re: [Interest] vs. Flutter
>> > I've been studying it for a while now, and I've decided that it
>will
>> likely be
>> my mobile development language.  I love Qt to death for desktop, but
>I've
>> never been able to take to it's declarative approach.  I know others
>swear
>> by
>> it, but it just never fit my brain waves for some reason.
>>
>> 
>> I guess I am one of those persons, who absolutely LOVE Qt's
>declarative
>> language.
>> I like QML so much, that I even started looking for QML -> HTML/CSS
>> translators. While I really like QML,
>> I absolutely hate HTML and CSS (never got used to its quirks). I mean
>> there are some attempts like
>> qmlcore (https://github.com/pureqml/qmlcore), but I haven't tried
>those
>> yet.
>> 
>>
>> Am Di., 19. Feb. 2019 um 18:47 Uhr schrieb Bob Hood
>:
>>
>>> On 2/18/2019 7:40 AM, René Hansen wrote:
>>> > I've not come across any myself, and have only built a few small
>things
>>> with
>>> > it a bit for now.
>>> >
>>> > Initial reactions was that it is *leagues* ahead of Qt with
>regards to
>>> > developer experience. You're not locked to an IDE, like with
>QtCreator,
>>> and
>>> > the ui live updates across device, simulators, emulators etc. when
>you
>>> write
>>> > changes. No need to build and .apk and wait for a build+deploy.
>>> >
>>> > There's no JS involved. It's Dart all the way. It doesn't even
>ship
>>> with a
>>> > web runtime afaik.
>>>
>>> I've been studying it for a while now, and I've decided that it will
>>> likely be
>>> my mobile development language.  I love Qt to death for desktop, but
>I've
>>> never been able to take to it's declarative approach.  I know others
>>> swear by
>>> it, but it just never fit my brain waves for some reason.
>>>
>>> I saw somebody in this thread moan about it being yet another
>language to
>>> learn.  Putting aside the fact that a robust developer should know
>more
>>> than
>>> one, Dart is quite familiar to anybody who has used a modern
>scripting
>>> language (e.g., Python).
>>>
>>> For me personally, Flutter's "feel" just fits mobile better in my
>mind
>>> than Qt.
>>>
>>> ___
>>> Interest mailing list
>>> Interest@qt-project.org
>>> https://lists.qt-project.org/listinfo/interest
>>
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> https://lists.qt-project.org/listinfo/interest
>> ___ Interest mailing list
>> 

Re: [Interest] [ANN] UniqLogger a Qt-based logging library

2018-11-17 Thread ich
ianal, 
but static linking is allowed, as long as you provide the object files to allow 
relinking.
This seems to be a field of discussion, though...

Alex


Am November 17, 2018 5:51:38 PM UTC schrieb Francesco Lamonica 
:
>Hello René,
>license is indeed LGPL-2 and you can use the library in your commercial
>product.
>That sentence you mention is for some specific needs like static
>compiling
>in a commercial product that, iirc, is not permitted by lgpl.
>
>regards
>
>On Sat, Nov 17, 2018 at 6:01 PM René Hansen  wrote:
>
>> Thank you for sharing Francesco!
>>
>> This seems confusing though, as LGPL is indeed free for commercial
>use:
>>
>> "License is LGPL-2, if you need a commercial license, feel free to
>contact
>> us."
>>
>>
>> /René
>>
>> On Sat, 17 Nov 2018 at 00:23 Francesco Lamonica
>
>> wrote:
>>
>>> Hi all,
>>> I'd just want to announce the availability of the UniqLogger
>library,
>>> it's an open-source Qt-based logging library with multiple backends
>(
>>> file, colored console, network, db) that runs on many platforms
>(linux,
>>> win, macOS, iOS, android)
>>>
>>> You can grab a copy at http://github.com/netresultsit/uniqlogger
>>> ___
>>> Interest mailing list
>>> Interest@qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/interest
>>>
>>

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest