summaryrefslogtreecommitdiffstats
path: root/components/clipboard/main.cc
Commit message (Collapse)AuthorAgeFilesLines
* Remove duplicate application cpp files in mojo/application.jam2015-05-201-3/+2
| | | | | | | | 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}
* mojo: Use ContentHandlers to bundle multiple Applications into a module.erg2015-05-011-27/+3
| | | | | | | | | | | | | | | | | | | | | | | | 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}
* Moves mojo/services/* to components/* part 1sky2015-04-201-0/+37
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}