replicant-frameworks_native

History

Kenny Root 92f5984d2c Optional use of UTF-8 strings in resource bundles Allows the use of UTF-8 for packing resources instead of the default of UTF-16 for Java. When strings are extracted from the ResStringPool, they are converted to UTF-16 and the result is cached for subsequent calls. When using aapt to package, add in the "-8" switch to pack the resources using UTF-8. This will result in the value, key, and type strings as well as the compiled XML string values taking significantly less space in the final application package in most scenarios. Change-Id: I129483f8b3d3b1c5869dced05cb525e494a6c83a		2009-12-07 15:14:15 -08:00
..
Android.mk	implement Mutex and Condition with pthread instead of calling futex directly.	2009-07-13 15:14:23 -07:00
Asset.cpp	Fix issue #2048263 : More debugging information	2009-08-11 18:56:41 -07:00
AssetDir.cpp
AssetManager.cpp	Don't re-parse the framework resources all the time.	2009-07-06 11:12:37 -07:00
BackupData.cpp	Turn off most of the backup-related debug logging	2009-09-30 17:07:37 -07:00
BackupHelpers.cpp	Better (and less) logging from backup.	2009-06-26 17:19:11 -04:00
BufferedTextOutput.cpp
CallStack.cpp
CharacterData.h
Debug.cpp
FileMap.cpp
misc.cpp
MODULE_LICENSE_APACHE2
NOTICE
README
RefBase.cpp
ResourceTypes.cpp	Optional use of UTF-8 strings in resource bundles	2009-12-07 15:14:15 -08:00
SharedBuffer.cpp
Static.cpp
StopWatch.cpp
String8.cpp	Optional use of UTF-8 strings in resource bundles	2009-12-07 15:14:15 -08:00
String16.cpp	Optional use of UTF-8 strings in resource bundles	2009-12-07 15:14:15 -08:00
StringArray.cpp
SystemClock.cpp
TextOutput.cpp
Threads.cpp	use broadcast() instead of signal() when signaling the condition-variable Thread::RequestExitAndWait() is waiting for	2009-09-09 02:45:26 -07:00
Timers.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.