| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove unused mojo/public/mojo_sdk.gni.
(we use third_party/mojo's version instead)
Update, use mojo/public/ mojo.gni and mojo_application.gni
(to define Chromium's mojo_root, mojo_native_application)
(we'll need a custom mojo_native_application for 498020)
Remove unnecessary imports of related gni files.
BUG=498020
TEST=Build still works as expected; no regressions.
R=sky@chromium.org
TBR=jochen@chromium.org,xhwang@chromium.org
Review URL: https://codereview.chromium.org/1175693002
Cr-Commit-Position: refs/heads/master@{#333600}
|
|
|
|
|
|
|
|
|
|
|
|
| |
I logged into one failing machine and ran "mojo_runner --use-headless-config --gtest_filter=ViewManagerTest.RootView mojo:view_manager_apptests". The test printed that it passed but then hung. The output had "[0525/201523:ERROR:default_logger_impl.cc(46)] validation_errors.cc(61): Invalid message: VALIDATION_ERROR_UNEXPECTED_STRUCT_HEADER". This is because a component had a different version of the mojom serialization. Tracking down the build dependencies, it was because view_manager didn't depend on surfaces, and also mandoline:tests needed to depend on view_manager:apptests. I verified that building mandoline:tests on a broken bot fixed this.
I looked through all the apptests to make sure there were no other missing dependencies. I also removed an unnecessary "$default_toolchain)" in clipboard's build file.
BUG=478244
Review URL: https://codereview.chromium.org/1154153002
Cr-Commit-Position: refs/heads/master@{#331465}
|
|
|
|
|
|
|
|
| |
Some of these files were forked in the initial Mandoline landing. After we forked the application code, we now had two implementations of some of these files. We only need one.
Review URL: https://codereview.chromium.org/1142323003
Cr-Commit-Position: refs/heads/master@{#330690}
|
|
|
|
|
|
|
|
|
|
| |
of application.
That way other targets that depend on it don't have to specify ":application".
Review URL: https://codereview.chromium.org/1136763003
Cr-Commit-Position: refs/heads/master@{#330020}
|
|
|
|
|
|
|
|
|
|
|
|
| |
Per in-person discussions, as long as we have a fork of mojo shell we'll fork the interfaces.
I'll do third_party/mojo/src/mojo/public/java/application in a followup.
TBR=tsepez
Review URL: https://codereview.chromium.org/1139123006
Cr-Commit-Position: refs/heads/master@{#329965}
|
|
|
|
|
|
|
|
|
|
|
|
| |
These were needed to get a clean build working.
BUG=none
TEST=none
R=ben@chromium.org
Review URL: https://codereview.chromium.org/1129193005
Cr-Commit-Position: refs/heads/master@{#329893}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous way of implementing core_services worked by having a
ServiceProvider as the external interface. This fell down because the
boundary between Applications in mojo is meaningful and is used in the
ViewManager and the WindowManager to restrict access to some services.
The (possibly misnamed) ContentHandler interface, on the other hand,
looks like a possible avenue of attack. ContentHandler's one method
starts new Applications. So mojo:core_services should be a
ContentHandler instead of a ServiceProvider and will spawn an
Application for each internal service.
This currently hard codes the mapping in context.cc, but eventually, we
should do something more intelligent for the packaging. This patch also
doesn't handle spawning new applications on new threads as we don't have
multiple applications yet.
BUG=477435
Review URL: https://codereview.chromium.org/1115363002
Cr-Commit-Position: refs/heads/master@{#327947}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of having an application for clipboard.mojo, a
view_manager.mojo, et all, we instead will have one core_services
application which provides implementations of all the services compiled
into one physical file so we don't have to pay the cost of //base/ in
each application.
For now, this just moves clipboard.mojo into core_services.
BUG=477435
R=sky@chromium.org
TBR=ben@chromium.org
Review URL: https://codereview.chromium.org/1084463003
Cr-Commit-Position: refs/heads/master@{#327077}
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Most go into components/, with the exception of events and
input_events. They are in ui/mojo now.
R=ben@chromium.org, jam@chromium.org, jochen@chromium.org
TBR=jochen@chromium.org
BUG=479353
Review URL: https://codereview.chromium.org/1085233004
Cr-Commit-Position: refs/heads/master@{#326535}
|
|
I'm splitting this up in chunks so I can actually use the cq.
R=ben@chromium.org
Review URL: https://codereview.chromium.org/1097183002
Cr-Commit-Position: refs/heads/master@{#325942}
|