home.social

#kni — Public Fediverse posts

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

  1. 3d в MonoGame, python в c# или всё таки KNI в браузере? трёхслойная постирония о том, как я игру делал

    Всем привет. В ходе этого материала вы узнаете: 1. Как сделать простой рендер на c# в MonoGame 2. Что использовать, чтобы вызвать python из c# 3. Почему пункт 2 - это плохая идея 4. Как MonoGame игру сбилдить в web/html с помощью его форка KNI Пристёгивайтесь, будет весело! ПРИСТЕГНУТЬСЯ!

    habr.com/ru/articles/1007946/

    #kni #monogame #microsoft_xna #mazegame #blazor_webassembly

  2. #Android friends, how do you unit test your #JNI / #KNI code? Do you write extra KNI glue just so you can trigger internal native methods that call back out into #Kotlin?

    Do you restrict yourself to only integration tests and black-box tests and just *not* unit-test this stuff?

    All solutions we’ve tried/considered so far kinda feel bad.

    (I'm mostly dealing with C/C++ and Kotlin)

  3. #Android friends, how do you unit test your #JNI / #KNI code? Do you write extra KNI glue just so you can trigger internal native methods that call back out into #Kotlin?

    Do you restrict yourself to only integration tests and black-box tests and just *not* unit-test this stuff?

    All solutions we’ve tried/considered so far kinda feel bad.

    (I'm mostly dealing with C/C++ and Kotlin)

  4. #Android friends, how do you unit test your #JNI / #KNI code? Do you write extra KNI glue just so you can trigger internal native methods that call back out into #Kotlin?

    Do you restrict yourself to only integration tests and black-box tests and just *not* unit-test this stuff?

    All solutions we’ve tried/considered so far kinda feel bad.

    (I'm mostly dealing with C/C++ and Kotlin)

  5. #Android friends, how do you unit test your #JNI / #KNI code? Do you write extra KNI glue just so you can trigger internal native methods that call back out into #Kotlin?

    Do you restrict yourself to only integration tests and black-box tests and just *not* unit-test this stuff?

    All solutions we’ve tried/considered so far kinda feel bad.

    (I'm mostly dealing with C/C++ and Kotlin)

  6. #Android friends, how do you unit test your #JNI / #KNI code? Do you write extra KNI glue just so you can trigger internal native methods that call back out into #Kotlin?

    Do you restrict yourself to only integration tests and black-box tests and just *not* unit-test this stuff?

    All solutions we’ve tried/considered so far kinda feel bad.

    (I'm mostly dealing with C/C++ and Kotlin)