98e71ddaed
Add a Flattenable interface to libutils which can be used to flatten an object into bytestream + filedescriptor stream. Parcel is modified to handle Flattenable. And GraphicBuffer implements Flattenable. Except for the overlay classes libui is now independent of libbinder. |
||
|---|---|---|
| .. | ||
| Android.mk | ||
| Asset.cpp | ||
| AssetDir.cpp | ||
| AssetManager.cpp | ||
| BackupData.cpp | ||
| BackupHelpers.cpp | ||
| BufferedTextOutput.cpp | ||
| CallStack.cpp | ||
| Debug.cpp | ||
| FileMap.cpp | ||
| Flattenable.cpp | ||
| misc.cpp | ||
| MODULE_LICENSE_APACHE2 | ||
| NOTICE | ||
| README | ||
| RefBase.cpp | ||
| ResourceTypes.cpp | ||
| SharedBuffer.cpp | ||
| Static.cpp | ||
| StopWatch.cpp | ||
| String8.cpp | ||
| String16.cpp | ||
| StringArray.cpp | ||
| SystemClock.cpp | ||
| TextOutput.cpp | ||
| Threads.cpp | ||
| Timers.cpp | ||
| VectorImpl.cpp | ||
| ZipFileCRO.cpp | ||
| ZipFileRO.cpp | ||
| ZipUtils.cpp | ||
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.