QtWebChannel, QtNFC, what else?



  • Well, after my posts (and from others ) without answer of why NFC is not working on android
    https://www.google.es/search?q=qt+nfc+android+not+working
    https://bugreports.qt.io/browse/QTBUG-61793

    , and decided that examples requires extra files not included, i decided to try out QtWebChannel.

    I created standalone project, compile, run, seems that it doesn't work neither. The QML examples client/server seems to work. But the standalone is not working.

    As i want to use it on a C++ server and QML Client, i use same code that standalone... and my code is of course not working neither.

    I just see how new packages are getting in, but they are not working properly, and nobody seems to check it....

    QtGamepad was used as an excuse to close a report requesting joystick support. Then someone asked to have joystick support on QtGamepad and got as answer that Gamepad is a gamepad and a joystick is joystick.

    https://bugreports.qt.io/browse/QTBUG-34740
    https://bugreports.qt.io/browse/QTBUG-54483

    Now they are adding new modules for IoT and smart home stuff... i guess it will be more of the same.

    I am just commenting what i feel and i see.



  • after my posts (and from others ) without answer of why NFC is not working on android
    i decided to try out QtWebChannel

    How is webchannel a replacement for NFC?

    QtGamepad was used as an excuse to close a report requesting joystick support

    Are you trying to integrate a joystick over NFC/WebChannel?! it seems odd, NFC would be probably too slow for typical joystick response times and I never saw an NFC enable joystick.

    I'm sorry but if this was a code question I'm a bit lost.



  • didn't try to replace NFC using webchannel. I just try out the new modules are coming to Qt, as an exercise to check what i can do with them later.

    Since NFC existed for android in Qt, i was unable to use it. I did long time ago a JNI implementation to use NFC (that was my way to try the JNI Qt API. That JNI API worked great and was enough well documented, so no everything is wrong with Qt)

    I am just telling that lot of new modules are coming, and i feel they don't have enough tests/ good examples/ good documentation and no support at all.

    And i see new modules coming that may end up with same problem.

    This post was just an invitation so someone closes my report about NFC without an answer, or just telling that "it's is working" even if there are people that are unable to make it work and examples and documentation are incomplete.



  • @bnogal said in QtWebChannel, QtNFC, what else?:

    Since NFC existed for android in Qt, i was unable to use it. I did long time ago a JNI implementation to use NFC (that was my way to try the JNI Qt API. That JNI API worked great and was enough well documented, so no everything is wrong with Qt)

    That is sad, but putting a lot of emotion into QTBUG-61793 does not help here.
    If you have problems, you should describe your use case without judging about the status quo. If you have suggestions how to improve examples and documentation, you are invited to do so.

    I am just telling that lot of new modules are coming, and i feel they don't have enough tests/ good examples/ good documentation and no support at all.

    As I said, you are invited to help here. Do your tests and report your results. Developers can fix things if they are aware of them (and if time permits, of course)

    And i see new modules coming that may end up with same problem.

    Sometimes it just take time for a module to mature. With constructive feedback you accelerate this process. As an example: In spring 2016 I tried the new QtSerialBus module (I'm interested in CAN bus at most). It worked, but there were a lot of small problems here and there. So I started contributing and have by now added over 100 patches to improve the things that are important for me (and hopefully for others also).

    This post was just an invitation so someone closes my report about NFC without an answer, or just telling that "it's is working" even if there are people that are unable to make it work and examples and documentation are incomplete.

    As I can see, your bug report is still open. I know the developer has a lot to do (also in totally different areas, like QtSerialBus), and I'm sure he will have a look at your problems as soon as time permits. And reading your bugreport, you already have some experience on Android, so maybe you can help? Remember that Qt covers a lot of platforms.

    QtGamepad was used as an excuse to close a report requesting joystick support. Then someone asked to have joystick support on QtGamepad and got as answer that Gamepad is a gamepad and a joystick is joystick.

    This may sound stupid to the end user, but by reading the linked reports I realized that gamepads and joysticks are using different backend APIs. Also, a joystick is an analog device while a gamepad is digital. Even if you manage to combine the different backends in one module, you have to think about an end-user API that covers both and is easy to understand.

    If you have suggestions how to do this, feel free to comment or even start coding a prototype: You got all the sources, nobody prevents you from improving them.



  • I wish i would have more free time, it is Sunday and i am still working.
    I can try to build some tiny examples to show that they are not working. For webchannel the standalone example is enough to check it.
    For NFC as i was testing Android to Android passing tag, i would make an example for that, if that helps to fix something.

    I really like how Qt works in general, as compared to other frameworks the core is really mature, well designed and documented. And passed the most important test for a framework, stand the test of time. But i really think that the project is running to much to introduce new stuff.

    Like some (or last year) don't remember, when you did a marathon to fix and close reports. I think a new marathon is required to make new modules work like a charm.



  • Well, if someone arrives here.
    The QWebChannel problem was related to have the correct qwebchannel.js version. Also i had the problem that i got crazy and forgot about the famous https://bugreports.qt.io/browse/QTBUG-13334

    This week i will build an example for NFC p2p and add it to my report.


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.