But as Volker said, what's the value of QFile exposed to those other
languages? Developers would probably prefer to use the native API for it.
Likewise for sockets in QtNetwork, or DNS lookup, or the XML and JSON content:
there's little unique about it. Our implementations may be better than
whatever else is available, but not unique.
Even QNAM might be a push, because most of those other languages have full
HTTP stacks (which may or may not be using the proxy settings correctly).
Having file, network, dns etc access in the bridged language doesn't
directly help you when you're writing QML. In QML you either need to use
Qt's QML modules or extra functionality manually exposed from the
bridged language. The latter is more hassle (and it will result in N+1
different ways of accessing files from QML).
best regards,
Ulf
--
Development mailing list
[email protected]
https://lists.qt-project.org/listinfo/development
