oh, im not sure, i think java8 is from android N

Yeah, interesting stuff though. You’ve definitely given me something to think about

dont overthink it, youre gonna endup calling findviewbyid manually lol

which really isn't that bad. it looks nearly like the property delegate approach https://github.com/JakeWharton/SdkSearch/blob/master/search/ui-android/src/main/java/com/jakewharton/sdksearch/search/ui/SearchUiBinder.kt#L52-L54

you could even get cute and put an operator extension onto

ViewGroup

so that you could do

root[R.id.whatever]

yea thats what I was gonna say, that only downside is that fuglu nullable vars

but if you create a view scoped object in fragment that only lives between onCreateView and onDestroyView you get that view as ctor param

and lovely vals

which is what databinding generates for you

you can ignore the rest of the databinding functionality and only use it as a view binding code generator

and i find per-layout objects with semantic names much more pleasant than magic properties

that might be kotterknife2

just inject that container object and reference views always via container.myView

btw how do those synthetics work? if theyre magic, cant they just use arrays and have view names as array index aliases?

I just get really grossed out by a huge block of view properties hanging out at the top of my activities or fragments. It’s one of the big reasons I love synthetics so much.

I have an activity where I have something like 20 views I need to reference and reserving 20 lines at the top of the class just to bind all the views to really bugs me

let me get you excited about databinding code generation then

all of the properties are contained in a class with a name the same of the layout. you don't need to guess which IDs you can use and which you can't. you can't use the wrong ID, in fact

view lookup is performed using a single view tree traversal instead of multiple traversals

@jw do i still need that executePendingWhatever if I only want views?

i don't know what that is. you should only need to do the change in the layout file

so you’re saying I can just bind this “layout object” at the top of my file and refer to that when I want a view from it?

yes

combine that with

with

and that actually sounds pretty great

any glaring drawbacks?

thats nice, I never really messed with databinding since they lost me at that xml logic mumbo jumbo

the biggest drawback is that it's tied to databinding

yeah, I got turned off of databinding when you could put code in xml

Historically, some combination of multi-module projects, databinding, and kapt has had problems. I can't speak for more recent versions. I know there's been a lot of work.

btw @jw , in Butterknife if you exposed the ViewBinding object, i.e. made the api nicer