does exists any port guide to korge 2 or maybe it isnt neces

Question

does exists any port guide to korge 2 or maybe it isnt necessary

RezMike · Answer

We re planning to write it soon

Pablo Caviglia · Answer

i ve some questions maybe before writing the docs you can help me out

Pablo Caviglia · Answer

```com soywiz korge view Fonts``` doesn t exists anymore

Pablo Caviglia · Answer

```override suspend fun init injector AsyncInjector Unit = injector run``` i have this in my module definition but looks like the method init cannot be overriden anymore

RezMike · Answer

Check something like `fun AsyncInjector init `

Pablo Caviglia · Answer

i have this ```val graphics = mainGraphics graphics fill Colors if lives i 00D4A9 else AAAAAA roundRect liveX liveY liveWidth liveHeight 30 0 30 0 ``` but the extension function of Graphics to add a new Graphics instance to itself doesn t work anymore

Pablo Caviglia · Answer

can it be that Graphics is not a component anymore

RezMike · Answer

not a container

Pablo Caviglia · Answer

sorry container

RezMike · Answer

maybe

RezMike · Answer

well you shouldn t use Graphics instance as a container anyway

Pablo Caviglia · Answer

ok got it will refactor that

Pablo Caviglia · Answer

```text text = if valid GREAT else WRONG resultTextView = this format = Html Format align = Html Alignment MIDDLE CENTER color = colorState size = 40 face = Html FontFace Bitmap fontLoader FontLoader Font NORMAL FONT xy circleResult x + circleResult width 2 width 2 circleResult y + circleResult height 1 1 ``` format attribute doesn t exists anymore on Text

RezMike · Answer

You should use TextAlignment instead

Pablo Caviglia · Answer

perfect that works

Pablo Caviglia · Answer

when upgrade to korge 2 the font rendering is quite different Anything I should know about it to change

Pablo Caviglia · Answer

this is the font definition i m using

Pablo Caviglia · Answer

< Deactivated User> sorry can you help me with this what can have happened that the font definition that previosuly worked fine now it looks weird

Deactivated User · Answer

I have fixed the text rendering a few hours ago not in rc2

Deactivated User · Answer

will be in the next release

Deactivated User · Answer

you can try it by downloading korge next repo changing version to 2 0 0 rc2 on the gradle properties and gradlew publishToMavenLocal

Deactivated User · Answer

it should be fixed by now

Pablo Caviglia · Answer

i ve this one configured as buildscript dependency ``` com soywiz korlibs korge plugins korge gradle plugin $korgePluginVersion ``` and this repo ```maven url = uri <https dl bintray com korlibs korlibs> ```

Pablo Caviglia · Answer

```korgePluginVersion=2 0 0 1 rc2```

Deactivated User · Answer

```korgePluginVersion=2 0 0 2 rc2``` is the latest

Deactivated User · Answer

that uses 2 0 0 rc2 artifacts

Pablo Caviglia · Answer

what about the repo is my configuration ok

Deactivated User · Answer

the 2 0 0 2 rc2 is the version of the gradle plugin

Deactivated User · Answer

Deactivated User · Answer

these are the repositories you should have

Pablo Caviglia · Answer

perfect

Pablo Caviglia · Answer

trying it now

Pablo Caviglia · Answer

thx

Deactivated User · Answer

+1

Pablo Caviglia · Answer

i ve also defined this project dependencies ```dependencies add commonMainApi com soywiz korlibs korvi korvi 2 0 0 rc2 add commonMainApi com soywiz korlibs korgw korgw 2 0 0 rc2 ``` should I change these versions

Deactivated User · Answer

they are probably published

Deactivated User · Answer

korgw is already included with korge

Pablo Caviglia · Answer

they are and they work fine but not sure if your font fix is in that version because i m getting the same result

Deactivated User · Answer

have you downloaded <https github com korlibs korge next>

Deactivated User · Answer

and gradle properties gt version=2 0 0 rc2

Deactivated User · Answer

and gradlew publishToMavenLocal

Pablo Caviglia · Answer

oooh gotcha you havent published it yet to the mvn repo

Pablo Caviglia · Answer

ok i ll have to wait because whenever i push my code i ll have the build server to fail because it will go search the dependencies remotely

Pablo Caviglia · Answer

i can wait if you tell me that you ll release the next version later

Pablo Caviglia · Answer

when are you planning to actually release that version

Deactivated User · Answer

we are waiting for the final release of Kotlin 1 4 20

Deactivated User · Answer

there are still a couple of issues I have to fix before the final release but probably that will happen in the next days

Pablo Caviglia · Answer

oh ok that s soon

Deactivated User · Answer

yeah if Kotlin 1 4 20 is not released this week I will release rc3 using the 1 4 20 rc version that is already on central

Pablo Caviglia · Answer

do you know if expect actual wil lbe part of 1 4 20 as a stable functionality

Deactivated User · Answer

what do you mean by expect actual

Deactivated User · Answer

korge requires 1 4 20 because 1 4 10 had some nasty bugs with the js backend

Pablo Caviglia · Answer

the kotlin functionality to define an interface common to all platforms by using expect keyword and the actual implementation

Deactivated User · Answer

multiplatform projects are 1 4 x is still experimental

Deactivated User · Answer

but it works fine

Pablo Caviglia · Answer

when I try to compile with gradle a korge s project using that syntax I get an error message indicating that I should enable explicitly multiplatform

Deactivated User · Answer

uhm

Pablo Caviglia · Answer

and i weren t able to find yet the place to let the kotlin compiler to know that I do want to use the experimental api

Deactivated User · Answer

can you put the error

Pablo Caviglia · Answer

sure one sec

Pablo Caviglia · Answer

ok for some reason probably because I ve updated to korge 2 the error has changed and looks simpler to fix

Pablo Caviglia · Answer

the weird thing is that I actually have defined the Video implementation for jvm

Deactivated User · Answer

that s because jvm and android source sets are different

Deactivated User · Answer

jvmAndroidMain or androidMain

Pablo Caviglia · Answer

uhhhm yes in fact I m getting this only when trying to build androidAar task

Pablo Caviglia · Answer

when I run runJvm task it doesn t complain

Pablo Caviglia · Answer

does it have something to do with android build variants

Pablo Caviglia · Answer

I see there s a well known nomenclature on the error message C devel projects tool framework multi platform src commonMain kotlin com senaptec toolframework ui Video kt 3 14 Expected class Video has no actual declaration in module lt tool framework multi platform debug gt for JVM that debug at the end of the module name seems to be the debug variant of an android project

Deactivated User · Answer

have you tried to put the actual on a folder called jvmAndroidMain so it works for both jvm and android

Pablo Caviglia · Answer

didnt know that target exists

Pablo Caviglia · Answer

let me try

Pablo Caviglia · Answer

should I define something else on build gradle or only by adding that extra folder should be enough

Deactivated User · Answer

is not a target but a source set both the android and the jvm targets include that folder to read the kotlin files from there

Deactivated User · Answer

if you are using the korge plugin that plugin configures those folders automatically

Pablo Caviglia · Answer

using it

Deactivated User · Answer

uhm

Deactivated User · Answer

maybe the plugin not

Pablo Caviglia · Answer

let me check if there s a way to list the sourcesets with some gradle task

Deactivated User · Answer

only korge next when building the projects

Deactivated User · Answer

you can try to just copy the jvmMain files into androidMain

Pablo Caviglia · Answer

actually there s no implementation at all in that only class they are defined exactly the same on both androidMain and jvmMain as this ```package com senaptec toolframework ui actual class Video ``` and then in commonMain as this ```package com senaptec toolframework ui expect class Video ```

Deactivated User · Answer

then if it fails the androidMain folder is not being loaded as part of the android source set

Pablo Caviglia · Answer

i m using this flag on korge s plugin will try without it to trace if that s causing it not probable but let s give it a try ```androidLibrary = true```

Deactivated User · Answer

the build platforms android build gradle doesn t reference the src androidMain folder

Pablo Caviglia · Answer

let me check

Pablo Caviglia · Answer

looks like not

Deactivated User · Answer

wtf looks like

Deactivated User · Answer

then that s a bug

Deactivated User · Answer

There is a `build extra gradle` you can add that manually

Deactivated User · Answer

```android sourceSets main java srcDirs += C devel projects tool framework multi platform src androidMain kotlin ```

Deactivated User · Answer

at least to try if that way it works

Deactivated User · Answer

Just created this issue <https github com korlibs korge next issues 71>

Pablo Caviglia · Answer

trying it now

Pablo Caviglia · Answer

< Deactivated User> man sorry it took this long to get back to you The android sourcesets fix on build extra gradle worked perfectly

Pablo Caviglia · Answer

now the expect actual declarations works as expected

Pablo Caviglia · Answer

how can I write into that file in the normal way because it s on the build folder and after a clean it ll get deleted

Deactivated User · Answer

well it is a bug should not be required I m going to fix that in the next release hopefully

Pablo Caviglia · Answer

oh great i ll wait then until its officially released

Pablo Caviglia · Answer

thx man

Deactivated User · Answer

+1 thanks for trying

Pablo Caviglia · Answer

everything is getting a great shape congrats for all the hard work man really appreciate all of this

Pablo Caviglia · Answer

i ve convinced my boss to stay on korge instead of unity

Deactivated User · Answer

oh that s great news smile cool

Pablo Caviglia · Answer

made my first demo on multiplatform with android and ios

Pablo Caviglia · Answer

everything run as expected on both platforms