Hi ya'll. Alas - I've been looking but can't find it. What is the Compose function for an editable text box?

Has anyone started working on something like 'Flutter Gallery' but for compose ? Or maybe just listing the available

@Composable

components ?

dev05 coming out anytime soon? I'm still on 03 and not sure if it's worth to upgrade at this point cus it's been a while since 04 came out

ok - I found TextField, but is there any Compose equivalent for the material design TextInputLayout https://material.io/develop/android/components/text-input-layout/ ? i.e. a text field with all the hint/border/background goodness? Stuff like: https://material.io/components/text-fields

Hey everyone, I'm just getting started with Compose. Is it possible to start with transforming one view of an existing codebase into a Composable and somehow use that within the old UI system?

Hi ya'll my app in coming along nicely, I should have an early ugly version up on github this week. Another noob question (because I'm cribbing from jetnews). What is the dev04 equivalent to the following removed modifier?

/**
 * A layout modifier that forces a target component to fill all available width.
 *
 * Example usage:
 * @sample androidx.ui.layout.samples.SimpleExpandedWidthModifier
 */
val ExpandedWidth: LayoutModifier = object : LayoutModifier

this is a lot of fun.

btw - will the JetNews app (which seems to be the most complete example out there) be getting updated to dev04/dev05?

I really hate to ask your guys about the Material Components Support.

I am trying to render html page using androidview but getting this error while importing the dependancy.

ERROR: Failed to resolve: androidx.ui:ui-android-view:0.1.0-dev04

Hmm - it seems the cursor in TextField is always black (rather than being white if using a dark palette). Also it doesn't seem to blink. Am I doing something wrong?

TextField(
    value = message.value,
    onValueChange = { message.value = it },
    textStyle = TextStyle(
        color = colors.onSecondary.copy(alpha = 0.8f)
    ),
    imeAction = ImeAction.Send,
    onImeActionPerformed = {
        <http://MessagesState.info|MessagesState.info>("did IME action")
    },
    modifier = LayoutPadding(4.dp)
)

A question on modifiers "

Modifier elements may be combined using `+` Order is significant; modifier elements to the left
* are applied before modifier elements to the right.

Does the last applied operator override previous modifers of the same type? i.e. if I have something like lA = LayoutSize(...) lB = LayoutSize(...) modifer = lA + lB Is this doc saying that lB will be the layout size for the modifier?

Is this the preferred way to merge TextStyles (in this case picking a standard style and then bumping down the opacity)?

Text(
    text = "9:49 AM",
    modifier = LayoutPadding(left = 8.dp),
    style = MaterialTheme.typography().caption.merge(
        TextStyle(
            color = palette.onSecondary.copy(
                alpha = 0.2f
            )
        )
    )
)

If so, what about letting TextStyles have an + operator to make their usage more similar to Modifiers?

I'm having a hard time figuring out how to have items inside a column expand to fill most of the available space. How do I say: I want the first item in the column to get most of the space, and the second item to get only a little space? I've tried LayoutSize.Min, but it seems Fill always just covers everything - rather than taking what it can get? i.e. my layout looks like:

fun MessagesContent() {
    Column(modifier = LayoutSize.Fill) { // want to fill entire screen
        Column(modifier = LayoutSize.Fill) {             
             messages.value.forEach { // I want this list of messages to fill most of the view
                MessageCard(
                    it, modifier = LayoutPadding(
                        left = sidePad,
                        right = sidePad,
                        top = topPad,
                        bottom = topPad
                    )
                )
            }
        }

        Surface(
            modifier = LayoutPadding(8.dp) + LayoutSize.Min(40.dp, 40.dp),
            color = backgroundColor,
            shape = RoundedCornerShape(4.dp)
        ) {
            TextField(
               ...
            )
        }
    }
}

I am trying to implement a deck of cards whereby I want to rotate the topmost card in the deck at 20 degrees. I have added a Draw composable to the current Stack composable code to do the rotation but the issue is that the Draw composable rotate all the children not only the topmost. How do you tell the Draw composable which child to rotate in layout?

Trying to learn Compose. I see lots of samples people have written using

…, style=+textThemeStyle

but cannot for the life of me figure out what

textThemeStyle

is. There’s a Github project I found that suggests it’s in

androidx.ui.material

but I don’t see it there for me. Probably something that was removed/deprecated-and-removed. What is it replaced by? I have one of my

Composable

functions wrapping a

Scaffold

with

CustomTheme

, and inside there I want to style a

Text

with a

Typography

defined inside the

CustomTheme

.

have any example with calls to api with compose?

I’m curious - I know the compose team has talked about releasing some parts of compose as multiplatform libraries separate from android, in the future after we have something stable for compose. I remember the tree analyzer was specifically mentioned around this. Was anything else discussed? Can anyone speak to how close that would get us to a compose api across multiple platforms?

Hi guys, I'm getting this exception when I try to run the app using Compose, anyone knows this exception and why could be the cause?

Where are the samples mentioned in the source code? For instance, in

Flex.kt

, part of

androidx.ui.layout

the doc comment block above

fun Column

says

@sample androidx.ui.layout.samples.SimpleColumn

, but I cannot locate that in the package or the source or anywhere googling that string.

Hi folks :) I'm looking for documentation related to dev03 -> dev04 changes. Thank you in advance!

Compose app crash with error

java.lang.IllegalStateException: Current layout is not an ancestor of the provided child layout

Note: It is occuring only sometime and most of time it is working with no issue

I’m trying to add compose to my app (currently using databinding) .. but it not compile.. can I have compose and databinding running side-by-side? (Maybe kapt is the main problem)

Hello! The Jetpack Compose dev05 drop has just been released as part of our new continuous release model and you can get it now on Google’s Maven Repository. Release notes are available at https://developer.android.com/jetpack/androidx/releases/compose and https://developer.android.com/jetpack/androidx/releases/ui. Please note that the majority of the documentation including codelabs, tutorials, and samples will only be updated for major releases. Feedback is always welcome; please log issues at https://issuetracker.google.com/issues/new?component=612128!

Will the next release after 0.1.0-dev05 be alpha?

Looks like right now we are not getting 60fps, phone Pixel 2 XL.

@Leland Richardson [G] Can you confirm if I understood the content of your presentation very well () . May you point out any knowledge gaps in my understanding and help me in understand this better. The

@Model

annotation will make the count property inside the

LabelState

data class observable which in turn gives it the ability to trigger recompositions on subsequent mutations.

@Model
data class LabelState(var count:Int)

Sample 1: Composable functions are positionally memoized meaning the inputs to composable functions, and their corresponding outcome resulting from composable functions calls are cached to avoid unneccessary recompositions when a composable function is called with the same inputs multiple times. In case where a composable function is called with the same inputs multiple times, compose runtime will check against the Slot table whether the same inputs have corresponding outputs that were previously cached. If yes, then the compose runtime will retrieve the previously cached results otherwise insert new inputs and their corresponding results to the Slot Table. Given that understanding, it means that the

LabelState

passed as input parameter to a composable in the following code snippet will be positionally memoized despite that is is not wrapped inside

remember

composable. Did I understood this correctly? If yes, then is this only applicable to situations where the state is hoisted? - in other words passed down the composable hierarchy from the owner to called composable functions?

@Composable
fun LabelThatPassStateAsParameter(labelState: LabelState){
    Text(text = "$labelState.count",
         style = MaterialTheme.typography().body1)
}

Sample 2 Alternatively, when the state is not passed as input to composable function, it can be obtained by a keeping a local variable that references the state by calling composable function such as

state

or a combination of

@Model

class wrapped inside

remember

composable as in code snippet below.

val labelState = state {0}

is equivalent to

val labelState = remember { mutableStateOf(0) }

where both does referential equality between old and new value to prior to mutation of state.

@Composable
fun LabelWithStateComposableThatDoesReferentialEquality(){
   val labelState = state {0}    
   Text(text = "$labelState.count", 
        style = MaterialTheme.typography().body1)
}

Otherwise if you want to do structural equality on state mutations, you can possible achieve by through the following. val

labelState2 = remember { LabelState(0) }

is equivalent to

val labelState2 = remember { mutableStateOf(value = 0, areEquivalent = StructurallyEqual) }

where both does structural equality between old and new value to prior to mutation of old state value.

One of the exciting project that we are currently working on which is built completely with compose. It is still in early stage development and will be probably be ready for going live once compose reaches its production ready stages.

Dear compose geeks. I know you said don't use this project for anything shipping, but just FYI - here's a hobby project that is using it for something shipping 😉. Don't worry - I'll keep updating to your newer builds and if needed (because ya'll decide you need to bail) it wouldn't be too painful for me to decomposemotize my app: https://www.meshtastic.org/

does anyone have any working samples of testing composable functions? im getting

E/TestRunner: java.lang.RuntimeException: Could not launch activity

when I attempt to use

createComposeRule()

. or am I trying to use something that isn’t ready?

@RunWith(JUnit4::class)
class SampleTests {

    @get:Rule
    val composeTestRule = createComposeRule(disableTransitions = true)

    @Test
    fun twoComponents_areChecked() {
        composeTestRule.setContent {
            MaterialTheme {
                Surface {
                    Column {
                        Checkbox(checked = true, onCheckedChange = null)
                        Checkbox(checked = true, onCheckedChange = null)
                    }
                }
            }
        }

        findAll(isOn())
            .assertCountEquals(2)
            .forEach {
                it.assertIsOn()
            }
    }
}

I still think I'm doing something wrong with the drawables, or there is a bug