summaryrefslogtreecommitdiffstats
path: root/content/public/app
Commit message (Collapse)AuthorAgeFilesLines
* reland of http://crrev.com/212230 Create top-level separate targets for...scottmg@chromium.org2013-07-181-3/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Original CL here: https://codereview.chromium.org/17619005/ Changed since previous landing is diff between ps1 and ps2. Diff since previous landing is a bit noisy, but in those files against original is relatively small. The conditions for the defines were incorrect and are simpler (and correct) now. Previously: Create top-level separate targets for browser and child dlls The general idea is that there's top level targets chrome and chrome_child, and corresponding content_app and content_app_child that depend on only the subtargets that should be included in the appropriate dll. Currently (probably) Windows-only and requires setting chrome_multiple_dll=1 for gyp. Links, but Blink is still included in browser. Single-process mode is currently disabled when chrome_multiple_dll is set. Current graph is at: http://commondatastorage.googleapis.com/chromelinkgraph/deps.html generated by "python tools\win\split_link\graph_dependencies.py deps.html" Remove the previous hacky-er attempt at this that was named "split dll". TBR=jam@chromium.org BUG=237249, 256965 Review URL: https://codereview.chromium.org/19572013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212415 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 212230 "Create top-level separate targets for browser and..."scottmg@chromium.org2013-07-181-29/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Caused Linux x64 sizes to fail for reasons unclear. > Create top-level separate targets for browser and child dlls > > The general idea is that there's top level targets chrome and chrome_child, > and corresponding content_app and content_app_child that depend on only > the subtargets that should be included in the appropriate dll. > > Pull bluetooth_utils from bluetooth_device into separate common target > as it's referenced from chrome/common/extensions. > > Currently (probably) Windows-only and requires setting chrome_multiple_dll=1 > for gyp. > > Links, but Blink is still included in browser. > > Single-process mode is currently disabled when chrome_multiple_dll is set. > > Current graph is at: http://commondatastorage.googleapis.com/chromelinkgraph/deps.html > generated by "python tools\win\split_link\graph_dependencies.py deps.html" > > Remove the previous hacky-er attempt at this that was named "split dll". > > TBR=jam@chromium.org > > BUG=237249,256965 > > Review URL: https://codereview.chromium.org/17619005 TBR=scottmg@chromium.org Review URL: https://codereview.chromium.org/19572012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212239 0039d316-1c4b-4281-b951-d872f2087c98
* Create top-level separate targets for browser and child dllsscottmg@chromium.org2013-07-181-7/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | The general idea is that there's top level targets chrome and chrome_child, and corresponding content_app and content_app_child that depend on only the subtargets that should be included in the appropriate dll. Pull bluetooth_utils from bluetooth_device into separate common target as it's referenced from chrome/common/extensions. Currently (probably) Windows-only and requires setting chrome_multiple_dll=1 for gyp. Links, but Blink is still included in browser. Single-process mode is currently disabled when chrome_multiple_dll is set. Current graph is at: http://commondatastorage.googleapis.com/chromelinkgraph/deps.html generated by "python tools\win\split_link\graph_dependencies.py deps.html" Remove the previous hacky-er attempt at this that was named "split dll". TBR=jam@chromium.org BUG=237249,256965 Review URL: https://codereview.chromium.org/17619005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212230 0039d316-1c4b-4281-b951-d872f2087c98
* remove wrong chrome_split_dll ifdefsscottmg@chromium.org2013-05-171-4/+2
| | | | | | | | | | | | | | In an attempt to get the renderer to load. These were supposed to be refactored to split the affected files into two parts, but that will be attempted later. TBR=jam@chromium.org R=cpu@chromium.org BUG=237249 Review URL: https://chromiumcodereview.appspot.com/14702007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@200890 0039d316-1c4b-4281-b951-d872f2087c98
* Add chrome_split_dll gyp variable, and duplicate chrome_main_dll target (reland)scottmg@chromium.org2013-05-081-2/+4
| | | | | | | | | | | | | | | | | Currently contains chrome_browser_dll target. Removes some paths from browser->webcore via content that are there due to single process mode, and removes dependency of content on content_renderer. Current remaining paths from chrome_browser_dll to webcore: http://i.imgur.com/7WWRvpA.jpg Reland of https://chromiumcodereview.appspot.com/14682014 TBR=cpu@chromium.org BUG=237249 Review URL: https://codereview.chromium.org/14794004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@198928 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 198834 "Add chrome_split_dll gyp variable, and duplicate ..."dewittj@chromium.org2013-05-081-4/+2
| | | | | | | | | | | | | | | | | | | | | > Add chrome_split_dll gyp variable, and duplicate chrome_main_dll target > > Currently contains chrome_browser_dll target. Removes some paths from browser->webcore > via content that are there due to single process mode, and removes dependency of content > on content_renderer. > > Current remaining paths from chrome_browser_dll to webcore: http://i.imgur.com/7WWRvpA.jpg > > R=cpu@chromium.org > BUG=237249 > > Review URL: https://chromiumcodereview.appspot.com/14682014 TBR=scottmg@chromium.org Review URL: https://codereview.chromium.org/14882004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@198837 0039d316-1c4b-4281-b951-d872f2087c98
* Add chrome_split_dll gyp variable, and duplicate chrome_main_dll targetscottmg@chromium.org2013-05-081-2/+4
| | | | | | | | | | | | | | | Currently contains chrome_browser_dll target. Removes some paths from browser->webcore via content that are there due to single process mode, and removes dependency of content on content_renderer. Current remaining paths from chrome_browser_dll to webcore: http://i.imgur.com/7WWRvpA.jpg R=cpu@chromium.org BUG=237249 Review URL: https://chromiumcodereview.appspot.com/14682014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@198834 0039d316-1c4b-4281-b951-d872f2087c98
* First step towards component build for Android.yfriedman@chromium.org2012-11-012-4/+4
| | | | | | | | | | Add symbol exports needed to build content shell. BUG=158821 Review URL: https://codereview.chromium.org/11368031 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@165420 0039d316-1c4b-4281-b951-d872f2087c98
* Move sandbox code in content to content namespace.jam@chromium.org2012-10-231-2/+1
| | | | | | Review URL: https://codereview.chromium.org/11228040 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@163656 0039d316-1c4b-4281-b951-d872f2087c98
* Exclude Mac and Linux-specific ContentMainDelegate functions on iOSstuartmorgan@chromium.org2012-09-272-4/+4
| | | | | | | | | | | | These functions are platform-specific; the ifdefs need to be adjusted to account for iOS BUG=None Review URL: https://chromiumcodereview.appspot.com/10983054 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@158997 0039d316-1c4b-4281-b951-d872f2087c98
* Enable a minimal content/ build on iOSstuartmorgan@chromium.org2012-09-181-0/+15
| | | | | | | | | | | | | | | | | | | | This removes some files from the already-upstreamed iOS content/ gyp support in order to get a minimal target building while the remaining content/ changes are upstreamed. Minor ifdefing is necessary in a few files in order to build them on iOS; these are included since they are core files without which it's very difficult to bring up a build at all. Adds one new class to the ui/ build since it's needed by the content/ code that is now built. BUG=None Review URL: https://chromiumcodereview.appspot.com/10933091 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@157421 0039d316-1c4b-4281-b951-d872f2087c98
* Remove #pragma once from contentajwong@chromium.org2012-07-114-5/+1
| | | | | | Review URL: https://chromiumcodereview.appspot.com/10696166 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@146071 0039d316-1c4b-4281-b951-d872f2087c98
* Undo the startup_helper_win.h change in r143501 because that breaks the ↵jam@chromium.org2012-06-221-3/+3
| | | | | | | | sandbox in component builds. Review URL: https://chromiumcodereview.appspot.com/10638010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@143515 0039d316-1c4b-4281-b951-d872f2087c98
* Enable incremental linking on browser_tests and unit_tests.jam@chromium.org2012-06-221-1/+4
| | | | | | | This is based off scottmg's https://chromiumcodereview.appspot.com/10572043/ and after r143272. Review URL: https://chromiumcodereview.appspot.com/10644003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@143501 0039d316-1c4b-4281-b951-d872f2087c98
* Added sandboxed process service.michaelbai@chromium.org2012-06-121-0/+4
| | | | | | | | | | BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/10546079 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@141618 0039d316-1c4b-4281-b951-d872f2087c98
* Simplify how Content*Client interfaces are created. Instead of depending on ↵jam@chromium.org2012-06-053-0/+42
| | | | | | | | | | | the embedder to know when to create and set them and to handle special cases like zygote/single-process, directly ask the embedder to create an instance of a specific type. Also, if the embedder doesn't return an instance create the empty version. Remove MockContentRendererClient since it existed before ContentRendererClient had an implementation and has no need anymore. Rename MockContentBrowserClient to TestContentBrowserClient to better reflect how it's used. BUG=98716 Review URL: https://chromiumcodereview.appspot.com/10479023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140524 0039d316-1c4b-4281-b951-d872f2087c98
* As part of the content_shell bring up, some un-upstreamed featuresmichaelbai@chromium.org2012-06-041-1/+8
| | | | | | | | | | | | | | | | | | | | have been disabled in browser process main related c++ and Java file. The disabled features are guarded by !defined(ANDROID_UPSTREAM_BRINGUP). For Java file, the code was removed. Fixed the dependency. - Moved the content_jni_registrar.{h|cc} and library_loader_hooks.cc content/app/android/ - Moved the android_library_loader_hooks.h to content/public/app/ BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/10444121 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140386 0039d316-1c4b-4281-b951-d872f2087c98
* Fixed the dependency.michaelbai@chromium.org2012-06-011-0/+23
| | | | | | | | | | | | | | | | - Moved the content_jni_registrar.{h|cc} and library_loader_hooks.cc to content/app/android/ - Moved the android_library_loader_hooks.h to content/public/app/ Those files execute the common tasks for all processes and should belong to content/app/. BUG= TEST= TBR=jrg Review URL: https://chromiumcodereview.appspot.com/10444113 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140062 0039d316-1c4b-4281-b951-d872f2087c98
* Give ContentMainDelegate a default implementation to simplify embedders.jam@chromium.org2012-05-302-12/+56
| | | | | | | BUG=98716 Review URL: https://chromiumcodereview.appspot.com/10458034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139582 0039d316-1c4b-4281-b951-d872f2087c98
* Get chrome:// dev tool urls hooked up in content_shell.michaeln@google.com2012-04-201-5/+5
| | | | | | Review URL: https://chromiumcodereview.appspot.com/9950040 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133107 0039d316-1c4b-4281-b951-d872f2087c98
* Support sharing of ContentMain and BrowserMain code with embedded use cases ↵marshall@chromium.org2012-02-103-2/+102
| | | | | | | | | | | | | | | | | | | | (try #3). For the browser use case it is convenient to have a single ContentMain entry point function that handles all initialization, run and shutdown. For embedded use cases it is often necessary to integrate with existing application message loops where initialization and shutdown must be handled separately. To support sharing of this code the following changes were required: 1. Refactor the ContentMain function to create a ContentMainRunner class containing separate initialization, run and shutdown functions. 2. Refactor the BrowserMain function and BrowserMainLoop class to create a BrowserMainRunner class containing separate initialization, run and shutdown functions. 3. Add a new BrowserMainParts::GetMainMessageLoop method. This is necessary to support creation of a custom MessageLoop implementation while sharing BrowserMainRunner initialization and shutdown code. BUG=112507 TEST=none Review URL: https://chromiumcodereview.appspot.com/9375017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121454 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 121236 - Support sharing of ContentMain and BrowserMain code with ↵marshall@chromium.org2012-02-093-102/+2
| | | | | | | | | embedded use cases (try #2). Tests failing. Review URL: https://chromiumcodereview.appspot.com/9372027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121245 0039d316-1c4b-4281-b951-d872f2087c98
* Support sharing of ContentMain and BrowserMain code with embedded use cases ↵marshall@chromium.org2012-02-093-2/+102
| | | | | | | | | | | | | | | | | | | | (try #2). For the browser use case it is convenient to have a single ContentMain entry point function that handles all initialization, run and shutdown. For embedded use cases it is often necessary to integrate with existing application message loops where initialization and shutdown must be handled separately. To support sharing of this code the following changes were required: 1. Refactor the ContentMain function to create a ContentMainRunner class containing separate initialization, run and shutdown functions. 2. Refactor the BrowserMain function and BrowserMainLoop class to create a BrowserMainRunner class containing separate initialization, run and shutdown functions. 3. Add a new BrowserMainParts::GetMainMessageLoop method. This is necessary to support creation of a custom MessageLoop implementation while sharing BrowserMainRunner initialization and shutdown code. BUG=112507 TEST=none Review URL: https://chromiumcodereview.appspot.com/9347022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121236 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Support sharing of ContentMain and BrowserMain code with embedded ↵evan@chromium.org2012-02-063-102/+2
| | | | | | | | use cases." This reverts commit r120574. Test failures. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@120581 0039d316-1c4b-4281-b951-d872f2087c98
* Support sharing of ContentMain and BrowserMain code with embedded use cases.marshall@chromium.org2012-02-063-2/+102
| | | | | | | | | | | | | | | | | | For the browser use case it is convenient to have a single ContentMain entry point function that handles all initialization, run and shutdown. For embedded use cases it is often necessary to integrate with existing application message loops where initialization and shutdown must be handled separately. To support sharing of this code the following changes were required: 1. Refactor the ContentMain function to create a ContentMainRunner class containing separate initialization, run and shutdown functions. 2. Refactor the BrowserMain function and BrowserMainLoop class to create a BrowserMainRunner class containing separate initialization, run and shutdown functions. 3. Add a new BrowserMainParts::GetMainMessageLoop method. This is necessary to support creation of a custom MessageLoop implementation while sharing BrowserMainRunner initialization and shutdown code. BUG=112507 TEST=none Review URL: https://chromiumcodereview.appspot.com/9190018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@120574 0039d316-1c4b-4281-b951-d872f2087c98
* Move content_restriction.h and main_function_params.h to ↵jam@chromium.org2011-10-311-4/+4
| | | | | | | | | content/public/common, and put them in the content namespace. BUG=98716 Review URL: http://codereview.chromium.org/8387039 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108004 0039d316-1c4b-4281-b951-d872f2087c98
* Expose the sandbox related code through the content API. I did a bit of ↵jam@chromium.org2011-10-291-0/+34
| | | | | | | | | | | | | cleanup while I was doing this. -got rid of SandboxInitWrapper, since I didn't see a need to expose given that we can just expose sandbox::SandboxInterfaceInfo -got rid of the duplicated code to initialize the broker -since I made MainFunctionParams only have the sandbox struct on Windows, I also made the mac specific auto release pool behind an ifdef as well. It seemed odd to make something so mac specific compile on all platforms to save some #ifdefs. BUG=98716 Review URL: http://codereview.chromium.org/8414020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@107863 0039d316-1c4b-4281-b951-d872f2087c98
* Move ZygoteForkDelegateLinux to content/public/common.jam@chromium.org2011-10-251-2/+3
| | | | | | | BUG=98716 Review URL: http://codereview.chromium.org/8381029 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@107128 0039d316-1c4b-4281-b951-d872f2087c98
* Move ContentMainDelegate to content/public/.joi@chromium.org2011-10-201-0/+73
Mostly a trivial move since the implementation for the class (now deleted) was do-nothing and the only subclass that didn't have a full implementation was ShellMainDelegate. BUG=98716 TEST=it builds + existing tests Review URL: http://codereview.chromium.org/8356025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106549 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-04 10:11:23 +0000