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 12:46 PM
From: "Richard Moore" <r...@kde.org>
To: "interestqt-project.org" <interest@qt-project.org>
Subject: Re: [Interest] Thoughts on a 'proper' (or standard) file/io API for QML?
From: "Richard Moore" <r...@kde.org>
To: "interestqt-project.org" <interest@qt-project.org>
Subject: Re: [Interest] Thoughts on a 'proper' (or standard) file/io API for QML?
Another set of js file API already exist:
Rich.
On 10 August 2016 at 16:09, Jason H <jh...@gmx.com> 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
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?
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
