Andy2 977feada82 use a reference to a byte array in the java heap (locking down the ... object) rather than allocating a new array in the C heap -- for the DAWG data of a dictionary. This can use up to 5% of the java heap for huge dictionaries, but I'm hoping it fixes a problem reported by a user of the large German dictionary that seems to involve allocation. If I'm reading correctly, as long as I stay within 16M (24M or more on newer devices) I'm sure to get my memory in the java world while it's less a sure thing in the JNI world (where in addition linux's aggressive overallocation is used, meaning I'll fail when I try to swap in memory on write rather than get back NULL from malloc.)		2011-01-31 18:56:20 -08:00
..
assets	add BasEnglish dictionary.	2010-12-06 21:08:15 -08:00
jni	use a reference to a byte array in the java heap (locking down the	2011-01-31 18:56:20 -08:00
res	turn proxy service back on	2011-01-21 06:10:06 -08:00
src/org/eehouse/android/xw4	use getChannel().size() rather than available() to decide how many	2011-01-27 21:03:37 -08:00
.gitignore	remove local.properties, and add a script, run from build.xml before	2010-06-20 09:29:13 -07:00
AndroidManifest.xml	add ACCESS_NETWORK_STATE permission	2011-01-06 08:08:36 -08:00
build.xml	remove local.properties, and add a script, run from build.xml before	2010-06-20 09:29:13 -07:00
build_unchecked.xml	version of build.xml modified to pass -xline to javac. For future use...	2010-11-05 05:06:04 -07:00
default.properties	Build for 1.6 instead of 1.5 for SMS APIs	2010-02-09 14:16:23 +00:00