soywiz
soywiz
Once everything is in its place again, we can try to split korge and the other libraries. To avoid duplication of the buildSrc folder, we can create a github repository...
And people need to comment them in the `gradle.properties`: ``` #org.gradle.configuration-cache=true #org.gradle.configuration-cache.problems=warn ``` We will need to test in e2e tests to avoid regressions. `packageJvmLinuxApp`, `packageJvmMacosApp` and `packageJvmWindowsApp`.
### Discussed in https://github.com/korlibs/korge/discussions/2089 Originally posted by **AShynkevich** December 24, 2023 Hello, I tried to create "hello world" application on Korge engine. OS: MacOS Sonoma 14.1.1 IDE: IntelliJ IDEA Ultimate...
Second time it is called it is already there.
Like the old libs, but for package name. Keeping `korge-foundation` and `korge-core` as a module without code linking to each module individually. * `korge-time` * `korge-crypto` * `korge-datastructure` * ......
For all the modules excluding KorGE (where JVM is used for desktop) And only targets supported by kotlinx-coroutines.
Ads shown in store and docs should be removed to sponsors.
Could be possible to instead of: ``` src@native/File.kt ``` have: ``` src/[email protected] ``` ? Could we autogenerate symbolic links somehow in a way that works? Would that require Kotlin support...
Maybe like `SystemFont.getFirstFont("Times New Roman", "Times", "serif", "sans-serif", "monospace")` Discussion here: https://github.com/korlibs/korge/discussions/2019
This week I fugured out that most of the time dynamic Proxies that perform castings and things like that that have a lot of overhead can be replaced with MethodHandles...