bad performance is a sum of bad design decisions.
especially in embedded world. and problem not only with IO speed on
embedded, but in memory footprint, GC procedures etc. actually, since you
are in Qt forum, you can read recommendations for using JS (as less as
possible), you can ask people, why
Em terça-feira, 16 de agosto de 2016, às 00:49:03 PDT, Henry Skoglund > Well
at least Qt does something right, I just tested on my Mac, Qt 5.7
> and Thunderbird, "line1" and "line2" show nice line breaks. So far, I
> tested on Ubuntu 14.04, 16.04 and now OSX, all ok with "line1" and
> "line2" on
On 2016-08-16 00:14, Bernhard Lindner wrote:
I can't confirm that it works. I tried on the command-line with xdg-open and
by directly clicking the link above in KMail. Neither time was the body
present at all.
When using the link in the mail, it doesn't work for me too.
When clicking the same
> I can't confirm that it works. I tried on the command-line with xdg-open and
> by directly clicking the link above in KMail. Neither time was the body
> present at all.
When using the link in the mail, it doesn't work for me too.
When clicking the same link in a local html file it works.
Very
On Monday 15 August 2016 17:41:25 Vlad Stelmahovsky wrote:
> I understand need of IO API, but I dont understand why the API should be
> implemented using slow and non effective (comparing to C++) JS
Because the IO itself will be slower than the overhead that the engine
imposes. In a real world
I developed this years *QtCon Conference APP for QtCon in Berlin.*
All with Qt 5.7 Material Style Qt QuickControls2
I'm just starting a very short Beta test Cycle - will end on Friday.
I prepared BetaTest for Android via Google Play and also via iTunes
Connect Testflight for iOS
*The first 5
Em segunda-feira, 15 de agosto de 2016, às 20:29:16 PDT, Bernhard Lindner
escreveu:
> It seems not to be an KMail issue because when writing the following into a
> HTML document, opening it in Firefox and clicking the link in the browser,
> it does exactly what I want (including line breaks in
Good point, my mistake. I saw the GNU license at the top - that only applies to
the Quickly transpiler.
Still, I think it should be part of QML and not an add-on license. What would
it take to get it included?
> Sent: Monday, August 15, 2016 at 2:44 PM
> From: "Gunnar Roth"
Because it isn't that slow. Even so, the Node API provides Async IO. Just because we're off in some engine that is v4 (assuming you're not using the QtQuick Compiler!) doesn't mean it won't be eventually fast. And we shouldn't be restricted to not writing files because it's "slow" when it is
> Am 15.08.2016 um 17:30 schrieb Jason H :
>
>
>
>> Sent: Wednesday, August 10, 2016 at 4:36 PM
>> From: "Alejandro Exojo"
>> To: interest@qt-project.org
>> Subject: Re: [Interest] Thoughts on a 'proper' (or standard) file/io API for
>> QML?
>>
>> On
On 2016-08-15 20:29, Bernhard Lindner wrote:
Hi!
I tried to send an e-mail with a prepared subject, receiver and body
using Qt. The mail shall open in the system default mail client. I am
testing on Linux with KMail and Qt 5.5.
This is the code I intended to use:
Hi!
I tried to send an e-mail with a prepared subject, receiver and body using Qt.
The mail shall open in the system default mail client. I am testing on Linux
with KMail and Qt 5.5.
This is the code I intended to use:
QDesktopServices::openUrl(QUrl("mailto:?
I understand need of IO API, but I dont understand why the API should be
implemented using slow and non effective (comparing to C++) JS
On Mon, Aug 15, 2016 at 5:22 PM, Jason H wrote:
> Many.
> The problem is if you implement non-generic file I/O, it has limited
> applicability,
> Sent: Wednesday, August 10, 2016 at 4:36 PM
> From: "Alejandro Exojo"
> To: interest@qt-project.org
> Subject: Re: [Interest] Thoughts on a 'proper' (or standard) file/io API for
> QML?
>
> On Wednesday 10 August 2016 17:09:17 Jason H wrote:
> > I know it's not a normal
That's just for reading, not writing. So it's disqualified.
It seems like node.js is the only sensible API to copy. Unless we provide our own, but that would limit compatibility with Node, which is the current biggest user of JS/fs codebase.
Sent: Wednesday, August 10, 2016 at
Many.
The problem is if you implement non-generic file I/O, it has limited applicability, and you will always need a C++ layer.
The problem is if you implement generic, non-standard I/O then there is no consistent API and charing code becomes hard, as everyone has to implement everone else's IO
UPDATE: Somehow I lost
ANDROID_PACKAGE_SOURCE_DIR = $$PWD/android
in my .pro
> Sent: Friday, August 12, 2016 at 5:04 PM
> From: "Jason H"
> To: "Jason H"
> Cc: "interestqt-project.org"
> Subject: Re: [Interest] Android not using my
I assume you men a geogrpahical map, as QMap is something else entirely.
It is trivial to interop between C++ and QML. Depending on how you do it, you can just set a context property as a QObject-derived class in the C++ API. Otherwise you have to use it as a MetaType.
I'm not an expert on audio formats & hardware, but I guess sending raw
data directly to an output device without a decoder in between is
probably not a good idea.
Have you tried the examples from http://doc.qt.io/qt-5/audiooverview.html ?
Viktor
On 12.08.2016 14:00, Anisha Kaul wrote:
> Much
Hi Chris,
> Is there any plan to add support for J1939 in QtSerialBus?
So far, no. As J1939 is a "higher-level" protocol, like CANopen, it
could be added as separate class if there is enough interest and people
help testing the development (I'm currently not working with either
protocol).
20 matches
Mail list logo