How to render Html context in compose ?

VerticalScroller no longer has

onScrolledPositionChanged

, was it removed on purpose?

Slightly confused about

Shape

who performs the drawing? is there an example? I want to draw an oval shape (not a

CircleShape

which is based off

RoundedCornerShape

)

Hello there! At the Google I/O 2019, in Declarative UI Patterns talk,

asyncLoad

function is presented by speakers in one slide () but I don’t find this function in the latest artifact or in source code of Jetpack Compose. Someone can tell me if this function has been removed or if it is in development? Thanks in advance! 🙂

Hi, if I use a Spacer in SwiftUI without a height argument, the spacer takes all available space. Is there an equivalent in Compose? So if I have a Column, that has the following subviews: "HeightSpacer, Text, HeightSpacer, Text, HeightSpacer" the HeightSpacers should equally take the remaining space automatically.

how to convert

Dp

to

Px

is there any special helper yet with compose APIs ? 🙂

I am trying to make navigation drawer(sidebar) using

ModelDrawerLayout

. Now, I have some question regarding implementation. 1. Is there anyway to resize the size of navigation drawer. 2. Is there any way to navigate inside navigation drawer. Here navigate means if I tap on some item(inside navigation drawer) it navigate to sub-item inside navigation drawer. For example, there is setting item inside navigation bar if tap on it will navigate to sub-menu inside same navigation bar.

Just open-sourced my little playground app memset which will eventually be a memory card creator app (like flash cards) just working on the editor part and at some point will add the ability to persist cards and see them as a listing. I tried to do this before with commercial motivations but failed due to time (got many other hobbies and interests!) so this time round I am going to offer the source code as open so other folks can benefit from my failed projects 😆 https://github.com/fluxtah/memset (apologies no docs yet)

Secure your UI with Jetpack Compose is more easier than before ! https://ibrahimalii.github.io/Securing-UI-With-Jetpack-Compose/

Not sure what I am doing wrong here but newing up a

Color

for Green shows up as Red in

@Preview

and in emulator? apologies if this is a known issue

Hey folks not sure why this is happening, I have a vector that seems to draw over itself depending on how I structure my compose tree, I have two

@Composable

s, one

DrawVectorToggle()

and another version

DrawVectorToggleDRY()

The first one draws a toggle and toggles up and down fine but the second ones vector draws over the first state when toggled, anyone see anything wrong here in usage pattern that could be causing this?

Hi folks, can any one tell me what’s the difference between state and memo wrt to compose?

Morning folks, is there any way to detect clicks further up the compose tree? I have a child that toggles visibility of a local element, but I want the clicks on the root to cancel (basically a pop up box that when you click outside of the popup it will close it)

Can we expect some ambient functions like 'ambientOrNull' or 'ambientOrElse'?

Tangental but kind of related to the above ambient question - right now the docs for an ambient show an example of, like, getting a current user via an ambient. My gut reaction is that that's putting the wrong stuff into ambients and is better handled by some other caching layer, but I could be off base here. I think I like ambients (a lot) for styling or strings or size paramters and whatnot, and I think I like them a lot less for application logic. A user, for example, could (presumably) be correctly modeled as not existing in an application (before they're logged in for example), and trying to use an ambient for that feels like it sets you up for very surprising crashes at runtime when you realize you re-used some component that's using the user ambient in your logged out state. It's similarly difficult to handle in a default way without dramatically reducing it's utility - if all ambients need a default, you could have an ADT or something representing a logged in vs logged out user, or a nullable user, but now the components that actually want a user are forced into dealing with a lot of ambiguity. Honestly it's the same problem that plagues all of the cross cutting react APIs (Context, Redux, etc) in my opinion. You need some initial state for things, and a lot of stuff doesn't have a logical initial state that's not just "null".

Question - one thing I struggle with when writing Flutter apps is when to use what containing widget. There's stacks, rows, columns, containers, expanded widgets, center widgets etc etc. On the react native side, there's really only a view and then flex modifiers. It seems like compose is erring more towards the flutter style containment than the react/web style containment (though I'm aware of FlexColumn). I'd love to hear about what kind of discussion happened around that topic

Source documentation often mentions "Example usage: @sample androidx.ui.layout.samples.#####" Are these samples available publicly somewhere?

Is there a way to achieve baseline alignment of two Texts of different sizes in a Row? Right now they are top aligned, and Gravity.Bottom provided by Row doesn't seem to have any effect on the smaller Text when passed in as a modifier.

Does anyone have Room working with Jetpack Compose? The project compiles fine but when I try to run I get

java.lang.NoSuchMethodError:GenerationState$Builder.isIrBackend(Z)Lorg/

. I thought I saw a bug fix in the latest Android Studio release notes but I am still getting the error. Could someone please point me to a GitHub or other example where it is working? This a show stopper for us :- ( Thanks really appreciate everyone's help :- )

What's the right way to set a background color to a row? Currently I do:

Surface(color = Color.Magenta) {
  Row(modifier = Spacing(16.dp)) {
    // ...
  }
}

Is there any way to inspect the "view hierarchy"? I know there is no view hierarchy so to speak, as it doesn't use views, but is there some sort of inspectable representation of the Composable function calls and their arguments used to render the UI? I'm asking chiefly programmatically, but I'm also wondering if a future version of the layout inspector will support Compose?

I'm trying to create a VerticalScroller that remembers its position when the page is redrawn - I've tried

val scrollerPosition: ScrollerPosition = +memo { ScrollerPosition() }
VerticalScroller(scrollerPosition) {
  // etc.
}

but it scrollerPosition.value always seems to be 0px

VerticalScroller

is not working properly with

ModalDrawerLayout

When

drawerContent

data wrap around verticalScroller whole view moves to center. I had tried to incoperate the samething in

jetnews

app. Updated the

AppDrawer

function

@Composable
private fun AppDrawer(
    currentScreen: Screen,
    closeDrawer: () -> Unit
) {
    VerticalScroller() {
        Column(modifier = Expanded) {
            HeightSpacer(24.dp)
            Row(modifier = Spacing(16.dp)) {
                VectorImage(
                    id = R.drawable.ic_jetnews_logo,
                    tint = (+MaterialTheme.colors()).primary
                )
                WidthSpacer(8.dp)
                VectorImage(id = R.drawable.ic_jetnews_wordmark)
            }
            Divider(color = Color(0x14333333))
            DrawerButton(
                icon = R.drawable.ic_home,
                label = "Home",
                isSelected = currentScreen == Screen.Home
            ) {
                navigateTo(Screen.Home)
                closeDrawer()
            }

            DrawerButton(
                icon = R.drawable.ic_interests,
                label = "Interests",
                isSelected = currentScreen == Screen.Interests
            ) {
                navigateTo(Screen.Interests)
                closeDrawer()
            }
        }
    }
}

Hello, I have a question about @Preview annotation. Why we need to it for seeing preview version of the code? Should it be the default for our screen? In my opinion, We should see a preview of every composable function in setContent.

any simple to understand animation examples yet? 🙂 I did some digging but nothing clicked so far, I see the cross fade anim and some infrastructure just need a nudge in the right direction

Hey, I was experimenting with Transition API and noticed that there's no way to check if user specified a key in transition definition or specify defaults. Do you plan to add support for it later? Example:

val X = FloatPropKey()
val Y = FloatPropKey()

val def = transitionDefinition {
    state(Initial) {
        this[X] = 0f
    }
}

Transition(definition = def, initState = Initial) { state ->
    val xValue = state[X]
    val yValue = state[Y] // <-- Crashes, as no value specified
}

Is there a resource for developing a custom widget? I can’t seem to find anything concrete as a baseline to use

I am implementing

BottomSheet

using

BottomDrawerLayout

but in doc it written that bottomDrawer is only used with bottom app bars. So, Is it okay to make bottomSheet using BottomDrawerLayout ?

Have another question, is there a way to show the widget bounds in a similar fashion to “Show layout bounds”?