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 "fast enough" for almost anyone.
Sent: Monday, August 15, 2016 at 11:41 AM
From: "Vlad Stelmahovsky" <vladstelmahov...@gmail.com>
To: "Jason H" <jh...@gmx.com>
Cc: interest@qt-project.org
Subject: Re: [Interest] Thoughts on a 'proper' (or standard) file/io API for QML?
From: "Vlad Stelmahovsky" <vladstelmahov...@gmail.com>
To: "Jason H" <jh...@gmx.com>
Cc: interest@qt-project.org
Subject: Re: [Interest] Thoughts on a 'proper' (or standard) file/io API for QML?
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 <jh...@gmx.com> wrote:
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 libray.The only reasonable solution is to provide a generic standard libray which satisfies every both use cases. The more code that gets written in QML, the more need you'll have to write to files. With this API missing, we are headed for a disaster. I'm surprised we've gone for this long without one.Sent: Thursday, August 11, 2016 at 4:08 AM
From: "Vlad Stelmahovsky" <vladstelmahov...@gmail.com>
To: interest@qt-project.org
Subject: Re: [Interest] Thoughts on a 'proper' (or standard) file/io API for QML?Sorry for offtop but..what the reason to use cross platform, native framework and implement file io via JS?_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interestOn Wed, Aug 10, 2016 at 10:36 PM, Alejandro Exojo <s...@badopi.org> wrote:On Wednesday 10 August 2016 17:09:17 Jason H wrote:
> I know it's not a normal thing, but occasionally in QML we need to access
> files. Exposing an object is not hard, but it would be really good to have
> a standard to enable QML libraries that use file IO.
>
> There are two ways to basically so this:
> - QML Specific API
> - Node.JS-compatible API
>
> I did find this: https://github.com/trollixx/node.qml
This is a different thing IMHO.
> But I think this is something Qt needs to standardize on. My opinion is to
> use the Node API, which contains sync and async functions.
>
> Does anyone have any opinions or insight on this?
Yes, isn't that what CommonJS intended? I don't remember what Qbs had, but
something like that I think.
Meanwhile, you should check this:
http://ibeliever.github.io/quickly/
--
Alex (a.k.a. suy) | GPG ID 0x0B8B0BC2
http://barnacity.net/ | http://disperso.net
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest--Best regards,Vlad
Best regards,
Vlad
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
