users/mraynsford/gluegen.git - GLUEGEN repository on http://jogamp.org/ ;

	Commit message (Collapse)	Author	Age	Files	Lines
*	Android: Cleanup ClassLoaderUtil/LauncherUtil - Using cached parent ↵	Sven Gothel	2013-01-31	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	ClassLoader for SYS-Packages w/ native libs, and non cached child ClassLoader for USR-Packages Android's Dalvik VM, like a JVM, cannot load a native library from one location by multiple ClassLoader. Since we don't like to hardcode the system-packages, as it was before, i.e. "com.jogamp.common", "javax.media.opengl", we need to either copy the libs or use parenting of cached ClassLoader. The latter is chosen, since it's faster and uses less resources. - System-packages are passed through from the user 'List<String> LauncherUtil.BaseActivityLauncher::getSysPackages()' to the ActivityLauncher, which instantiates the ClassLoader. - No more hard-reference the system-packages in ClassLoaderUtil ("com.jogamp.common", "javax.media.opengl"), just use the new user provided system-packages. - The system-packages denominate a hash-key for caching, a new ClassLoader is created and mapped if it does not yet exist. - A non-chached user-packages ClassLoader is created using the cached system-packages ClassLoader as it's parent.
*	Fix ActivityLauncher/MainLauncher .. and make adb-launch-main more suitable	Sven Gothel	2013-01-19	1	-24/+16
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	- ActivityLauncher - no finish() from onDestroy() - MainLauncher - finish activity after returning 'main()' returns - no finish() from onDestroy() - adb-launch-main: - Clear logcat - Wait until activity is stopped - Dump logcat to local logfile
*	MainLauncher: Remove Thread.destroy() - n/a on Android ..	Sven Gothel	2013-01-19	1	-1/+2
\|
*	Android Completion for launching main() class via MainLauncher; Fix ↵	Sven Gothel	2013-01-18	1	-14/+32
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	ActivityLauncher order of delegation/super activity callbacks. - StaticContext: - Add ViewGroup for standalone tests w/ UI - MainLauncher/LauncherUtil: - Complete launching a main() class from our activity launcher - adding main-cmdline-args - ActivityLauncher - Fix order of delegation/super activity callbacks.
*	AndroidLauncher: Add 'MainLauncher'; ClassLoaderUtil adds list of direct ↵	Sven Gothel	2012-05-03	1	-0/+239
	APKs to add to classpath MainLauncher is capable of launching a traditional static main method from a activity. TODO: - parametrize the APK list (junit, ..) - pass-through the activity instance to be used w/ NEWT AndroidWindow