So just some feedback FWIW. I think moko (template especially) saves some config headaches. Howeve...

# moko

[Andy Gibel]

So just some feedback FWIW. I think moko (template especially) saves some config headaches. However, what I would find really valuable is a medium article or something describing exactly what is going on in your DSLs. I know the source is available but just some discussion on why you chose this abstraction, what problems it's solving, future support plans, etc

[Michal Harakal]

I can imagine, that guys are now quite busy with KotlinConf preparation https://kotlinconf.com/speakers/d15615b3-f005-4c37-b133-beddab03f7a8/

[Andy Gibel]

oh nice! Good call I didn't know they were speaking. Very cool

[alex009]

what exactly DSLs you mean?

[Andy Gibel]

Well not DSLs I guess but the special setup basically. The setup framework call with exports, the integration of the cocoapods plugin. I was also not sure why you had an AndroidManifest in the mpp-library androidMain. I haven't seen it setup like this before

[alex009]

all android libraries must have AndroidManifest 🙂 main sourceset (default path for android) in mpp module is strange, so we change main to androidMain and AndroidManifest also like res directory moved to androidMain

[alex009]

so you mean more description of https://github.com/icerockdev/mobile-multiplatform-gradle-plugin ?

[Andy Gibel]

Right, exactly

[alex009]

maybe you can add issue on github with list of questions? this will be helpful

[Andy Gibel]

Ah ok. Didn't know if you wanted to track non tech issues there

[Andy Gibel]

Also as you can see from above I often have newbie questions and don't want to pollute your GitHub :P

[alex009]

i mean add issue for documentation improvement. with questions that cannot be answered in the current documentation

[alex009]

other questions can be asked here in slack 🙂

[Patrick Jackson]

agree with @Andy Gibel . I'm attempting to pull in the resources library/plugin into an existing KotlinMP project and having a hard time with it. Your projects are not setup like 'typical' kotlin mp projects. and the kotlin build.gradle files add another layer (I'm using groovy)

[alex009]

Can you show more details about problems with setup? in which repository and what part of the documentation should be improved? which points are not clear?

[Patrick Jackson]

One current problem is having a dependency on a moko resource based module in another kotlin MP module. I run into all kinds of gradle sync problems. I'm using the standard groovy KMP in the other module build.gradle. I would expect to be able to add `implementation project(':mymodule') in the commonMain dependency block. When building I get an error:

Could not resolve project :mymodule.
     Required by:
         project :templates > project :sdk
      > Cannot choose between the following variants of project :smymodule:
          - androidDebugAndroidTestCompile
          - androidDebugAndroidTestRuntime``

[Patrick Jackson]

Ran into other errors and sync problems as I tried various setups, but haven't documented them. I like what your doing, just spinning my wheels trying to get setup

[alex009]

can you show project config? or maybe project on github? i will try help with dependency issue if i reproduce it