Any idea why the

FlexColumn

compose the 2

Text

in a row instead of a column?

this is broken for us to atm. someone working to fix it now

Ok, I got another weird scenario with `Ripple`s, but it’s someway complex to explain - and I don’t want to copy-paste that much code, who can I get in touch with?

Will this be

suppressed

by default for

@Composable

functions?

I tried searching but didn’t find anything that helps and I’m confused. Should I expect the views to change/recompose when passing

@Model

into another

@Composable

function? Something like:

@Composable
fun App() {
    val appState = +memo {
        ParentModel(
            listOf(
                ChildModel("Item 1", false),
                ChildModel("Item 2", true)
            )
        )
    }
    Column {
        appState.childModels.forEach { item ->
            Item(item)
        }
    }
}

@Composable
fun Item(item: ChildModel) {
    ListItem(
        text = { Text(item.description) },
        trailing = {
            Checkbox(
                checked = item.checked,
                onCheckedChange = { item.checked = it })
        }
    )
}

@Model
data class ParentModel(
    var childModels: List<ChildModel>
)

@Model
data class ChildModel(
    var description: String,
    var checked: Boolean
)

?

Another question: when I’m quickly adding items to a

ModelList

, they are being added out of order, that is when I add items slowly I have e.g.

1, 2, 3, 4, 5

. But when I click button to add them fast, I end up with

0, 4, 3, 2, 1

. Even when I try explicitly adding the item at position

list.size

. The same happens for an immutable list. Is this because mutating the state doesn’t guarantee order of the mutation? Is there any way actually have the changes applied in order?

Compose artifacts updated to 0.1.0-dev02 https://androidx.tech/updates/2019-10-22-compose-update/

0.1.0-dev02 seems to break my Compose demo app, so there's definitely been some significant change somewhere

No direct method <init>(Ljava/lang/String;Lkotlin/jvm/functions/Function0;)V in class Landroidx/compose/Ambient; or its super classes

I have a question about modifiers: right now I see the only handled

Modifier

type is a

LayoutModifier

, which, if I understand correctly, is read and applied in the

LayoutNode

in appropriate place. I know there’s been a discussion about the scope of modifiers, but in the end there’ll be just some number of modifier types handled by the core library in appropriate places, right? Could you share what other possible types of modifiers were you thinking about in general, not necessarily ones that are likely to be part of Compose?

There are no such items in AS 4.0 Canary 1. 🙂

Is AS 4.0 a new thing? I just saw happened to see it today

I'm really interested in Compose, but I currently represent all my data (model) as immutable data. I use

Flow<T>

for this. Every instance of

T

is immutable all the way down, which has a bunch of advantages.

@Model

seems to require use of

var

So who will be the first one to ship Compose to play store 🤔

I hope compose is gonna kill fragments, that was really a mess

Compose can't possibly work with the new MotionLayout animation editor right?

@Preview
@Composable
fun Greeting(name: String = "Android") {
    Text (text = "Hello $name!")
}

Would the preview work by using default values?

It seems like Jetpack Compose is much similar to writing UI in Flutter.

@Preview

annotation is actually pretty cool in terms of documenting your UI components library. Good job! Any plans to have a Library tab in Android Studio, similar to ResourceManager, where I could see all of my components annotated with

@Preview

? It would be super cool to have this kind of visual reference of the project guidelines

Suggestion: What if there is a preview button (next to @Composable functions) in the gutter just like Run button in psvm?

1 👁️ | @Composable
2    | fun Greeting(name: String = "Android") {
3    |    Text (text = "Hello $name!")
4    | }

Will the

+

thing for effects be removed? Back then you were saying it's gonna go away.

Theoretically, will Compose be compatible with how companies are defining "Design Language" components and shipping as internal libraries?

I don't seem to be getting a live preview? 😕

So we don’t need to use AndroidStudio bundled with Compose anymore?

It uses layoutlib that's already used by the visual editor

With jetpack compose, how do we access things like view insets, context, etc?

In order to get the live preview, do you have to have something with the @Preview annotation?

Has anyone gotten a

FloatingActionButton

to display an image yet? I feel like I’m missing something very simple…

val resource = +vectorResource(R.drawable.ic_baseline_add)
        FloatingActionButton(icon = resource) // takes an Image instead of Vector, how does one convert a Vector to an Image with Compose?

Would the issue tracker be a good spot to make requests? I was hoping to do something like this:

@Model
class Name(var name: String = "Android") : ViewModel()

But inheritance isn’t currently supported for Model objects. We currently use LiveData a lot today but with Compose it seems like unnecessary overhead.

Ah gotcha,

+observe

isn’t quite I was hoping for, making the entire ViewModel observable with

@Model

was more what I was hoping for. I don’t think

+observe

currently exists as part of the Canary build either? Android Studio at least can’t recognize it on my end. I’ll try to stop by the office hours tomorrow to talk it through a bit more. Thanks again for all of the help and sorry for bugging ya at 10:30 at night 😅

Guys, great work on the progress. It's great to see that our feedback is actually being listened to. Quick question. Where is it better to write compose functions? In a class or a file?