Currently, this has only the following capabilities:
+ Authenticate using a Google account on the phone
+ Query and display the host list from the Chromoting directory server
+ Connect to and communicate with the host service over XMPP/ICE
+ Establish peer-to-peer channels for communicating with the host service
Notable missing features are:
- Display the host's desktop
- Handle any kind of input
Review URL: https://chromiumcodereview.appspot.com/19506004
git-svn-id: http://src.chromium.org/svn/trunk/src/build@212496 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This will house material analogous to the Pepper implementation remoting_client_plugin, except designed to interface instead with JNI, the Java Native Interface.
For now, this folder contains the jni_interface family of functions (which will receive calls FROM Java) and the ChromotingJNIInstance class, which implements ClientUserInterface (while being responsible for calls TO Java).
Review URL: https://chromiumcodereview.appspot.com/18856012
git-svn-id: http://src.chromium.org/svn/trunk/src/build@211073 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This simplifies using components in Content Shell. As components can
depend on the content layer, trying to use a component from Content Shell
results in a cross-reference of gyp files which isn't allowed on Mac.
TBR=joi,robertshield (trivial one-line renames in gyp files)
Review URL: https://chromiumcodereview.appspot.com/17366006
git-svn-id: http://src.chromium.org/svn/trunk/src/build@209420 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The compositor bindings for WebKit should only be used in a render process or in
webkit_support for DumpRenderTree or webkit_unit_tests. It's never used in a
browser process. This moves the bindings code under webkit/renderer/ so we can
enforce this via DEPS rules.
The path is unfortunately a bit awkward. Once we drop DumpRenderTreeSupport and
figure out a way to deal with webkit_unit_tests, we can move the bindings into
content/renderer/gpu/ since they'll only be used by the content embedding.
BUG=239107
TBR=piman@chromium.org
Review URL: https://codereview.chromium.org/14651027
git-svn-id: http://src.chromium.org/svn/trunk/src/build@200350 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The cacheinvalidation_java target is also added to build/all_android.gyp to
ensure it is always built since nothing currently depends on it upstream.
When all of Android-specific sync code is upstreamed, a target for sync
should be used instead of cacheinvalidation.
BUG=158382
Review URL: https://chromiumcodereview.appspot.com/11146005
git-svn-id: http://src.chromium.org/svn/trunk/src/build@167746 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
- The java files had the issue that findbugd plugin need to find out, they
compiled with the same configuration as chrome for android's.
- The run_findbugs_plugin_tests.py runs the findbugs against the above Java
classes, and expects to find the same issues as those in expected_result.txt.
BUG=143971, 157970
Review URL: https://chromiumcodereview.appspot.com/11343057
git-svn-id: http://src.chromium.org/svn/trunk/src/build@165442 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Add a new property generate.test.jar to ant scripts.
When this property is set, a jar containing all compiled
classes and referred classes is generated and placed in
out/{Debug|Release}/test.lib.java directory.
This makes it easier and cleaner to write ant build files for test apks.
New directory structure for the build:
Apks are placed in : out/{Debug|Release}/apks
All java libraries in : out/{Debug|Release}/lib.java
All test java libraries in : out/{Debug|Release}/test.lib.java
This CL also includes cleanup to work with the modified output
directory structure.
BUG=146583
Review URL: https://chromiumcodereview.appspot.com/10905138
git-svn-id: http://src.chromium.org/svn/trunk/src/build@157570 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Fixed build breakages:
-Had to add DEPS file for testshell/java.
-Something changed with ant from the time I tested and the time my CL got committed. Had to move
sdk-targets.xml import in the ant file to the end of the file.
This reverts commit 2d30dc03dc0bd0723236c549313774119f163056.
BUG=
Review URL: https://chromiumcodereview.appspot.com/10905209
git-svn-id: http://src.chromium.org/svn/trunk/src/build@156458 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This makes check_deps fail on linux thusly:
Using base directory: src
Checking: src
WARNING: no package definition found in src/content/test/data/plugin/java_applet.java
WARNING: no package definition found in src/content/test/data/plugin/applet-tests/cookies/CookieTest.java
WARNING: no package definition found in src/content/test/data/plugin/applet-tests/authenticator/AuthenticatorTest.java
WARNING: multiple definitions of com.example.HelloLicenseServlet:
src/chrome/common/extensions/docs/examples/apps/hello-java/workspace/HelloLicense/src/com/example/HelloLicenseServlet.java
src/chrome/common/extensions/docs/examples/apps/hello-java/HelloLicenseServlet.java
ERROR in src/chrome/android/testshell/java/src/org/chromium/chrome/testshell/ChromiumTestShellActivity.java
Illegal include: "content/public/android/java/src/org/chromium/content/app/LibraryLoader.java"
Because of no rule applying.
Illegal include: "content/public/android/java/src/org/chromium/content/browser/ContentView.java"
Because of no rule applying.
Illegal include: "content/public/android/java/src/org/chromium/content/common/CommandLine.java"
Because of no rule applying.
ERROR in src/chrome/android/testshell/java/src/org/chromium/chrome/testshell/ChromiumTestShellApplication.java
Illegal include: "content/public/android/java/src/org/chromium/content/app/LibraryLoader.java"
Because of no rule applying.
Illegal include: "content/public/android/java/src/org/chromium/content/browser/ResourceExtractor.java"
Because of no rule applying.
FAILED
Add a build target and tie it into android_all. This will build and link
Chrome code for a test apk for Android. When it runs it properly
loads the library but crashes. Will fix the crashes in subsequent
patches, but can fork that work after this is in.
BUG=136786
Review URL: https://chromiumcodereview.appspot.com/10918113TBR=dtrainor@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10911202
git-svn-id: http://src.chromium.org/svn/trunk/src/build@155958 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Add a build target and tie it into android_all. This will build and link
Chrome code for a test apk for Android. When it runs it properly
loads the library but crashes. Will fix the crashes in subsequent
patches, but can fork that work after this is in.
BUG=136786
Review URL: https://chromiumcodereview.appspot.com/10918113
git-svn-id: http://src.chromium.org/svn/trunk/src/build@155950 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Move the webview targets from the android_experimental target into All
so they are built by default on the main tree and on trybots. The tests
are not run currently; this is just checking that they compile.
The libwebview target is a dependency of android_webview_apk so it
doesn't need to be specified explicitly here.
BUG=
Review URL: https://chromiumcodereview.appspot.com/10918124
git-svn-id: http://src.chromium.org/svn/trunk/src/build@155498 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Clocks can't be synchronized programmatically on non-rooted devices due to the
inability to use the SET_TIME permission in non-system apps.
We were depending on synchronization in AndroidCommands.PushIfNeeded() to
handle incremental data push by comparing host and device file timestamps.
This CL adds tools/android/m5sum and uses it in android_commands.py so that we
can avoid depending on dates to handle incremental data push.
This is a first step towards clock synchronization removal.
BUG=143114
Review URL: https://chromiumcodereview.appspot.com/10867008
git-svn-id: http://src.chromium.org/svn/trunk/src/build@154751 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
1) Rename WebViewMainDelegate to AwMainDelegate for consistency with
other classes.
2) Move gyp file to the top level and don't bother having separate gypi
files for the subcomponents for now; the file list is very short anyway
and is not going to be a significant source of contention between the
small number of webview developers at this time, and it's easier to see
what's going on if it's all in one place.
BUG=
Review URL: https://chromiumcodereview.appspot.com/10893025
git-svn-id: http://src.chromium.org/svn/trunk/src/build@154020 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This creates a "libwebview" build target for the JNI code to power the
Android WebView. This is unfinished and can't run without additional
code that has not yet been upstreamed, but it compiles and links
successfully.
In its present state the WebViewMainDelegate reuses Chrome
implementations of other content client interfaces. This is a temporary
state of affairs until necessary refactorings can be performed.
Review URL: https://chromiumcodereview.appspot.com/10825155
git-svn-id: http://src.chromium.org/svn/trunk/src/build@150780 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This consists of a simple native program which dumps /proc/diskstats and
/proc/stat to a file at a regular interval. The dump is then processed host-side
into a JSON format which is charted in HTML via the Google Charts API.
The perf test runners are not upstreamed yet and when they are this will be part
of the set of profilers available.
BUG=136690
TEST=manual, run activity_monitor.py to try out.
Review URL: https://chromiumcodereview.appspot.com/10783020
git-svn-id: http://src.chromium.org/svn/trunk/src/build@147019 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
gkanwar@chromium.org
solb@chromium.org
jam@chromium.org
mnaganov@chromium.org
qinmin@chromium.org
jamesr@chromium.org
jochen@chromium.org
frankf@chromium.org
cjhopman@chromium.org
jayjang@chromium.org
gman@chromium.org
jln@chromium.org
nileshagrawal@chromium.org
boliu@chromium.org
kaiwang@chromium.org
ppi@chromium.org
bulach@chromium.org
nyquist@chromium.org
jcivelli@chromium.org
mkosiba@chromium.org
michaelbai@chromium.org
shashishekhar@chromium.org
felipeg@chromium.org
epenner@chromium.org
dtrainor@chromium.org
peter@chromium.org
thakis@chromium.org
torne@chromium.org
yfriedman@chromium.org
pliard@chromium.org
ilevy@chromium.org
satish@chromium.org