home.social

#pyqtdeploy — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #pyqtdeploy, aggregated by home.social.

  1. @birnim I developed an app using #pyqtdeploy and #Kirigami a few years ago.
    One limitation I noticed that however which Python Qt API limits you to access Qt's Android API's
    that you have to use because of Android's interaction with files.
    In general you are more limited when having to call Java API's.
    The other thing was that Androids #openssl fork #boringssl was a limitation if your Qt is build with
    openssl.
    A smaller issue was to setup scripts for building and bootstrapping.

  2. @birnim I developed an app using #pyqtdeploy and #Kirigami a few years ago.
    One limitation I noticed that however which Python Qt API limits you to access Qt's Android API's
    that you have to use because of Android's interaction with files.
    In general you are more limited when having to call Java API's.
    The other thing was that Androids #openssl fork #boringssl was a limitation if your Qt is build with
    openssl.
    A smaller issue was to setup scripts for building and bootstrapping.

  3. @birnim I developed an app using #pyqtdeploy and #Kirigami a few years ago.
    One limitation I noticed that however which Python Qt API limits you to access Qt's Android API's
    that you have to use because of Android's interaction with files.
    In general you are more limited when having to call Java API's.
    The other thing was that Androids #openssl fork #boringssl was a limitation if your Qt is build with
    openssl.
    A smaller issue was to setup scripts for building and bootstrapping.

  4. @birnim I developed an app using #pyqtdeploy and #Kirigami a few years ago.
    One limitation I noticed that however which Python Qt API limits you to access Qt's Android API's
    that you have to use because of Android's interaction with files.
    In general you are more limited when having to call Java API's.
    The other thing was that Androids #openssl fork #boringssl was a limitation if your Qt is build with
    openssl.
    A smaller issue was to setup scripts for building and bootstrapping.

  5. @birnim I developed an app using #pyqtdeploy and #Kirigami a few years ago.
    One limitation I noticed that however which Python Qt API limits you to access Qt's Android API's
    that you have to use because of Android's interaction with files.
    In general you are more limited when having to call Java API's.
    The other thing was that Androids #openssl fork #boringssl was a limitation if your Qt is build with
    openssl.
    A smaller issue was to setup scripts for building and bootstrapping.