Hello ! I was looking to implement compose desktop-based time and date pickers, but could not import...

# compose-desktop

[Raphaël Blard]

Hello ! I was looking to implement compose desktop-based time and date pickers, but could not import them in 1.4.1.
Are these unavailable, or was I simply unable to find them ?
Thank you very much

[Kirill Grouchnikov]

What are you trying to import exactly, the material pickers? Compose Multiplatform 1.4.1 ships with M3 1.0.1, not 1.1.0.

[Kirill Grouchnikov]

https://github.com/JetBrains/compose-multiplatform/issues/3256#issuecomment-1595164729

[Raphaël Blard]

Ah, and material date/time pickers are in 1.1.0 ? Gotcha.

[Raphaël Blard]

Thank you

[Mitchell Syer]

I have a library you could use for date and time pickers https://github.com/Syer10/compose-material-dialogs

[Raphaël Blard]

Thank you !

[CLOVIS]

@Mitchell Syer are you using the M3 wheel time picker on Desktop? I'm worried it won't be great UX using a mouse.

[Kirill Grouchnikov]

Are these two diverging libraries at the moment? The original seems to be quite active.

[Mitchell Syer]

I mostly use cherry picking to pull upstream commits, so it just looks that way

[Kirill Grouchnikov]

The project’s landing page doesn’t have any info from what I can see on what is the difference between the original and the fork.

[CLOVIS]

I was expecting to see some desktop screenshots in the README, too

[Mitchell Syer]

There isn't any real differences other then using Kotlinx Datetime instead of java.time and it being multiplatform instead of Android only

[Kirill Grouchnikov]

Is the original repo against contributions to support multiplatform? Apologies for the drive by comments, it’s just not clear why there is an active fork of an active library, with no clear message on the landing page.

[Kirill Grouchnikov]

(and using the same name)

[Mitchell Syer]

Upstream is very android only, any function that takes text can take a android Res integer as well. To integrate Compose Mutliplatform they would need to remove all raw Res support.
So I just made my fork and left it at that.
Also I didn't make any extra screenshots since it doesn't focus on any 1 platform, it supports Android, Desktop, and iOS, no need for platform screenshots when they are the same dialogs.

[Kirill Grouchnikov]

If you look at it from the perspective of an outsider, it’s a total mystery.

An active fork of an active library. No prominent callout on why it’s needed (the only difference that I can find is the last two words in “Easy to use library to help you build complex dialogs using Compose Multiplatform”). Same package name in the modules.

Anyways, this is distracting from the original question.