Won't we get some context into each composable fun...

# compose

[Michal Bacik]

Won't we get some context into each composable function? Current View has Context which allows to load resources (strings, images), read configuration or even get Application object. Now I wonder if similar context may be there automatically, or we must pass it ourselves as paramater?

[Luca Nicoletti]

https://kotlinlang.slack.com/archives/CJLTWPH7S/p1572098323479400?thread_ts=1572096397.476100&cid=CJLTWPH7S

[Michal Bacik]

Interesting. Thanks!

[Luca Nicoletti]

nw 🙂

[Adam Powell]

We'll probably have a nicer effect than the raw ambient for doing this, one that will automatically trigger recomposition on a config change when appropriate

[Michal Bacik]

Config change will restart Activity as usual, so why another check in compose?

[Adam Powell]

Because ideally fully compose apps will disable activity recreation because it's not necessary

[Adam Powell]

Activity recreation is a super coarse recompose and it's redundant if your whole UI is already using compose

[kioba]

I can't give enough like for this Adam 😄

[Luca Nicoletti]

You can use all the love emoji

[Luca Nicoletti]

See? There’s tone of them

[Michal Bacik]

But we will have to mark in manifest lots of config changes flags for each activity, or will it work somehow automatically to avoid activity restarts for example when screen rotates?

[kioba]

maybe the ComposeActivity can set this up automaticly 🤔
take a look at the ComposeActivity annotation idea:
https://kotlinlang.slack.com/archives/CJLTWPH7S/p1565132788112000?thread_ts=1565101902.109300

[Adam Powell]

Exactly

[Luca Nicoletti]

🔝

[Leland Richardson [G]]

my idea was to have @Composable fun main() be the entry point 🙂

[pavi2410]

Not again @Leland Richardson [G]

[Luca Nicoletti]

DO IT

[Adam Powell]

the difficulty with main being magic for android is that it maps poorly to multiple activity entry points to an app, which isn't something I want to discourage with the shape of our preferred entry point definition mechanism

[Luca Nicoletti]

no multiple activity with compose 🧌

[Adam Powell]

can't nicely put more than one at the top level in a file, not much of a place to define the intent filters, etc. etc.

[Adam Powell]

you still want multiple activity for viewers that start on top of other apps, for example

[Luca Nicoletti]

Sure, was kidding 🙂

[Adam Powell]

posting it mostly for the benefit of onlookers 🙂

[Leland Richardson [G]]

yeah to be clear i was actually thinking the main() thing for a different usage, and thought it was cute. not actually thinking we should do this. it doesn’t map to the platform well enough