The new resource system in 1.6.0 is nice but it feels like a downgrade in that it doesn't seem to su...

# compose-desktop

[Marcin Wisniowski]

The new resource system in 1.6.0 is nice but it feels like a downgrade in that it doesn't seem to support nested directories.
I had my graphics organized nicely into a directory tree, but to migrate to the new resources I have to dump them all together into composeResources/drawable with no subdirectories allowed.

[romainguy]

I assume it's because it makes it compatible with Android resources

[Marcin Wisniowski]

Probably, but when I'm making a Desktop-only project without Android (or anything else multiplatform), it doesn't feel like limitations of Android should apply. So that's my feedback.

[Marcin Wisniowski]

It does allow resources with - in the name, even though Android doesn't. 🤔

[mohamed rejeb]

I think this can be possible and compatible with android, maybe during compile time the resources can be moved to the drawable folder.
And the names can be something like this:
/drawable/icon/cancel.xml -> Res.drawable.icon_cancel

[mohamed rejeb]

@Konstantin Tskhovrebov 👀

[Altynbek Nurtaza]

would it then be a problem to have both /drawable/icon/cancel.xml and /drawable/icon_cancel.xml? @mohamed rejeb

[mohamed rejeb]

Yes the build can fail in this case with a message saying that there's two resources with the same name or something like that.

[Konstantin Tskhovrebov]

nested directories are supported in the files directory but there are no static accessors. so, you need to choose.
the nesting makes static accessors generation much harder.

[Marcin Wisniowski]

Sure, using Res.readBytes() works, but using that for every resource is not a real choice. The real choice is to no longer organize your resources, or keep using the old resource system which supports nested directories. I think the static accessors are worth it, but it's still a loss.

[Marcin Wisniowski]

I have opened an issue for this: https://github.com/JetBrains/compose-multiplatform/issues/4487