A Preview (not available in the repo) of the new D-KMP Navigation for Compose, which will work on an...

# compose

[Daniele B]

A Preview (not available in the repo) of the new D-KMP Navigation for Compose, which will work on any platform: Android, Web, Desktop. The navigation logic is hosted in the shared-code, and will apply also to SwiftUI.
Any feedback is welcome.

[Daniele B]

Currently the logic in MainComposable is to just display a single screen, but I am working on a logic to also display it as “two-pane”, in case the shared-code navigation logic decides so.
The shared-code navigation logic knows everything, as it also gets notified of screen orientation changes.

[andylamax]

Since any feedback is welcomed, here is one.

While DKMP is a good name for an architecture, I think DKMP is a bad name for a library.

[Daniele B]

It’s D-KMP, with an hyphen 😉
what do you mean exactly?

[Daniele B]

I guess you mean it’s not possible to add the hyphen in a Class name? is this the reason?

[andylamax]

I mean DKMPNavigation and DKMPApp are not very intuitive names for classes

[Daniele B]

yes it comes out as a 4-letters acronym
the alternative would be: DkmpNavigation and DkmpApp, but still not sure which version I prefer

[tad]

The class names could just be Navigation and App

[tad]

DKMP means nothing to someone reading the code

[andylamax]

in deed.

Navigation can be class in the dkmp package

[Daniele B]

if it’s part of a dkmp package, which you can import in your app, then yes, it would be superfluous to add the acronym as part of the class name, as dkmp would already be in the package name

[Daniele B]

I have made naming/code changes. Now the only class starting with “DKMP” is “DKMPApp”, which should be tolerable ;-)

[tad]

Keep in mind the standard Kotlin and Java naming convention: acronyms are titlecased (URI -> Uri, UIFoo -> UiFoo, etc.)