History log of /frameworks/data-binding/compiler/src/main/kotlin/android/databinding/tool/writer/DataBinderWriter.kt
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
af146d6a8c0efcf5682d14047c06866a5548f78f 22-Jan-2016 Yigit Boyar <yboyar@google.com> Update data binding to kotlin beta 4

I've also run some cleanup inspections to keep codebase
more up to date.

Bug: 26738574
Change-Id: I02aa43157cad858c0ea60dd41a22150e3cf2cfa1
/frameworks/data-binding/compiler/src/main/kotlin/android/databinding/tool/writer/DataBinderWriter.kt
59229481aec5a284d322a2ca80dff836485feb0c 30-Oct-2015 Yigit Boyar <yboyar@google.com> upgrade kotlin to 1.0-beta1

Change-Id: I62b77fd118e2715d272a16d96b9083d2347f5fb1
/frameworks/data-binding/compiler/src/main/kotlin/android/databinding/tool/writer/DataBinderWriter.kt
d3dc1b70aa71e8343dbf5e05a2feeb72bb29b6ec 08-Oct-2015 Yigit Boyar <yboyar@google.com> Fix tag check in data binding mapper

This CL fixes a bug in data binding mapper where if the View's tag does
not match one of the expected tags, it would fall through to the ext
case statemet which would result in a meaningless error.

This CL detects the case and throws an exception. This case should not
happen since it is not a supported case but happened here due to another
bug

Bug: 24745000
Change-Id: Ic5c6d4ce2da6ad043fb6fe56cd0847c98ea2472d
/frameworks/data-binding/compiler/src/main/kotlin/android/databinding/tool/writer/DataBinderWriter.kt
e4cd38824a6627b9fef229c549c636e35ad63b5f 07-Jul-2015 George Mount <mount@google.com> Support dependency injection.

Bug 22389109

Change-Id: Iec63375c5412edc03b4808ee129a7596b61bf9e6
/frameworks/data-binding/compiler/src/main/kotlin/android/databinding/tool/writer/DataBinderWriter.kt
4df4ba38a62b791bbbc25e923efe8d9c2f9a52e9 27-Jun-2015 Yigit Boyar <yboyar@google.com> Data binding startup improvement

This CL replaces how we map tags(string) to layout ids in the
generated DataBindingMapper class. Previously, we would create
a hashmap which was some unnecessary work in startup. The alternative
was using switch(string) but we did not want to require java 7.
This CL does what java 7's switch(string) would do thanks to the
well defined API of String.hashCode.

This CL also adds a method to DataBindingUtil to convert BR.ids
back to String for debugging purposes.

Bug: 22108735
Change-Id: I4b8ef816f4aac99b2963793dd46519b056ce4a30
/frameworks/data-binding/compiler/src/main/kotlin/android/databinding/tool/writer/DataBinderWriter.kt
4cc84854a6a5e8eca4ba1cfe574d5a8092b598d6 15-May-2015 George Mount <mount@google.com> Remove unused getId from DataBinderMapper and BR.java
/frameworks/data-binding/compiler/src/main/kotlin/android/databinding/tool/writer/DataBinderWriter.kt
ed6428586a939e00d9e66314d5cf1056ad48767e 30-Apr-2015 George Mount <mount@google.com> Add static method to get ViewDataBinding for a View.

Bug 20676836

Change-Id: I8690f64b395ceb06fd12daaadcb0f31d6629fc0b
/frameworks/data-binding/compiler/src/main/kotlin/android/databinding/tool/writer/DataBinderWriter.kt
96e1c821dd446d1ed78f8ae61131550588f60a24 10-Apr-2015 George Mount <mount@google.com> Support merge tags.

This also drops the requirement for include tags to have an ID.

Each root view tag is given a numeric suffix, starting with 0.
Merge tags can have multiple roots, the first of which always
is suffixed with 0. The remainder have tag identifiers that
are interspersed with the tags used with expressions. The
numeric suffix is used to identify the View in the mapBindings
call.

Include tag information now uses the tag of its parent so that
its parent will search for the includes within it. When
mapBindings is looking at the parent, it looks for all direct
children with the appropriate tag of the format "layout*/name_0".
Then it searches for all siblings with the same prefix and different
numeric suffixes. Any that are found are considered part of the
same merged include. If it finds another with _0, it knows that
a new include was found.

Change-Id: Idd1144d9037648193724667320744bd079791476
/frameworks/data-binding/compiler/src/main/kotlin/android/databinding/tool/writer/DataBinderWriter.kt
0390898cf7c4fcad255e8cfd6802f722b516cb2c 03-Apr-2015 George Mount <mount@google.com> Use layout path for the tag on bound layout roots.

Change-Id: I6bda5d5716e749251b27c112865da066ba908509
/frameworks/data-binding/compiler/src/main/kotlin/android/databinding/tool/writer/DataBinderWriter.kt
e7c2a5e45d7651899790bd347da635875f9c73fb 02-Apr-2015 George Mount <mount@google.com> Use setTag(id, val) when minSdk is ICS and later.

setTag(id, val) leaks on versions before ICS. When the
minimum SDK is before ICS, setTag(val) must be used
for bindings. However, this prevents the developer from
using the tag for his or her own purposes. Therefore,
if the minimum SDK is ICS and greater, setTag(id, val)
is used.

Change-Id: I46327084bde4bafc05a64f82ad5ebcf710820ecc
/frameworks/data-binding/compiler/src/main/kotlin/android/databinding/tool/writer/DataBinderWriter.kt
125f08f32dbe73b457768aeca4accfbc44dd44b6 01-Apr-2015 George Mount <mount@google.com> Don't use reflection for DataBinderMapper.

By having a concrete implementation of DataBinderMapper in the
library and then stripping it out, the generated DataBinderMapper
may be instantiated without reflection.
/frameworks/data-binding/compiler/src/main/kotlin/android/databinding/tool/writer/DataBinderWriter.kt
dea555cf42dc3583604699c8c018d22681f56166 30-Mar-2015 George Mount <mount@google.com> Merge implementation into base class for single implementations.

Bug 19933646

Change-Id: Ifc947d929b5275e32598e8d40f0122504a99d7f8
/frameworks/data-binding/compiler/src/main/kotlin/android/databinding/tool/writer/DataBinderWriter.kt
fead9ca09b117136b35bc5bf137340a754f9eddd 23-Mar-2015 George Mount <mount@google.com> Move to package android.databinding.
/frameworks/data-binding/compiler/src/main/kotlin/android/databinding/tool/writer/DataBinderWriter.kt