https://kotlinlang.org logo
#android
Title
# android
m

marcinmoskala

05/10/2017, 9:16 AM
Pretty new concept to use property delegation to make MVP implementation much easier. I would love to have some feedback 🙂
l

leosan

05/10/2017, 9:21 AM
marcinmoskala: hey @marcinmoskala just a little typo here, and should be
password
I think ( still reading though 😄, looking cool)
Copy code
override fun getEail() {
    return passwordView.text.toString()
}
}
m

marcinmoskala

05/10/2017, 9:23 AM
True, sorry
r

reggar

05/10/2017, 9:23 AM
While we’re on typos, should
checkVaildity
be
checkValidity
?
m

marcinmoskala

05/10/2017, 9:25 AM
True again. Will be online in minute
m

mg6maciej

05/10/2017, 9:40 AM
If the code was in repo, all these typos would not compile or at least there would be a weak warning. 🙂
c

curioustechizen

05/10/2017, 9:51 AM
I once made a typo, in the word typo, while I was pointing out a colleague's typo ¯\_(ツ)_/¯
😂 3
🙃 2
d

diego-gomez-olvera

05/10/2017, 9:52 AM
The title is a clickbait, but the implementation is very elegant. I like that it keeps the Presenter framework independent while minimizing the typical MVP View boilerplate
👍 1
simple smile 1
k

kenkyee

05/10/2017, 1:05 PM
Would also help if it explained why using MVVM with Android bindings is bad. I don't think it's that bad except for the compile time stack mess if there's a compile issue. Just don't put logic in your XML files
3
m

mg6maciej

05/10/2017, 2:26 PM
I put all the logic in XML files whenever I use android bindings. It's a lot of fun.
🧌 2
m

marcinmoskala

05/10/2017, 7:36 PM
@kenkyee I may be wrong, because I base on opinions I heard and my experiences for over half year ago. But when I tried it, it was hard to make it work with Kotlin. Especially for more complex use-cases.
k

kenkyee

05/10/2017, 9:41 PM
It didn't play well with the kotlin plugin for a while...and stack traces are almost as useless as the dagger 2 ones 😔
g

gildor

05/11/2017, 1:18 AM
@marcinmoskala We use databindings a lot with Kotlin and we have very complex use-cases in some parts of application, no issue. Completely disagree that DataBindings is something bad or weak, you can implement everything what you have in your article but using even less code and more reusable in some cases (in your code viewmodel coupled with view id).
👍 2
m

marcinmoskala

05/11/2017, 7:38 AM
I would like to see it one day. Still, here there is no need for annotation processing and code generation, and it is easy to analyze how it is working. Everything have its pros and cons 🙂
6 Views