Wednesday, September 23, 2015

Episode 35: Data Bound

In this episode, we chat with George Mount and Yigit Boyar from the Android UI Toolkit team. Yigit and George worked on the new Data Binding feature announced at Google I/O and which is available in the preview release and in recent versions of Android Studio.

Subscribe to the podcast feed or download the audio file directly.

Relevant Links

Data Binding Guide

George Mounthttps://plus.google.com/+GeorgeMount007
Yigit Boyarhttps://plus.google.com/111851968937104436377@yigitboyar
Tor: google.com/+TorNorbye@tornorbye
Chet: google.com/+ChetHaase@chethaase

4 comments:

  1. Hey guys, that was a nice episode. I've been using the data binding tool for 2 or 3 weeks. But there's a subject I notice you didn't mention and it's the one I've been struggling with, which is data input. Being more specific, I only could get data binding to work in one way (data to interface), but not two ways (both data to interface and interface to data). Sorry for the lazy writing, I'm doing it while on a bus. Congratulations for the podcast it's really nice

    ReplyDelete
  2. Android data binding v1 is one-way only. You'll still have to listen to change events to handle the user's input. This has been made a little easier for you by allowing hookups to the events in XML. For example, you can bind to TextView change events with android:onTextChanged="@{handlers.passwordTextChanged}".

    ReplyDelete
  3. How do you use viewstub when using data binding? Can anyone provide an example, because instantiating a ViewStubProxy using a reference to the ViewStub obtained from the bound layout causes compiler errors in Android Studio.

    ReplyDelete
  4. How do you use viewstub when using data binding? Can anyone provide an example, because instantiating a ViewStubProxy using a reference to the ViewStub obtained from the bound layout causes compiler errors in Android Studio.

    ReplyDelete