Do you prefer 2 or 4 spaces for Compose files? Or don't care?

4 spaces is always the answer :)

Flipping it on it's head to have this Idea for theme synchronization between Android XML Themes & Compose: • Apply Compose (Kotlin Defined) styles upon Existing Android Views. This could be done by extending the current View set to make AndroidX.Button.ComposeThemed or something? You would force attributes of your Compose Defined Theme in that Android View programmatically and ignore existing style attributes. It seems like a nice way to start defining styles in Kotlin, and slowly migrating existing widgets over to use those styles. Thoughts?

Hello, i'm using 0.1.0-dev13 version of the compose, is there a version of

Seekbar

in it?

SeekbarPreference

is deprecated now

How can I align elements in a row, such that one element is centered and the other is attached to the right? The following solutions do not work:

Row(horizontalArrangement = Arrangement.Center) {
            Text("Center")
            Text("Right", modifier = Modifier.fillMaxWidth().wrapContentWidth(Alignment.End))
        }

Row(horizontalArrangement = Arrangement.Center) {
            Text("Center")
            Spacer(modifier = Modifier.weight(1f))
            Text("Right")
        }

As in both cases the

Center

element will get attached to the left. The desired behavior is in this image:

Hey, how can I stop a view from being recreated on recomposition using AndroidView with the resId parameter?

It seems like text input is lagging behind

How can I make an Icon visibly bigger? I've tried various size modifiers (preferred, width, height, size, etc) but they only make the icon take more space, and the icons stays just as small.

Icon(Icons.Rounded.Search, Modifier.padding(8.dp).preferredSize(60.dp)) // Actual icon size looks around 30dp

How to give views an absolute position (want to plot dots on a small graph, for which I'm using

Box

/ shapes)?

That’s quite disappointing, is there anything I can do to make Compose aware of the inside of an object ?

Leland and Adamp (dont want to ping here on a Sunday morning) would know

Let’s say I have a simple app with a bottomBar and two tabs, each showing a list of items. What would be the right thing to do for opening those items? A new activity? A new screen + hiding the bottomBar with an animation? in Jetnews there is no bottomBar in the first screen, so it feels easier to just change the screen..

Slider

doesn’t follow the

steps

and lets me drag it all over. Is this a known bug? Is the main issue tracker the right place to report issues on material design compose lib?

I get it is early times still in the world of jetpack compose, nevertheless I have a notion that it is not too early to raise the topic of code coverage for compose code. What would it take to get either an IntelliJ or a Jacoco coverage report for the JetNews sample app? The IntelliJ path did not look promising so I am about to explore the Gradle/Jacoco path.

apparently JB is planning to make compose a crossplatform UI solution https://old.reddit.com/r/androiddev/comments/hufnjq/jetbrains_is_porting_compose_to_desktop_and_other/

Hey everyone! What seems to be the encouraged alternative between

Modifier.foo() + Modifier.bar()

and

Modifier.foo().bar()

?

Is there a way to constrain an element absolutely, without letting it relayout itself to fit within the available space? The use case is to create a component that can swipe between different screens. (I already have it implemented, but the children keep moving around as they're getting constrained) This image illustrates the idea:

So Compose is a collaboration between Google and JetBrains? I thought it was only the Android team.

I wonder what would be the best to prepare for Compose. I know we have like a year / year and a half till 1.0, so it gives us devs plenty of time to prepare at our ease. I guess a good separation between data loading and UI would be nice. I am sure apps created more than 3 or 4 years ago aren’t there yet.

I dare say that since it's related to Android Studio 4.2 then when that version is ready compose will be ready too

What about Portrait vs Landscape with Compose ? Are we just going to build two Composables? What about tablets?

Consider the following code

Column {
        var on by state { true }

        Button(onClick = { on = !on }) {
            Text(text = "Toggle", style = textStyle.h1)
        }

        val list = @Composable {
            LazyColumnItems(items = listOf(1, 2, 3, 4, 5, 6, 7, 8, 9, 10)) {
                Text(text = it.toString(), style = textStyle.h1)
            }
        }
        if (on) {
            list()
        } else {
            list()
        }
    }

Here we have a scrolling list, with a button above it, that seemingly, does nothing. However, it doesn't - it resets the current scroll progress in the scrolling list. I have a feeling this is the intended behavior (unfortunately). I have a less trivial case where the same list is being used at multiple places, but it loses its scroll progress when it gets invoked through a different branch of code. It might be possible to somehow structure the code such that only one invocation occurs, but I find that difficult. Is there some way to make compose understand this is the same list?

Is there a tutorial or a page for localization with Jetpack Compose?

I found using dev14. There is a big ripple to the FilledField when clicked. And I can grab the label to copy the text. Are those actions expected already?

setContent {
            MaterialTheme(
                colors = lightColorPalette(
                    background = colorResource(id = R.color.loginPageBackgroundColor),
                    primary = colorResource(id = R.color.colorPrimary),
                    primaryVariant = colorResource(id = R.color.colorPrimaryDark),
                    secondary = colorResource(id = R.color.colorAccent)
                )
            ) {
                Column(
                    modifier = Modifier.fillMaxSize(),
                    horizontalGravity = Alignment.CenterHorizontally,
                    verticalArrangement = Arrangement.Center
                ) {
                    var text by savedInstanceState { "" }

                    FilledTextField(
                        modifier = Modifier.fillMaxWidth(),
                        value = text,
                        onValueChange = { text = it },
                        label = { Text(text = "Username") },
                        keyboardType = KeyboardType.Email,
                        imeAction = ImeAction.Done
                    )
                }
            }
        }

Where does Compose stand about Material Motion? https://material.io/design/motion/the-motion-system.html I love the look of those transitions 😍

Hey everyone! For the last few weeks I've been working on a material dialog library for compose which provide the basis and common components for building a material speced dialog. This includes things such as single and multi-selection lists, date and time picker and a colour picker. I'd love to get some feedback on it and I'm open to any suggestions for other common dialog components that should be implemented. https://github.com/vanpra/compose-material-dialogs

Hi folks, I'm here again. This time with a vector drawable not rendering correctly. I'm re-learning Compose porting this codelab: https://codelabs.developers.google.com/codelabs/mdc-101-kotlin/#0

Image(asset = vectorResource(id = R.drawable.shr_logo))

In the picture we can see Shrine logo rendering filled instead the path. PS: the logo that is not rendering correctly. Others are rendering fine. compose:

0.1.0-dev14

Do we have a Composable for bottom bar with a cradled fab like this one -> https://material.io/develop/android/components/app-bars-bottom ?

Why are

MutableState<T>.setValue

/

MutableState<T>.getValue

extension methods instead of instance methods? This creates some confusion for me when I write

by state{}

and it errors, and I need to use the import quickfix.

Is Compose prone to problems similar to which a deeply nested Android ViewGroup suffers? I mean double layout taxation, slow measure/layout phases, etc. On Android, we always tried to build a flat view hierarchy, without deep nesting or weights. And what with Compose?