kotlinlang #android

huh..i'm trying to instantiate a ViewHolder as i see in examples, but it says can't instantiate an abstract class edit: nvm, stupid same-naming of examples

rharter

10/10/2016, 8:28 PM

Anybody have a good solution for synthetic view accessor in Dialogs? AFAIK the extension functions are only for activities and views

rharter

10/10/2016, 8:30 PM

In my custom dialog’s

onCreate

, I want to

setContentView(R.layout.foo)

and then configure subviews

withoutclass

10/10/2016, 10:05 PM

Would using lazy variables work?

brianwernick

10/10/2016, 10:07 PM

I know in `ViewHolder`s you reference the

itemView

to access the synthetic properties (e.g.

itemView.titleTextView.text = “foo”

)

brianwernick

10/10/2016, 10:07 PM

I wonder if dialogs are similar

withoutclass

10/10/2016, 10:26 PM

I mean something like

val button by lazy { findViewById(R.id.button) }

withoutclass

10/10/2016, 10:27 PM

gotta be careful with accessing the variable before setContentView

shaunhubbard

10/11/2016, 12:21 AM

allo folks, does anyone know of a github integration that runs something like KTLint against your Pull Requests and comments on them for an android project? Thanks 😄

stepan.zalis

10/11/2016, 9:42 AM

hi, have you ever tried Kotlin with Realm? I have an error: “error: cannot inherit from final xxxx"

stepango

10/11/2016, 9:43 AM

open

☝️ 3

👍 2

bamdmux

10/11/2016, 9:47 AM

@vmironov I'm using bindPreference and bindArgument in production 👍

chi

10/11/2016, 2:53 PM

I’m having the following issues running my project

Copy code

Unresolved reference: databinding
Error:Execution failed for task ':app:compileDebugKotlinAfterJava'.
> Compilation error. See log for more details

rameshbhupathi

10/12/2016, 6:04 AM

@sorinirimies yes, u can use it.

kko

10/12/2016, 9:56 AM

Hi guys. So not really a purely Kotlin question per se. I've got a Kotlin app with MVP pattern where I want to enforce that

Presenter

calling

View

always happens on UI thread. How (if at all?) does everyone else deal with this?

uhe

10/12/2016, 10:10 AM

@kko 1. If a method is called from the UI thread (e.g. from a click listener), then do nothing special. 2. If the presenter itselfs starts some background stuff (e.g. some scheduled thing or something that is local to the presenter), it has to make sure it calls the view on the UI thread:

Copy code

scheduler.after(30.seconds) {
                onMainThread {
	                   view?.updateFoo()
                }
            }

3. If the presenters trigger backend stuff in the model, it kind of depends on your architecture. If you're using EventBus you could use

ThreadMode.MAIN

. If you're using Rx you could use main thread schedulers.

uhe

10/12/2016, 10:10 AM

at least that's how I do it in our app and it's been working quite well so far

kko

10/12/2016, 10:11 AM

hey @uhe, that's kind of what I'm doing right now as well

kko

10/12/2016, 10:12 AM

I guess I should have been more specific

kko

10/12/2016, 10:12 AM

I'm talking specifically about the scenarios where

Presenter

calls back to the

View

, stuff like

view.errorMessage = "something"

kko

10/12/2016, 10:13 AM

view

is usually implemented by

Activity

Fragment

and just forwards to actual UI elements

kko

10/12/2016, 10:14 AM

I've got heaps of plumbing code in the

Presenter

that does the marshalling to UI thread and I constantly need to think what thread I will be calling the

View

on...

kko

10/12/2016, 10:14 AM

so I guess my question is more about - is there a bit of infrastructure I could push that to, some nifty language feature I'm unaware of

kko

10/12/2016, 10:15 AM

for a second I thought delegated properties could help but clearly that's not what they are for

kko

10/12/2016, 10:16 AM

my main concern here is the readability of my code

kko

10/12/2016, 10:26 AM

the best I can think of is hiding most of this in a Kotlin builder so instead of:

Copy code

val activity = breakAbstractionAndGetActivityInstance()
activity.runOnUiThread{
   view.someStuff("hello")
}

I have

Copy code

ui(view) {
   someStuff("hello")
}