about SwiftUI, no more of IB?

This message was deleted.

Swift uses structs, react native and flutter use classes, compose uses functions.

Text("Hello World")
         .padding()

Seems nicer than

Padding {
            Text("Hello World")
         }

I have to be honest.

I wonder how Google predicts it before Apple 😋

This message was deleted.

The syntax is already quite similiar

https://kotlinconf.com/workshops/

Then we'll explore Jetpack Compose, a Kotlin native UI toolkit for Android. You'll learn how it fits together with your existing architecture to build reusable UI components. Built with a goal of integrating with your existing code we'll take a look at how to combine Jetpack Compose with Android views. We'll also cover some best practices for how to use Jetpack Compose!

So I guess by December there will be alphaish release of Jetpack Compose?

also the fact that the order matters on them is a bit worrisome to me

I’d rather introduce a new primitive into the language (😱) that provides for this kind of composition but without nesting of curly braces. We run into it all the time even without compose. Instead of:

fun foo() = logged { transactional { ... } } // (1)
Padding(color=my) { OtherWrapper { Component() } } // (2)

It would be preferable to be able to write:

fun foo() = logged <compose> transactional { ... } // (1)
Padding(color=my) <compose> OtherWrapper <compose> Component() // (2)

The trick is what

<compose>

sequence of characters is. It is extremely hard to find a syntactic form that is readable and understandable, looks nicely, and is not ambiguous with all the current and potential future extensions of Kotlin language. Ideas are welcome, use a thread please :thread-please:

Actually, we’ve been playing with SwiftUI and some snapshot testing and that nesting syntax is what’s using under the hood:

struct ContentView: View {
    var body: some View {
        Spacer().padding()
    }
}

Is transformed into

▿ _ModifiedContent<Spacer, _PaddingLayout>
  ▿ content: Spacer
    - minLength: Optional<CGFloat>.none
  ▿ modifier: _PaddingLayout
    ▿ edges: Set
      - rawValue: 15
    - insets: Optional<EdgeInsets>.none

The upside is that people skilled in reading SwiftUI code will boost their reverse Polish notation reading prowess and mental stack capacity and they’ll soon be able to fluently program in Forth!

anyone here from the flutter team? I wanna hear their thoughts as well 🙂

Interesting benefit of the

tapAction

modifier in SwiftUI.

Text("hello")
.tapAction { println("tapped") }

Over

Clickable(onClick = { println("tapped") }){
     Text("hello")
}

You get

{ println("tapped") }

over

(onClick = { println("tapped") })

Text("/(capacity) people")

is translatable

Will this bring any performance improvement to rendering, measuring and layout phases or will just skip the xml parsing or the performance improvements are likely to come when the UI composing will be truly multi-threaded.

the on-device developer setting? I forget exactly what that keys off of, assuming it's readable as public api I see little reason why we wouldn't key off of it in debug modes or something. If you mean some of the new tooling in android studio, we already have plans there yes

Hi!, Jetpack Compose makes use of extensions such as

org.jetbrains.kotlin.extensions.TypeResolutionInterceptorExtension

in its component registration. I looked in Github and there are no such extensions in the Kotlin Compiler master branch. Where are those extensions coming from? Is there a list of available extensions available? Thanks.

Are there instructions to build jetpack compose in a dev machine? I’d like to learn and contribute since I’m getting involved with compiler plugins as well but I have not found a way to build the

support

repo or the subset of jetpack compose which is the one I’m interested in. Any help is appreciated, thanks.

I am trying Jetpack Compose and I have tons of questions and bugreports 🙂 What is the idiomatic way of having the colored background? Just Surface with color property?

Second: What about text input? EditableText doesn't seem like a component to provide proper input(if text is an empty string you can't even start typing)

Hi! How can I contribute to Compose? Is there a public issue tracker where I could take some tasks from?

Any plans on having a preview for Composable functions in AS ?

Also, why root surface is expanded on a whole screen while surface enclosing say an EditableText does not?

How do I access android Context in the Composable? Or I should pass all such code as properties?

yep