there is a lot of material from those ecosystems around the mental model and patterns/practices that i think would be useful to learn and think about if you’re interested

i could link a few articles or videos from some folks if that seems useful

since material coming from us is still fairly… light 😉

ScrollingList is very interesting functions

With Compose we bring a lot of mutability to our code, are we think about an official kind of unidirectional data flow api to work with compose?

Anyone succeeded in creating a custom component? I tried to create tab layout but I'm facing an internal code analysis compilation error. Is there any task that I should run to find the proper error?

If that doesn't solve it, you're likely running into a limitation of either the IR compiler or the Compose plugin

Is there a list of currently available composables?

When you write the wrong parameters, you get a confusing error message in the composable about mismatching parameters. It would be more helpful if the error is directed at the mismatching parameter. The problem here is that

textStyle

should actually be

style

. The image illustrates the feedback given in Compose in the upper case, and the feedback given in Flutter in the bottom case.

Remember it's still a work in progress :)

Of course

Tooling is something we want to get right but we're still working on some of the fundamentals

Also recent changes in syntax made the editing experience not as good as it used to be

You mean the change from xml-like?

yeah - we had a lot more time to get the xml syntax ide experience right, and haven’t spent near as much time on the current syntax.

Is there a way to navigate between composables right now? Doing something like this:

@Composable
fun MyApp() {
    val currentWidgetState = +state { root }
    val currentWidget = currentWidget.value
    MaterialTheme {
        GenericWidget(currentWidget, onOptionClicked ={currentWidgetState.value = it} )
    }
 }

was not welcomed by the framework.

what is the type of

currentWidget

here?

It's just a data class, I simplified my case a little

full code https://pastebin.com/FdpCra4a

you’re doing this

when(currentFile){
            is Folder ->  FolderWidget(currentFile,onFileClicked ={currentFileState.value = it} )
            is TextFile -> TextFileWidget(currentFile)
        }

which should work fine. are you asking how to make something like your

GenericWidget

?

It's not working. I should probably make a more cohesive explanation

I made a bug report regarding it @Matej Drobnič https://issuetracker.google.com/issues/133064200

Constraint/MotionLayout: yes

The analog to LayoutParams is receiver scope functions that accept composable lambdas used within a layout block

You can see this in action with things like FlexRow so far

Is there some kind of navigation function to navigate to a new screen and back ?

Can Flutter's documentation be a good source for best practices for now?

See my earlier response in the channel for more details, but short answer is yes, with quite a few things that need to be decided (static declaration vs DSL, or both, etc). We want to maintain tooling support as well as possible.

Is there going to be pre-built versions of JetPack Compose made available to manually include via Gradle?

No.