Build mojo_shell on Android

mojo/shell/android/shell_apk/src/org/chromium/mojo_shell_apk/MojoShellActivity.java

Index: mojo/shell/android/shell_apk/src/org/chromium/mojo_shell_apk/MojoShellActivity.java
diff --git a/mojo/shell/android/shell_apk/src/org/chromium/mojo_shell_apk/MojoShellActivity.java b/mojo/shell/android/shell_apk/src/org/chromium/mojo_shell_apk/MojoShellActivity.java
new file mode 100644
index 0000000000000000000000000000000000000000..966ea278942b82cc3d48b8adab5bb9bb519ddf3d
--- /dev/null
+++ b/mojo/shell/android/shell_apk/src/org/chromium/mojo_shell_apk/MojoShellActivity.java
@@ -0,0 +1,36 @@
+// Copyright 2013 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+package org.chromium.mojo_shell_apk;
+
+import java.lang.UnsatisfiedLinkError;

[bulach, 2013/10/24 12:58:04]

nit: no need, afaict java.lang is implicit.

[abarth-chromium, 2013/10/24 13:43:05]

Oh, that's nice.  I'm a Java noob.

+
+import android.os.Bundle;
+import android.app.Activity;
+import android.util.Log;
+
+import org.chromium.mojo_shell_apk.LibraryLoader;
+
+/**
+ * Activity for managing the Mojo Shell.
+ */
+public class MojoShellActivity extends Activity {
+    private static final String TAG = "MojoShellActivity";
+
+    @Override
+    protected void onCreate(final Bundle savedInstanceState) {
+        super.onCreate(savedInstanceState);
+
+        setContentView(R.layout.mojo_shell_activity);
+
+        try {
+            LibraryLoader.ensureInitialized();

[bulach, 2013/10/24 12:58:04]

yeah, not saying to do now, but just highlighting that the "real deal" does not
initialize this way... if mojo is to become an example on how to have a base
multi-process app :) we should probably change this soon.

also, it needs to call into base::android::InitApplicationContext()...
this is now exposed at the content level,

ContentMain.initApplicationContext(getApplicationContext()), mojo (shell) would
probably require something similar..

[abarth-chromium, 2013/10/24 13:43:05]

I'm sorry, but I didn't understand this comment.  What should we change this to?
Yeah, we aren't calling "main" type functions on the C++ side yet.  I was going
to work through that in the next CL.  We'll obviously need to do that soon.  :)

[bulach, 2013/10/24 16:27:57]

ops, sorry I wasn't clear.. :)
it's perfectly fine to keep as is for the time being..
As mentioned before, we'd need to extract the building blocks from content up
here at some point...
specifically, the "ensureInitialized" would be blocking.
At the "onCreate" level, we'd want to kick off loading the library in a separate
thread, do the java initialization here, then listen for a callback to proceed
with further initialization once the library has been loaded...
the great thing about mojo is that will help clarify and make it more generic,
right now each one of our "shells" (content, chromium, chrome) have their own
mechanisms, so I'm really looking forward to this being a major force in
clarifying / refactoring such building blocks!

+        } catch (UnsatisfiedLinkError e) {
+            Log.e(TAG, "libmojo_shell initialization failed.", e);
+            finish();
+            return;
+        }
+        Log.i(TAG, "libmojo_shell initialization success.");
+    }
+}