replicant-frameworks_native

History

…
..
tests	Fade out the mouse pointer after inactivity or other events.	2011-03-02 15:37:57 -08:00
Android.mk
Asset.cpp	Change assets to use 64-bit API	2010-12-08 11:21:30 -08:00
AssetDir.cpp	auto import from //depot/cupcake/@135843	2009-03-03 19:31:44 -08:00
AssetManager.cpp
BackupData.cpp
BackupHelpers.cpp
BufferedTextOutput.cpp
CallStack.cpp
Debug.cpp
FileMap.cpp	Change assets to use 64-bit API	2010-12-08 11:21:30 -08:00
Flattenable.cpp
Looper.cpp
misc.cpp	auto import from //depot/cupcake/@135843	2009-03-03 19:31:44 -08:00
MODULE_LICENSE_APACHE2	auto import from //depot/cupcake/@135843	2009-03-03 19:31:44 -08:00
NOTICE
ObbFile.cpp
Pool.cpp
PropertyMap.cpp
README
RefBase.cpp
ResourceTypes.cpp
SharedBuffer.cpp
Static.cpp
StopWatch.cpp
StreamingZipInflater.cpp
String8.cpp
String16.cpp
StringArray.cpp	rename string_array.h to StringArray.h and move the implementation from the header file to a new cpp file.	2009-06-05 01:26:23 -07:00
SystemClock.cpp
TextOutput.cpp
Threads.cpp
Timers.cpp
Tokenizer.cpp
Unicode.cpp
VectorImpl.cpp
ZipFileCRO.cpp
ZipFileRO.cpp
ZipUtils.cpp	fix FILE* version of ZipUtils::inflateToBuffer	2009-07-16 11:27:13 -07:00

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.