Hi guys, anyone trying to port compose to KotlinJS like what the developer from kotlin-libui is doing?

Is there a modifier that does something like

WRAP_CONTENT

?

Just few questions regarding compose 1. Are there any plans to release composables that implements the same behaviour found in recycler views and view pagers? For curiosity reasons, what is the development status of ScrollingList that was shown on code snippets at Android Dev summit last year? 2. Are there any plans to add support for Lottie style animations? In other words, implementing a composable that can render animations defined in Adobe AfterEffects json file. 3. I understand that view models are scoped to the lifecycle of their Lifecycle owners such as Fragments and Activities.  However, is there a possibility that you add support for scoping ViewModels to lifecycle of composable functions. I am asking this question because it feels so cumbersome to initialise a ViewModel inside an activity then pass down its reference to a composable function in order to call functions inside the view model that fetches data. 4. I have find it impossible to arrange items in a Column or Row with Arrangement.Begin for example to place them at the beginning of main axis but still define fixed spacing between the items to space them evenly without having to manually put Spacers between the items. The problem with SpaceBetween, SpaceEvenly, SpaceAround is that it distributes the items over the main axis based on the width or height of the screen especially when the column is root of a composable. Take a look at the example below. If I want to arrange children of a Column to the beginning but still space them evenly, I have to end up writing this boilerplate code of putting spacers between items.

Column(modifier = LayoutPadding(16.dp), arrangement = Arrangement.Begin) {
  Text(text = "Klaas", style = MaterialTheme.typography().body1)
  Spacer(LayoutHeight(12.dp))
  Text(text = "James", style = MaterialTheme.typography().body1)
  Spacer(LayoutHeight(12.dp))
  Text(text = "Tom", style = MaterialTheme.typography().body1)
  Spacer(LayoutHeight(12.dp))
  Text(text = "Martin", style = MaterialTheme.typography().body1)
  Spacer(LayoutHeight(12.dp))
  ColoredRect(color = Color.Red, modifier = LayoutWidth.Fill, height = 200.dp)
}

Can’t we have something like this where we can arrange the children of a layout to the beginning but still give the fixed spacing to spaces them evenly without having to put spacers between the items.  

Column(modifier = LayoutPadding(16.dp) + ChildSpacing(16.dp), arrangement = Arrangement.Begin) {
  Text(text = "Klaas", style = MaterialTheme.typography().body1)
  Text(text = "James", style = MaterialTheme.typography().body1)
  Text(text = "Tom", style = MaterialTheme.typography().body1)
  Text(text = "Martin", style = MaterialTheme.typography().body1)
  ColoredRect(color = Color.Red, modifier = LayoutWidth.Fill, height = 200.dp)
}

is

ContextAmbient

always activity? I need to get at the activity to silently get a

ViewModel

behind the scenes using

ViewModelProvider

fun getModel(): MyViewModel {
        val context = ambient(ContextAmbient) as AppCompatActivity
        return ViewModelProvider(context).get(MyViewModel::class.java)
    }

WIP

Does

@Stable

annotation on the composable functions within the framework mean the composable functions are stable and not subject to change? Is that right ?

I watched a talk by @Leland Richardson [G] where he was explaining how the compositions are handled using the Gap Buffer, how positional memoization and recomposition works in compose. It was quite interesting. Now my question is that are the compositions under the scene happening on a single thread(i.e. Main thread) or do you guys runs them on multiple threads to speed up the whole process?

Is there an equivalent of

CrossAxisAlignment.Center

for Row as was in FlexRow in dev04?

Just reading through the

AdapterList

PR, excited to see this start to take shape. I believe Flutter implements their lists on top of a fairly complex “sliver” API which they also use to implement things like fancy Material collapsing AppBars ala

CoordinatorLayout

. Does the Compose team have any thoughts about how to implement collapsing app bars with Compose? (The AdapterList PR is here: https://android-review.googlesource.com/c/platform/frameworks/support/+/1218839)

I'm getting this exception:

java.lang.IllegalArgumentException: LayoutNode@dcd3e1b children: 1 measureBlocks: MeasuringIntrinsicsMeasureBlocks@cccb17f{ measureBlock=androidx.ui.foundation.ScrollerKt$ScrollerLayout$1$2@876754c } shouldn't require remeasure. relayoutNodes consists of the top nodes of the affected subtrees

when trying out

HorizontalScroller

and

BottomDrawerLayout

. Any thoughts of what might have caused this? I basically put 2 sample code together.

Its not happening all the time but its when toggling a model boolean property which in turn recomposes part of the UI, in my little card app if you click on a card it recomposes to toggle to the back or front of the card, I was repeatedly clicking it when this happened

does anyone know how to do the equivalent of

layout_weight

in a

Row

in dev04?

How one should structure a new android project with the hope of migrating to Compose later in order to make migration smoother as possible? MVVM, MVI, BLOC? @romainguy

Composing fun 😆 not that proud of my code though still, it looks cool

Before begin using me precius time... can Room and Compose coexist in dev04 ?

Will there be a way to debug previews in future release? 🙂

Is there any workaround to make

Room

run in a Compose project?

Is

LayoutHeight.Fill

in dev04 the proper replacement for

ExpandedHeight

in dev03?

also, should we use @Model or +state?

👋 I have a question about a potential onion architecture using jetpack compose. • A single activity with a composable view containing the whole application • Each screen is a composable fnuction • Navigation is done by a `androidx-architecture:navigation-compose`implementation In a nutshell: In our current architecture, we are using fragment to handle each screen, and each fragment have a viewmodel to retain it’s state and call the core layer made of use cases and repositories interfaces (implemented in the data layer). Fragment’s view model are scope by their fragment lifecycle so use cases are disposed when needed (using

viewModelScope

) Is a composable screen going to expose a scope so that we’ll be able to provide a ViewModel associated with such a scope ?

is there any way to use compose with a webview?

Is there something new to consider using

DoubleTapGestureDetector

with

dev04

this seemed to work but now it won't 😞

Clickable(onClick = { onClick(element) }) {
            DoubleTapGestureDetector(onDoubleTap = { onDoubleTap(element) }) {
                when (element) {
                    is TextElement -> TextElement(
                        element,
                        isSelected,
                        isEditing
                    )
                    is ShapeElement -> ShapeElement(element, isSelected)
                    is PianoRollElement -> PianoRollElement(element, isSelected)
                }
            }
        }

anyone already tried to use Glide together with jetpack compose?

It seems closures is used a lot in Compose, for example onClicks and childrens. Because they are created each time when a composible function is called, so they are not equal to the previous closure. So does it cause unnecessary compose? Are there plans to address this (like comparing captured variables)?

Is there any documentation out on how compose handles state saving (for both configuration changes and process death)? I'm mostly curious about various state objects that are arbitrary classes and thus cannot be parcelized into saved state bundle.

What is Ambient and ContextAmbient

so does MaterialTheme point to your current app theme or to some ready made default theme?

As of at least dev04 (haven’t tried earlier), it looks like

Clip

isn’t doing anything. I can implement

DrawModifier

and manually clip the canvas before drawing the children, and that works, but

Clip

doesn’t seem to have any effect whatsoever. Is this a known issue?

Is WearOS first-class support planned for Compose once the API stabilizes?