Good morning, I am currently trying to implement a...

# moko

[Uli Niggemann]

Good morning,
I am currently trying to implement a customer/brand/theme based app.
The basic idea is to have a “Base”-Set of colors, images and strings. However, all properties must be overwritable via another set (e.g. override thge logo, but the navigation-drawer-icon should be used from “base”.

I would like to do that directly via moko-resources for both platforms.
My first approach was to create two library projects that both have Moko resources, but this seems to clash even if I have different `multiplatformResourcesPackage`s.
An other way would be to have a “virtual”/merged source commonMain/ressources/MR but this would also be quite complex at some point.
Which approach do you guys use? Is there anything

[alex009]

we use resources in multiple modules and all works fine.
just set different package.
what exactly not work with different packages?

[Uli Niggemann]

Oh, you are right. (I didn’t override all dimensions of the logo therefore it was not displayed)
And afterwards you are doing something like this?

painterResource(
try  {
   de.jumero.theme.MR.images.logo
} catch (e : Exception) {
   de.jumero.base.MR.images.logo
})

[alex009]

why it should be in this way?

[alex009]

we have resources in multiple modules but this resources is not override eachself

[alex009]

every feature have own set of resources

[alex009]

and access to shared resources

[alex009]

so it's not like your case

[Uli Niggemann]

But unfortunately this is what we need.
For instance if customerA wants to override a icon all other customers needs to have this item in the “customer”-resources…
In android this could be done by simply adding a resource with the same name into the project itself.

[alex009]

i will try to do some experiments to achive this...maybe something will works

[alex009]

are you have android build flavours for android target to achive this?

[Uli Niggemann]

At first I just hoped that the MR resources would be merged if they had the same package - but unfortunately that’s not the case 😉

[alex009]

for android it will, just because android works in this way

[alex009]

but for ios we have separated bundles and this bundles can have same names inside

[Uli Niggemann]

but the generated MR-class is not merged, isn’t it? I guess it has been either the one or the other

[alex009]

classes not merged, yes.

[alex009]

maybe will work - pass gradle property when run gradle compilation, like -Presources.variant=base and base on this property decide what exactly resources library should be added in dependency

[alex009]

not best solution but now i not see some multiplatform way...

[Uli Niggemann]

Hey Aleksey,
Thank you! I will give it a try…