https://kotlinlang.org logo
Title
a

andylamax

11/05/2020, 10:40 AM
Only thing that makes me cringe is seeing the
androidx
imports in desktop code. i wish the package name, could be platform agnostic. Probably
compose
?🤷‍♂️ Is it just me who is disturbed by this? anyone else?
22
1
o

olonho

11/05/2020, 10:58 AM
We want to make sure the sourcecode is compatible between Jetpack Compose and CfF, and introducing different package name looks not very reasonable in light of that
a

andylamax

11/05/2020, 11:05 AM
I understand it is abit late to do this. But just importing
androidx.*
packages in a none android project, is like seeing
import {File} from "<http://java.io|java.io>"
c

caelum19

11/05/2020, 4:09 PM
I think there should only be 1 package prefix if the code is compatible, and from a technical standpoint if androidx.compose packages aren't actually android specific, maybe they shouldn't have androidx at the start. But also it is part of a project with androidx people made with what I assume is androidx resources so it feels a bit unreasonable to suggest that they change it. Maybe in the medium-term future this stuff can move to a separate organisation developed by other organizations like Kotlin is?
a

andylamax

11/05/2020, 4:37 PM
if one uses androidx resources, Is it a requirement to have an
androidx
package name?
l

Leland Richardson [G]

11/05/2020, 5:35 PM
i tried to push for compose to have a different package name early on for precisely this reason. no dice 😛
😥 20
😔 4
l

louiscad

11/06/2020, 10:56 AM
Since Compose is still in alpha, it's still time for such a change, right?
4
☝️ 3
a

Arkadii Ivanov

11/06/2020, 11:56 AM
Agree! It will increase adoption in future by iOS teams.
✔️ 2