Does compose provide some standalone way to deal with Strings and translations without xml resources?

what is the right way of making something like a page with multiple pages inside like viewPager and tab layouts , also how to handle the state of moving through them?

🤔 Did recomposing on

Configuration

changes stop working recently? That’s what it seems like when I use the code snippet below and specify

android:configChanges="uiMode"

in my manifest.

MaterialTheme(
    colors = if (isSystemInDarkTheme()) darkColors() else lightColors()
) {
    Box(
        Modifier.size(48.dp),
        backgroundColor = MaterialTheme.colors.onBackground
    )
}

The color of the

Box

doesn’t change when I toggle dark mode on my device (pixel 3), but I feel like it did on an older version of compose. The color does get updated correctly if I kill the app and re-open it. I’m seeing this behavior on

alpha01

and

dev17

, using API 29. I also tried similar things by using

ConfigurationAmbient.current

directly, and saw the same behavior. When debugging the app, I was able to see

AndroidComposeView.onConfigurationChanged

get called with the new

Configuration

though.

Hey everyone! I am thrilled to introduce Airbnb’s latest open source project - 🔦 Showkase 🔦 Showkase is an annotation processor based Android library that helps you organize, discover, search and visualize Jetpack Compose UI elements. It auto-generates a UI browser app for you ✨ More info in the thread 👇🏼

Also struggling to figure out how to load an xml drawable. Apparantly the imageResource function isn’t appropriate for that.

Is it possible to use Jetpack Compose within multiplatform modules?

Beginner's question: how to interact with outside world from compose, lets say I have on click on a button and lets say that I want to start a service with that. Or the other way around, I get a message from service in a an activity holding composable, do I need to pass it to viewmodel and trigger recomposition via live data for example or do I have some other options?

Having an issue with getting started with Compose. I only copy pasted these dependencies and configs in an existing project https://developer.android.com/jetpack/compose/setup

Playing around with Jetsnack sample. The project compiles and works fine. But the preview is broken because it is unable to handle the SystemUI padding modifier. Under the hood is NPE about InsetAmbient.current is NULL. I believe this is the case when the Preview can't provide the framework's Window(or any other components) and it breaks. Will Preview support such things in the future or we(developers) have to avoid of passing any Contexts, Windows, etc to composable functions that must work inside Preview?

Jetchat sample. Is it a known issue? Huge performance tanking when selecting the text.

Compose Preview doesn’t work with Multiplatform modules. The next use cases are not working • Android module with Compose implements a Multiplatform module with JVM target (didn’t try with Android target) • Compose inside Multiplatform module But it is working perfectly if Compose is in an Android module and it implements a Kotlin JVM module

Where should bugs against material components be filed? Regular issue tracker?

Just starting to really use compose. Going through the tutorial it starts with

Text("A day in Shark Fin Cove")
        Text("Davenport, California")
        Text("December 2018")

and then tells you to wrap it in a column

Column {
        Text("A day in Shark Fin Cove")
        Text("Davenport, California")
        Text("December 2018")
    }

Is there an easy way to wrap elements in a layout? I think swift UI had an easy way to highlight and right click > wrap with X layout or something. I could see myself using that a lot. Would also be nice to get a list of all layouts when you "surround with" or something. Unless this already exists... and I'm missing it.

Other thoughts from going through the tutorial, maybe someone from the team will find my beginner point of view interesting? Starting a thread:

Where can I file issues related to the docs on developer.android.com? If we can do pull-requests it'll be even better 😄 Sometimes I see references to APIs/Composables that have been renamed or deprecated - e.g. this one.

VerticalScroller

was deprecated in dev15 and

ScrollableColumn

is the Composable to be used. Also

LazyColumnItems

was renamed to

LazyColumnFor

in dev16.

Is anyone seeing this error:

Caused by: java.lang.IllegalStateException: Reading a state that was created after the snapshot was taken or in a snapshot that has not yet been applied

at androidx.compose.runtime.snapshots.SnapshotKt.readError(Snapshot.kt:1495)

at androidx.compose.runtime.snapshots.SnapshotKt.readable(Snapshot.kt:1491)

at androidx.compose.runtime.snapshots.SnapshotKt.readable(Snapshot.kt:1482)

at androidx.compose.runtime.SnapshotMutableState.getValue(MutableState.kt:294)

...then my code

It's happening pretty randomly, in code WAY down in my base layers that has absolutely nothing to do with Compose, and at expressions that are very simple and shouldn't fail (one example is just creating a Fraction instance from the apache library).

Although this is not directly related to compose, it's about AS 4.2 Canary 8 and Gradle 6.6. I'm getting the following error when I try to build my compose project which is using gradle kotlin dsl, with the specified AS and gradle versions

Unable to load class 'kotlin.KotlinNothingValueException'.

This is an unexpected error. Please file a bug containing the idea.log file.

I’m always getting the following error:

e: java.lang.NoSuchMethodError: 'void org.jetbrains.kotlin.cli.common.messages.MessageCollector$DefaultImpls.report$default(org.jetbrains.kotlin.cli.common.messages.MessageCollector, org.jetbrains.kotlin.cli.common.messages.CompilerMessageSeverity, java.lang.String, org.jetbrains.kotlin.cli.common.messages.CompilerMessageLocation, int, java.lang.Object)'

Execution failed for task ':app:kaptGenerateStubsDebugKotlin'.
> Internal compiler error. See log for more details

Anyknow knows how to solve this? (AS 4.2, Canary 8, Gradle 6.6, Gradle Plugin 4.2 beta Alpha 8, Kotlin 1.4.0, Compose 1.0.0-alpha01)

Is this the right way to use a ViewModel in compose?

@Composable
fun SearchMovie(viewModel: SearchViewModel, query: String) {

    val vm = remember(0) { viewModel }     
    vm.search(query)
    val state by vm.result.collectAsState()

    ...

Also is there a way to “assign” a

CoroutineScope

to a given

@Composable

function? My ViewModel does not inherit from the Android’s one, so I’m free to pass a Scope in the constructor and cancel it, but I’m not sure how to deal with a Composable’s life-cycle

just wondering as compose is now in alpha , still we need AS canary for this?

Ambients - why sometimes ambients are "registered" with the value directly and sometimes you pass a remembered state of the value? What's is the logic/meaning behind this? I thought that there is already a logic in ambient how to compare new provided value to the previous.

Material's Colors has all its fields as a state - documented as an optimization to when the color changes not to recompose everything, but only composables depending on the particular color. But I can't find any place that would modify any color. So is this a preoptimized for some user-land use-cases? And what they could be?

In the Layout Codelab I don't get this part

For example, if you wanted to add some outer spacing, change the background color of the composable, and round the corners of the ripple, you could use the following code:

specifically the "round the corners of the ripple". This is the code snippet they're talking about:

Row(modifier
        .padding(8.dp)
        .clip(RoundedCornerShape(4.dp))
        .background(MaterialTheme.colors.surface)
        .clickable(onClick = { /* Ignoring onClick */ })
        .padding(16.dp)
    ) {

We're not actually rounding the corner of the ripple, we're more so rounding the corner of the row, and so the ripple only goes up to the clipped area which gives you a rounded corner ripple... right?

Also, a

CircularProgressIndicator

inside an

AlertDialog

seems like it's not as smooth outside of it. I'll post a video of this + sample code in a few hours.

Layouts codelab; "Compose also comes with some predefined Material icons you can use, for example the close, favorite and menu icons." Does this mean my apk automatically includes all material icons? Or do they only get packaged in if I reference them in a composable?

I'd like to style my "components". Let's say I have specific color for my button. Ideally, I like to call

Button(backgroundColor = Color.MyColor)

, but of course, also content color has to be handled. Explicit passing of such seems to be pretty verbose, but there is not probably any way to modify contentColorFor() behavior for my color. Other options is to create own Button implementation but that's not much elegant.

Sure. I didn't mean to sound inaccurate. I will file an issue on Kotlin issue tracker as well.

Is there a way to make LazyColumn/LazyRow snap items after fling/scroll ended? If there was this would be a working view pager out of the box :)

This message was deleted.