replicant-frameworks_native

History

Jeff Brown e839a589bf Native input dispatch rewrite work in progress. The old dispatch mechanism has been left in place and continues to be used by default for now. To enable native input dispatch, edit the ENABLE_NATIVE_DISPATCH constant in WindowManagerPolicy. Includes part of the new input event NDK API. Some details TBD. To wire up input dispatch, as the ViewRoot adds a window to the window session it receives an InputChannel object as an output argument. The InputChannel encapsulates the file descriptors for a shared memory region and two pipe end-points. The ViewRoot then provides the InputChannel to the InputQueue. Behind the scenes, InputQueue simply attaches handlers to the native PollLoop object that underlies the MessageQueue. This way MessageQueue doesn't need to know anything about input dispatch per-se, it just exposes (in native code) a PollLoop that other components can use to monitor file descriptor state changes. There can be zero or more targets for any given input event. Each input target is specified by its input channel and some parameters including flags, an X/Y coordinate offset, and the dispatch timeout. An input target can request either synchronous dispatch (for foreground apps) or asynchronous dispatch (fire-and-forget for wallpapers and "outside" targets). Currently, finding the appropriate input targets for an event requires a call back into the WindowManagerServer from native code. In the future this will be refactored to avoid most of these callbacks except as required to handle pending focus transitions. End-to-end event dispatch mostly works! To do: event injection, rate limiting, ANRs, testing, optimization, etc. Change-Id: I8c36b2b9e0a2d27392040ecda0f51b636456de25		2010-06-13 17:42:16 -07:00
..
tests	Native input dispatch rewrite work in progress.	2010-06-13 17:42:16 -07:00
Android.mk	Native input dispatch rewrite work in progress.	2010-06-13 17:42:16 -07:00
Asset.cpp
AssetDir.cpp
AssetManager.cpp	ZipUtilsRO rewrite based on Dalvik Zip rewrite	2010-05-12 05:07:48 -07:00
BackupData.cpp
BackupHelpers.cpp
BufferedTextOutput.cpp
CallStack.cpp
Debug.cpp
FileMap.cpp
Flattenable.cpp
misc.cpp
MODULE_LICENSE_APACHE2
NOTICE
PollLoop.cpp	Native input dispatch rewrite work in progress.	2010-06-13 17:42:16 -07:00
Pool.cpp	Native input dispatch rewrite work in progress.	2010-06-13 17:42:16 -07:00
README
RefBase.cpp
ResourceTypes.cpp
SharedBuffer.cpp
Static.cpp
StopWatch.cpp	Native input dispatch rewrite work in progress.	2010-06-13 17:42:16 -07:00
String8.cpp	Fix String8 to free its memory only after assignment operations based on pointers are finished in case that pointer referred to the string's original contents.	2010-06-10 11:25:51 -07:00
String16.cpp
StringArray.cpp
SystemClock.cpp
TextOutput.cpp
Threads.cpp
Timers.cpp
VectorImpl.cpp	Native input dispatch rewrite work in progress.	2010-06-13 17:42:16 -07:00
ZipFileCRO.cpp	ZipUtilsRO rewrite based on Dalvik Zip rewrite	2010-05-12 05:07:48 -07:00
ZipFileRO.cpp	ZipUtilsRO rewrite based on Dalvik Zip rewrite	2010-05-12 05:07:48 -07:00
ZipUtils.cpp

README

Android Utility Function Library

If you need a feature that is native to Linux but not present on other
platforms, construct a platform-dependent implementation that shares
the Linux interface.  That way the actual device runs as "light" as
possible.

If that isn't feasible, create a system-independent interface and hide
the details.

The ultimate goal is *not* to create a super-duper platform abstraction
layer.  The goal is to provide an optimized solution for Linux with
reasonable implementations for other platforms.