This patch turns NativePanZoomController's MotionEvent handler into a native method, and it adds the WrapForJNI annotations to all native methods so that bindings will be automatically generated for them.

This patch adds specializations of jni::Ref for primitive arrays like IntArray and FloatArray, so that the arrays can be accessed through the GetElement, GetElements, and Length members.

This patch adds the NPZCSupport class to nsWindow and use it to implement the NPZC native methods that were implemented in AndroidJNI.cpp. For HandleMotionEvent, the code also includes a portion from AndroidJavaWrapper::MakeMultitouchEvent.

This patch adds a way to attach a particular NativePanZoomController instance held by LayerView to a particular nsWindow instance. Because LayerView already calls GLController.SetLayerClient during initialization, this patch renames it to attachToJava and modifies it to accept an additional NPZC parameter. In the new AttachToJava implementation, we create or reuse a NPZCSupport object and associate it with the NPZC instance.

This patch rewrites AndroidContentController to get rid of any dependencies on a static nsWindow or APZC tree manager.

With APZC supporting multiple nsWindows, this patch removes some obsolete APZ code, including the previous implementation of NativePanZoomController native methods in AndroidJNI.cpp, and the various static members of nsWindow.

This patch autogenerates constants for MotionEvent to replace the manual definitions in AndroidJavaWrappers.

Comment on attachment 8706639 [details] [diff] [review] Switch NativePanZoomController to use native methods (v1) Review of attachment 8706639 [details] [diff] [review]: ----------------------------------------------------------------- ::: mobile/android/base/java/org/mozilla/gecko/gfx/NativePanZoomController.java @@ +45,5 @@ > + final float[] toolMinor = new float[count]; > + > + final MotionEvent.PointerCoords coords = new MotionEvent.PointerCoords(); > + final PointF point = !keepInViewCoordinates ? new PointF() : null; > + final float zoom = !keepInViewCoordinates ? mView.getViewportMetrics().zoomFactor : 0.0f; If the default is 1.0f and not 0.0f you wouldn't need the if check on line 69. This obviously fine the way it is, I just get nervous when I see a variable set to 0.0 and then used in a divide later.

https://hg.mozilla.org/integration/mozilla-inbound/rev/84815007ef6b https://hg.mozilla.org/integration/mozilla-inbound/rev/7ea026f1ff21 https://hg.mozilla.org/integration/mozilla-inbound/rev/efc13abebc11 https://hg.mozilla.org/integration/mozilla-inbound/rev/1424238752d3 https://hg.mozilla.org/integration/mozilla-inbound/rev/959e9cd05801 https://hg.mozilla.org/integration/mozilla-inbound/rev/a6812fd0c533 https://hg.mozilla.org/integration/mozilla-inbound/rev/644097e60a78

https://hg.mozilla.org/mozilla-central/rev/84815007ef6b https://hg.mozilla.org/mozilla-central/rev/7ea026f1ff21 https://hg.mozilla.org/mozilla-central/rev/efc13abebc11 https://hg.mozilla.org/mozilla-central/rev/1424238752d3 https://hg.mozilla.org/mozilla-central/rev/959e9cd05801 https://hg.mozilla.org/mozilla-central/rev/a6812fd0c533 https://hg.mozilla.org/mozilla-central/rev/644097e60a78

Fix bustage for non-APZ builds. r=me