[Interest] Thoughts on a 'proper' (or standard) file/io API for QML?
Vlad Stelmahovsky
vladstelmahovsky at gmail.com
Thu Aug 11 10:08:22 CEST 2016
Sorry for offtop but..
what the reason to use cross platform, native framework and implement file
io via JS?
On Wed, Aug 10, 2016 at 10:36 PM, Alejandro Exojo <suy at 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 at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
--
Best regards,
Vlad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20160811/1dee08e8/attachment.html>
More information about the Interest
mailing list