chromium_src.git - central chromium sources

	Commit message (Collapse)	Author	Age	Files	Lines
*	Python script to generate Chromoting's main.html.	garykac@chromium.org	2014-02-20	1	-20/+0
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	With this change, it will be much easier to make changes to the UX (since the dialogs will be easier to manage) and the set of JavaScript includes will be guaranteed to match the gyp target. This change also auto-generates the wcs_sandbox.html file. BUG= R=jamiewalch@chromium.org Review URL: https://codereview.chromium.org/146903006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252135 0039d316-1c4b-4281-b951-d872f2087c98
*	Make host/url references configurable.	rmsousa@chromium.org	2013-02-05	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	In C++, they're all passed as optional command line parameters (like google_apis/gaia already allows us to do with the gaia oauth urls). So one can start the host with a monstrosity such as: out/Debug/remoting_me2me_host out/Debug/remoting_start_host --gaia-host=accounts.google.com --oauth-user-info-url=https://www.googleapis.com/oauth2/v1/userinfo --chromoting-bot-jid=remoting@bot.talk.google.com --chromoting-base-url=https://www.googleapis.com/chromoting/v1 --talk-server-host=talk.google.com --talk-server-port=5222 -[-disable-talk-server-tls] --oauth2-token-url=https://accounts.google.com/o/oauth2/token In Javascript and IT2Me, unfortunately we don't have a command line, so instead we put all these settings in plugin_settings.js, and the javascript passes them all into the it2me plugin as appropriate. They can then be changed by manually hacking plugin_settings.js and manifest.json in the build output, changing the remoting.settings object at runtime (although any new hosts you configure that are not in the manifest's CSP won't work), or, preferrably, by passing them via environment variables to the build, and letting build-webapp.py do its magic - for example, like with this: GOOGLE_CLIENT_ID_REMOTING=<clientid> GOOGLE_CLIENT_SECRET_REMOTING=<secret> OAUTH2_ACCOUNTS_HOST=https://accounts.google.com OAUTH2_API_HOST=https://www.googleapis.com CHROMOTING_BOT_JID=remoting@bot.talk.google.com CHROMOTING_API_HOST=https://www.googleapis.com TALK_SERVER_HOST=talk.google.com TALK_SERVER_PORT=5222 TALK_SERVER_USE_TLS=true TALK_GADGET_HOST_SUFFIX=talkgadget.google.com OAUTH2_REDIRECT_HOST_PREFIX=https://chromoting-oauth. TALK_GADGET_HOST_PREFIX=https://chromoting-client. ninja -C out/Debug remoting_webapp I've tested with me2me (host and client) and it2me (share and access), and verified both that the defaults work as before (without command line parameters), and that I can substitute test server hostnames in all of those parameters. BUG= Review URL: https://chromiumcodereview.appspot.com/11346040 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@180622 0039d316-1c4b-4281-b951-d872f2087c98
*	Fixed missing references in wcs_sandbox.html.	jamiewalch@chromium.org	2013-02-03	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \|	This broke the error handling path. BUG=134213 Review URL: https://chromiumcodereview.appspot.com/12091112 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@180298 0039d316-1c4b-4281-b951-d872f2087c98
*	Get Chromoting client working in Apps V2	jamiewalch@chromium.org	2013-01-29	1	-0/+18
	This involves the following: 1. Removing chrome extension API calls from wcs.js and wcs_loader.js. 2. Moving those files into a separate <iframe> sandbox. 3. Adding a postMessage-based API to communicate with the rest of the code. 4. Working around miscellaneous sandbox restrictions. BUG=134213 Review URL: https://chromiumcodereview.appspot.com/12021029 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@179413 0039d316-1c4b-4281-b951-d872f2087c98