tree fbf466ffc298f6beb1b59a21e185183b1c5ec460
parent 2cde1f97b8a15c357bca3f98a43d8b4779c0d031
author Brian Colonna <bcolonna@google.com> 1333731689 -0400
committer Brian Colonna <bcolonna@google.com> 1333980752 -0400

Separated FUL functionality from LockPatternKeyguardView

This is the first step toward fix 5460649.  All of the FUL functions
were pulled out of LockPatternKeyguardView into their own FaceUnlock
class.  LockPatternKeyguardView now has an mFaceUnlock member, which
is new'd inside of the LockPatternKeyguardView constructor, passing
it some objects it needs to do FUL.  FUL calls are now made from
LockPatternKeyguardView by doing mFaceUnlock.foo().  Some of the
function names were reduced to avoid redundancy (e.g.
mFaceUnlock.start() instead of mFaceUnlock.startFaceLock()).

This change is just a refactoring and is not intended to change
any functionality.  There will be other cleanups in the near
future...this is basically just the minimum changes needed to get
the FUL functionality into its own class.

Change-Id: I7dc5b22857bbf1659238b0e2d113069f7bf9ffe7