https://kotlinlang.org logo
#splitties
Title
# splitties
s

Sergio Crespo Toubes

12/04/2019, 8:48 AM
Hello #splitties any idea about
startActivityForResult
? I think is not implemented yet
l

louiscad

12/04/2019, 8:53 AM
Hello @Sergio Crespo Toubes What are you looking for exactly?
s

Sergio Crespo Toubes

12/04/2019, 8:55 AM
i am migrating from anko and i had something like
startActivityForResult<Activity>(requestCode,extra)
l

louiscad

12/04/2019, 9:19 AM
I see, can you open an issue with the example on GitHub? I'll consider adding it after the KotlinConf week.
👍🏻 1
i

ispbox

12/07/2019, 8:41 AM
I would like to add my 5 cents. From my point of view, it is really not necessary to wrap ugly Activity lifecycle events and messages in Splitties DSL / UI part of code. It is the responsibility of some other framework (for example, I would suggest Conductor for all that stuff).
l

louiscad

12/07/2019, 9:17 AM
But this thread is not about lifecycle events!? @ispbox
i

ispbox

12/07/2019, 11:40 AM
@louiscad You are right - startActivityForResult is more related to Intents, rather than Activity lifecycle. But that's why I added "events and messages" 🙂 I think that all activity-related stuff (events, intents) should be separated from UI (Splitties DSL). You can have any helpers in other Splits, that's ok. My concern was about weak responsibility segregation in Anko, that was really tied to Activities and Fragments. I appreciate that Splitties DSL goes another way :)
l

louiscad

12/07/2019, 5:48 PM
Splitties try to be like: do your own class, use interfaces if it fits, and use it from wherever you want, even all at once if needed.
3 Views