summaryrefslogtreecommitdiffstats
path: root/remoting/tools
Commit message (Collapse)AuthorAgeFilesLines
* Remove obsolete scripts from remoting.sergeyu@chromium.org2013-08-148-741/+0
| | | | | | | | | These scripts haven't been updated for long time and most of them probably don't work anymore. Review URL: https://chromiumcodereview.appspot.com/23104003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@217419 0039d316-1c4b-4281-b951-d872f2087c98
* Added script to test native messaging for Chromoting.jamiewalch@chromium.org2013-08-031-0/+153
| | | | | | | | This should help us debug the host component without needing to use the web-app. Review URL: https://chromiumcodereview.appspot.com/21680003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215488 0039d316-1c4b-4281-b951-d872f2087c98
* Cleanup chromoting host config handling on Linux.sergeyu@chromium.org2013-08-031-23/+4
| | | | | | | | | | | | | | | | | | | | 1. Host config was previously passed through stdin by specifying --host-config=/dev/stdin . But the host process wasn't aware that the config is read from stdin - it still watched /dev/stdin, which leads to wrong behaviour when OS is upgraded (watch notification is fired for /dev/stdin). 2. Previous the daemon script would erase content of the host config when host exits with the error code indicating that the config is invalid. There is no reason to do that anymore. Cleanup that code so the config is erased only when the host is delete from the directory (crbug.com/179416). BUG=264910 R=lambroslambrou@chromium.org Review URL: https://codereview.chromium.org/20776003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215436 0039d316-1c4b-4281-b951-d872f2087c98
* Localized Chromoting Host on Mac and Linux.alexeypa@chromium.org2013-07-313-4/+174
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Re-landing r214379. Two additional fixes: - HOST_PLUGIN_MIME_TYPE is passed unquoted making the code the uses it responsible for stringizing it. - msvs_cygwin_shell is set to 0 to avoid cygpath changing "remoting_locales\nl.pak" to "remoting_ocales\nl.pak". This CL implements generation of localizable strings from remoting_strings.grd file. Depending on the platform the localized resources are placed to: - Mac: localized .string and .pak resources are added to each application bundle under 'Resources/<locale>.lproj' - Linux: localized .pak files are placed under 'remoting_locales' directory next to the binary locading them. - Windows: .rc resources are generated from .jinja2 templates and embedded into a relevant binary. Chrome l10n and i18n APIs are used to retrieve the current locale and RTL flag (Mac & Linux). The it2me plugin sets the locale to match the locale of the browser. Collateral changes: - UiString is not used any more. - Increased width of disconnect window message on Mac. - The host plugin version is correctly reported on Mac. - Dialogs use RTL templates in case of RTL languages. No more updating the templates dynamically (Windows). - remoting_unittests.ResourcesTest now runs on Mac, LInux and Windows. - '@' is used for variable substitutions by remoting_localize.py. - HOST_PLUGIN_MIME_TYPE is defined in one place now. - Deleted unused commong_resources.grd. Mac installer and preference panel are not localized yet. BUG=155204 Review URL: https://chromiumcodereview.appspot.com/21059003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@214855 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 214379 "Localized Chromoting Host on Mac and Linux."alexeypa@google.com2013-07-303-174/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The CL broke "Google Chrome Win" in a strange way: http://build.chromium.org/p/chromium.chrome/builders/Google%20Chrome%20Win/builds/19799/steps/compile/logs/stdio 671> Traceback (most recent call last): 671> File "webapp/build-webapp.py", line 331, in <module> 671> sys.exit(main()) 671> File "webapp/build-webapp.py", line 327, in main 671> sys.argv[5], sys.argv[6], files, locales, patches) 671> File "webapp/build-webapp.py", line 141, in buildWebApp 671> shutil.copy2(current_locale, destination_file) 671> File "c:\b\build\slave\google-chrome-rel-win\build\src\third_party\python_26\lib\shutil.py", line 99, in copy2 671> copyfile(src, dst) 671> File "c:\b\build\slave\google-chrome-rel-win\build\src\third_party\python_26\lib\shutil.py", line 52, in copyfile 671> fsrc = open(src, 'rb') 671> IOError: [Errno 2] No such file or directory: 'c:/b/build/slave/google-chrome-rel-win/build/src/build/Release/\\remoting_ocales\\nl.pak' 671>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(151,5): error MSB6006: "cmd.exe" exited with code 1. > Localized Chromoting Host on Mac and Linux. > > Re-landing r213997. TBR because this is a trivial, mechanical fix. > > This CL implements generation of localizable strings from remoting_strings.grd file. Depending on the platform the localized resources are placed to: > - Mac: localized .string and .pak resources are added to each application bundle under 'Resources/<locale>.lproj' > - Linux: localized .pak files are placed under 'remoting_locales' directory next to the binary locading them. > - Windows: .rc resources are generated from .jinja2 templates and embedded into a relevant binary. > > Chrome l10n and i18n APIs are used to retrieve the current locale and RTL flag (Mac & Linux). The it2me plugin sets the locale to match the locale of the browser. > > Collateral changes: > - UiString is not used any more. > - Increased width of disconnect window message on Mac. > - The host plugin version is correctly reported on Mac. > - Dialogs use RTL templates in case of RTL languages. No more updating the templates dynamically (Windows). > - remoting_unittests.ResourcesTest now runs on Mac, LInux and Windows. > - '@' is used for variable substitutions by remoting_localize.py. > - HOST_PLUGIN_MIME_TYPE is defined in one place now. > - Deleted unused commong_resources.grd. > > Mac installer and preference panel are not localized yet. > > TBR=garykac@chromium.org > BUG=155204 > > Review URL: https://codereview.chromium.org/20985002 TBR=alexeypa@chromium.org Review URL: https://codereview.chromium.org/21090006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@214401 0039d316-1c4b-4281-b951-d872f2087c98
* Localized Chromoting Host on Mac and Linux.alexeypa@chromium.org2013-07-303-4/+174
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Re-landing r213997. TBR because this is a trivial, mechanical fix. This CL implements generation of localizable strings from remoting_strings.grd file. Depending on the platform the localized resources are placed to: - Mac: localized .string and .pak resources are added to each application bundle under 'Resources/<locale>.lproj' - Linux: localized .pak files are placed under 'remoting_locales' directory next to the binary locading them. - Windows: .rc resources are generated from .jinja2 templates and embedded into a relevant binary. Chrome l10n and i18n APIs are used to retrieve the current locale and RTL flag (Mac & Linux). The it2me plugin sets the locale to match the locale of the browser. Collateral changes: - UiString is not used any more. - Increased width of disconnect window message on Mac. - The host plugin version is correctly reported on Mac. - Dialogs use RTL templates in case of RTL languages. No more updating the templates dynamically (Windows). - remoting_unittests.ResourcesTest now runs on Mac, LInux and Windows. - '@' is used for variable substitutions by remoting_localize.py. - HOST_PLUGIN_MIME_TYPE is defined in one place now. - Deleted unused commong_resources.grd. Mac installer and preference panel are not localized yet. TBR=garykac@chromium.org BUG=155204 Review URL: https://codereview.chromium.org/20985002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@214379 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 213997 "Localized Chromoting Host on Mac and Linux."alexeypa@google.com2013-07-263-174/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It passed CQ but broke Linux Builder. I'm filing a bug agains CQ. > Localized Chromoting Host on Mac and Linux. > > This CL implements generation of localizable strings from remoting_strings.grd file. Depending on the platform the localized resources are placed to: > - Mac: localized .string and .pak resources are added to each application bundle under 'Resources/<locale>.lproj' > - Linux: localized .pak files are placed under 'remoting_locales' directory next to the binary locading them. > - Windows: .rc resources are generated from .jinja2 templates and embedded into a relevant binary. > > Chrome l10n and i18n APIs are used to retrieve the current locale and RTL flag (Mac & Linux). The it2me plugin sets the locale to match the locale of the browser. > > Collateral changes: > - UiString is not used any more. > - Increased width of disconnect window message on Mac. > - The host plugin version is correctly reported on Mac. > - Dialogs use RTL templates in case of RTL languages. No more updating the templates dynamically (Windows). > - remoting_unittests.ResourcesTest row runs on Mac, LInux and Windows. > - '@' is used for variable substitutions by remoting_localize.py. > - HOST_PLUGIN_MIME_TYPE is defined in one place now. > - Deleted unused commong_resources.grd. > > Mac installer and preference panel are not localized yet. > > BUG=155204 > > Review URL: https://chromiumcodereview.appspot.com/19803010 TBR=alexeypa@chromium.org Review URL: https://codereview.chromium.org/20854002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213998 0039d316-1c4b-4281-b951-d872f2087c98
* Localized Chromoting Host on Mac and Linux.alexeypa@chromium.org2013-07-263-4/+174
| | | | | | | | | | | | | | | | | | | | | | | | | | | This CL implements generation of localizable strings from remoting_strings.grd file. Depending on the platform the localized resources are placed to: - Mac: localized .string and .pak resources are added to each application bundle under 'Resources/<locale>.lproj' - Linux: localized .pak files are placed under 'remoting_locales' directory next to the binary locading them. - Windows: .rc resources are generated from .jinja2 templates and embedded into a relevant binary. Chrome l10n and i18n APIs are used to retrieve the current locale and RTL flag (Mac & Linux). The it2me plugin sets the locale to match the locale of the browser. Collateral changes: - UiString is not used any more. - Increased width of disconnect window message on Mac. - The host plugin version is correctly reported on Mac. - Dialogs use RTL templates in case of RTL languages. No more updating the templates dynamically (Windows). - remoting_unittests.ResourcesTest row runs on Mac, LInux and Windows. - '@' is used for variable substitutions by remoting_localize.py. - HOST_PLUGIN_MIME_TYPE is defined in one place now. - Deleted unused commong_resources.grd. Mac installer and preference panel are not localized yet. BUG=155204 Review URL: https://chromiumcodereview.appspot.com/19803010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213997 0039d316-1c4b-4281-b951-d872f2087c98
* Generate the lists of localization files instead of hardcoding them.alexeypa@chromium.org2013-07-113-64/+121
| | | | | | | | | | | | | | | | | | | | This CL modifies remoting/tools/localize.py script such that it can: - be invoked via 'pymod_do_main' filter. - generate a separate output file for each locale/language. - produce the list of output files for given set of parameters. remoting.gyp now generates the lists of .pak and message.json files invoking the script via 'pymod_do_main' filter. 'pymod_do_main' is necessary to pass paths unaltered between GYP and python. The script was also renamed to remoting/tools/build/remoting_localize.py to avoid potential name clashes since the script is globally visible now. TBR is for the DEPS changes only. TBR=cpu@chromium.org BUG=155204 Review URL: https://chromiumcodereview.appspot.com/18868009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@211227 0039d316-1c4b-4281-b951-d872f2087c98
* Localized Chromoting Host on Windows.alexeypa@chromium.org2013-07-093-1/+724
| | | | | | | | | | | | | | | | This CL introduces remoting/tools/localize.py script. The script is based on Jinja2 templating language. It is used to generate localizable resources (string table, dialogs, message table and version information) from a common template. The translated strings are taken from json files (used by the webapp as well), which, in turn, are generated from remoting_strings.grd. Collateral changes: - Branding of Window resources has been moved to remoting_strings.grd. .ver files are not used anymore. - Updated verify_resources.py so that it could recognize strings used by Jinja2 templates. - Fixed the dialog layouts for RTL languages. TBR=cpu@chromium.org BUG=155204 Review URL: https://chromiumcodereview.appspot.com/18323017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@210591 0039d316-1c4b-4281-b951-d872f2087c98
* Add notification when the host successfully starts.rmsousa@chromium.org2013-06-121-41/+169
| | | | | | | | | | | | This adds a listener for when first heartbeat is successful, which I think is the best signal that everything is working and the host is able to receive connections. On Linux, that can send a signal if requested by the caller. On the script side, when running as a daemon, we create a pipe that allows the parent process to wait for that signal (or a permanent failure), and dump all Python log input to the STDERR. This gives users a much better feedback about whether starting the host worked or not. BUG=179419 Review URL: https://chromiumcodereview.appspot.com/16448005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@205837 0039d316-1c4b-4281-b951-d872f2087c98
* Remove host/auth config based on Linux Me2Me host exit codes.lambroslambrou@chromium.org2013-06-061-0/+2
| | | | | | | | | | | | | The Linux Me2Me script wasn't reacting properly to certain exit codes from the Host process, because the Config object wasn't been marked as changed after keys were removed. BUG=179416 Review URL: https://chromiumcodereview.appspot.com/16484002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@204471 0039d316-1c4b-4281-b951-d872f2087c98
* LogExts API Logging Manifest describing the interfaces of the Remote Desktop ↵alexeypa@chromium.org2013-05-071-0/+848
| | | | | | | | | | | | ActiveX control. This manifest can be used to trace calls of COM interfaces exposed by the Remote Desktop ActiveX control. This file is for debugging purposes only. It is not used during the build. R=jamiewalch@chromium.org Review URL: https://codereview.chromium.org/14580016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@198747 0039d316-1c4b-4281-b951-d872f2087c98
* Write pulseaudio config on chromoting host to set default sampling rate to ↵sergeyu@chromium.org2013-05-011-4/+10
| | | | | | | | | | | 48000. BUG=221755 R=wez@chromium.org Review URL: https://codereview.chromium.org/14577003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@197693 0039d316-1c4b-4281-b951-d872f2087c98
* Disable Composite iff running Unity 2D.wez@chromium.org2013-04-061-1/+9
| | | | | | | | | | | This works-around an issue in the Metacity compositor, used by Unity 2D. BUG=166468 Review URL: https://chromiumcodereview.appspot.com/13746003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192755 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Disable the Composite extension for in virtual X sessions."wez@chromium.org2013-03-221-3/+0
| | | | | | | | | | | Disabling the Composite extension works around broken XDAMAGE notifications under Metacity but breaks some other desktop environments, e.g. Cinnamon. BUG=222732,166468 Review URL: https://codereview.chromium.org/12582008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@189886 0039d316-1c4b-4281-b951-d872f2087c98
* Disable the Composite extension for in virtual X sessions.wez@chromium.org2013-03-181-6/+10
| | | | | | | | | | | | | | Disabling the Composite extension prevents the default Unity 2D session from running with the Metacity compositor enabled. The compositor doesn't seem to affect the appearance of the session but does appear to break DAMAGE notifications in some cases. BUG=166468 Review URL: https://chromiumcodereview.appspot.com/12542018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@188782 0039d316-1c4b-4281-b951-d872f2087c98
* Improve PID-file handling in Linux Me2Me script.lambroslambrou@chromium.org2013-03-101-100/+36
| | | | | | | | | BUG=166068,178102 Review URL: https://chromiumcodereview.appspot.com/12377030 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187185 0039d316-1c4b-4281-b951-d872f2087c98
* Apply different back-off periods depending on how often a process has failed ↵jamiewalch@chromium.org2013-02-281-11/+24
| | | | | | | | | | | to start. BUG=177417 Review URL: https://chromiumcodereview.appspot.com/12317140 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@185117 0039d316-1c4b-4281-b951-d872f2087c98
* Fix pylint warnings.jamiewalch@chromium.org2013-02-271-19/+17
| | | | | | Review URL: https://codereview.chromium.org/12316147 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@185076 0039d316-1c4b-4281-b951-d872f2087c98
* Improve gksudo prompt when enabling chromoting host.sergeyu@chromium.org2013-02-091-6/+7
| | | | | | | | | | | | | 1. gksudo prompt timeout has been increased to 5 minutes, 2. gksudo is killed when the timeout expires, 3. gksudo is launched with -D instead of -m. BUG=155920,167791 Review URL: https://chromiumcodereview.appspot.com/12207086 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@181599 0039d316-1c4b-4281-b951-d872f2087c98
* Load /etc/environment in Me2Me sessionlambroslambrou@chromium.org2013-01-121-0/+21
| | | | | | | | | | | | | | This is a "quick fix". A much better fix would be to use the system's Display Manager (for example, lightdm) to start sessions. BUG=169641 NOTRY=true Review URL: https://chromiumcodereview.appspot.com/11874014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@176492 0039d316-1c4b-4281-b951-d872f2087c98
* Improve error log when failed to load configlambroslambrou@google.com2013-01-111-21/+38
| | | | | | | | | | | | This replaces the undefined "config_filename" error with a better message indicating the cause of the error when loading the config. BUG=167817 NOTRY=true Review URL: https://codereview.chromium.org/11711004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@176237 0039d316-1c4b-4281-b951-d872f2087c98
* Remove XSESSION_COMMAND from Me2Me scriptlambroslambrou@chromium.org2013-01-051-29/+6
| | | | | | | | | | | | | This also removes the warning shown when running Unity 2D desktop - it's been working fine for quite a while. BUG=168374 Review URL: https://chromiumcodereview.appspot.com/11791002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@175259 0039d316-1c4b-4281-b951-d872f2087c98
* Set Virtual Me2Me desktop's initial DPI to 96lambroslambrou@chromium.org2013-01-051-9/+9
| | | | | | | | | | | BUG=168210 TEST=Before any client connects, "xdpyinfo -display :20|grep -A1 dimensions" shows ~96dpi. NOTRY=true Review URL: https://chromiumcodereview.appspot.com/11782006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@175240 0039d316-1c4b-4281-b951-d872f2087c98
* Improve xsession executionlambroslambrou@chromium.org2013-01-041-2/+6
| | | | | | | | | | | | | | | When running a custom xsession (such as ~/.xsession), execute it with /bin/sh -c, which copes better with scripts that have the executable permission set, but don't have a she-bang line, for example. BUG=167409 TEST=Verify with ~/.xsession executable but no she-bang. Also verify with default unity-2d session on Precise. NOTRY=true Review URL: https://chromiumcodereview.appspot.com/11715003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@175212 0039d316-1c4b-4281-b951-d872f2087c98
* Add trailing space to sudo promptlambroslambrou@chromium.org2013-01-021-1/+2
| | | | | | | | | | BUG=167390 NOTRY=true Review URL: https://chromiumcodereview.appspot.com/11702002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@174817 0039d316-1c4b-4281-b951-d872f2087c98
* Don't set XAUTHORITY in Virtual Me2Me parent processlambroslambrou@chromium.org2012-12-271-5/+7
| | | | | | | | | | | | | | | Instead, pass the Xauthority filename directly to "xauth add" using the -f option. Problem was that setting XAUTHORITY to a non-existent file broke "gksudo" when the Me2Me script was run with "--add-user". BUG=166948 TEST=Try to setup and start a Chromoting host on an account where ~/.Xauthority is not present. NOTRY=true Review URL: https://chromiumcodereview.appspot.com/11642057 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@174692 0039d316-1c4b-4281-b951-d872f2087c98
* [Chromoting] Add script to switch release channels.garykac@chromium.org2012-12-191-0/+68
| | | | | | Review URL: https://codereview.chromium.org/11154023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@174037 0039d316-1c4b-4281-b951-d872f2087c98
* Source Python from /usr/bin rather than the user's path.skonig@chromium.org2012-12-191-1/+1
| | | | | | | | | | | | | | | It's possible for multiple versions of Python to be installed. Sourcing from the path can cause us to load the wrong version, causing the script to fail. Sourcing from /usr/bin ensures that the version we declare a dependency for is the one that's used. BUG=166591 Test=Manual Review URL: https://chromiumcodereview.appspot.com/11644022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@173986 0039d316-1c4b-4281-b951-d872f2087c98
* Increase default maximum desktop size and make it configurable.jamiewalch@google.com2012-12-141-6/+17
| | | | | | | | BUG=166099 Review URL: https://codereview.chromium.org/11566037 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@173214 0039d316-1c4b-4281-b951-d872f2087c98
* Fix me2me_virtual_host.py to handle blocked user accounts properly.sergeyu@chromium.org2012-12-111-2/+6
| | | | | | | | | Previously the host daemon wasn't handling correctly error codes 103 and 105. This was a caused by merge conflict between crrev.com/10830225 and crrev.com/10823083. Review URL: https://codereview.chromium.org/11535010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@172430 0039d316-1c4b-4281-b951-d872f2087c98
* Fixed potential umask bug.jamiewalch@chromium.org2012-11-171-2/+3
| | | | | | Review URL: https://chromiumcodereview.appspot.com/11316061 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168425 0039d316-1c4b-4281-b951-d872f2087c98
* Add an option to run the remoting session script with a specific config.wez@chromium.org2012-11-171-8/+21
| | | | | | | | | | | This is primarily useful when running the script foregrounded, for debugging. Also adds some comments to clarify the script's initialization steps. Review URL: https://chromiumcodereview.appspot.com/11348080 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168399 0039d316-1c4b-4281-b951-d872f2087c98
* replace verify-webapp.py script with verify_resources.pysergeyu@chromium.org2012-11-121-0/+155
| | | | | | | | | verify-webapp.py was lookin only in webapp sources. The new verify_resources.py verifies all source files and not only webapp. Review URL: https://codereview.chromium.org/11362072 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167224 0039d316-1c4b-4281-b951-d872f2087c98
* Move Chromoting strings to string_resources.grd and simplify ↵sergeyu@chromium.org2012-11-062-46/+190
| | | | | | | | | | | | | | | | | | remoting_resources target. Previously all strings were in messages.json files. Moving them to GRD file will allow to share them with native components. Also simplified how resources are generated: 1. Now <if> is used to handle branded strings instead of generating grd file in build time 2. Removed resource_ids - ids are now specified in grd files. BUG=158995 Review URL: https://chromiumcodereview.appspot.com/11275101 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166127 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Move Chromoting strings to string_resources.grd and simplify ↵phajdan.jr@chromium.org2012-11-052-190/+46
| | | | | | | | remoting_resources target." This reverts commit f5dfed801f9358411900c4f9ca58ef0a11cce9ae. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166069 0039d316-1c4b-4281-b951-d872f2087c98
* Move Chromoting strings to string_resources.grd and simplify ↵sergeyu@chromium.org2012-11-052-46/+190
| | | | | | | | | | | | | | | | | remoting_resources target. Previously all strings were in messages.json files. Moving them to GRD file will allow to share them with native components. Also simplified how resources are generated: 1. Now <if> is used to handle branded strings instead of generating grd file in build time 2. Removed resource_ids - ids are now specified in grd files. BUG=158995 Review URL: https://codereview.chromium.org/11275101 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166068 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 166003 - Move Chromoting strings to string_resources.grd and simplify ↵sergeyu@chromium.org2012-11-052-190/+46
| | | | | | | | | | | | | | | | | | | | remoting_resources target. Previously all strings were in messages.json files. Moving them to GRD file will allow to share them with native components. Also simplified how resources are generated: 1. Now <if> is used to handle branded strings instead of generating grd file in build time 2. Removed resource_ids - ids are now specified in grd files. BUG=158995 Review URL: https://codereview.chromium.org/11275101 TBR=sergeyu@chromium.org Review URL: https://codereview.chromium.org/11365095 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166013 0039d316-1c4b-4281-b951-d872f2087c98
* Move Chromoting strings to string_resources.grd and simplify ↵sergeyu@chromium.org2012-11-052-46/+190
| | | | | | | | | | | | | | | | | remoting_resources target. Previously all strings were in messages.json files. Moving them to GRD file will allow to share them with native components. Also simplified how resources are generated: 1. Now <if> is used to handle branded strings instead of generating grd file in build time 2. Removed resource_ids - ids are now specified in grd files. BUG=158995 Review URL: https://codereview.chromium.org/11275101 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166003 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 165041 (caused http://crbug.com/158995, which is apparently somewhatthakis@chromium.org2012-11-052-200/+4
| | | | | | | | | | | | | | | | | | tricky to fix -- this can reland with the fix) - Move Chromoting strings to string_resources.grd. Previously all strings were in messages.json files. Moving them to GRD file will allow to share them with native components. Also added script that I used to convert translations - to make it easier to review this CL and just in case we need it again in the future. Review URL: https://chromiumcodereview.appspot.com/11150008 TBR=sergeyu@chromium.org Review URL: https://codereview.chromium.org/11312087 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@165953 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 165605 - Fix branding in chromoting string resources.hbono@chromium.org2012-11-021-0/+52
| | | | | | | | | | | | | | | | | When chromoting resources were converted from messages.json to .grd format incorrect branding was used. Beside that simplified how resources are generated: 1. Now <if> is used to handle branded strings instead of generating grd file in build time 2. Removed resource_ids - ids are now specified in grd files. BUG=158995 Review URL: https://chromiumcodereview.appspot.com/11275101 TBR=sergeyu@chromium.org Review URL: https://codereview.chromium.org/11359035 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@165611 0039d316-1c4b-4281-b951-d872f2087c98
* Fix branding in chromoting string resources.sergeyu@chromium.org2012-11-021-52/+0
| | | | | | | | | | | | | | When chromoting resources were converted from messages.json to .grd format incorrect branding was used. Beside that simplified how resources are generated: 1. Now <if> is used to handle branded strings instead of generating grd file in build time 2. Removed resource_ids - ids are now specified in grd files. BUG=158995 Review URL: https://chromiumcodereview.appspot.com/11275101 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@165605 0039d316-1c4b-4281-b951-d872f2087c98
* Add executable bit to remoting/tools/win/chromoting-set-channel.bat to pass ↵tzik@chromium.org2012-11-021-0/+0
| | | | | | | | | | | permission check on buildbot. BUG=None TBR=garykac@chromium.org Review URL: https://codereview.chromium.org/11275118 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@165590 0039d316-1c4b-4281-b951-d872f2087c98
* [Chromoting] Script to switch release channels on Windows.garykac@chromium.org2012-11-011-0/+49
| | | | | | Review URL: https://chromiumcodereview.appspot.com/11145028 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@165530 0039d316-1c4b-4281-b951-d872f2087c98
* Fix AudioCapturer implementation to read from audio pipe even when there are ↵sergeyu@chromium.org2012-11-011-1/+1
| | | | | | | | | | | | | | | | no active clients. Pulseaudio blocks playback when the host stops reading from the audio pipe. Previously the host was reading from the pipe only when there is an active client. Fixed the capturer to always read from the pipe, so that we don't halt playback when user disconnects. Also changed sampling rate to 48000 to avoid resampling in the host. BUG=153090 Review URL: https://codereview.chromium.org/11316010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@165275 0039d316-1c4b-4281-b951-d872f2087c98
* Move Chromoting strings to string_resources.grd.sergeyu@chromium.org2012-10-302-4/+200
| | | | | | | | | | | | Previously all strings were in messages.json files. Moving them to GRD file will allow to share them with native components. Also added script that I used to convert translations - to make it easier to review this CL and just in case we need it again in the future. Review URL: https://chromiumcodereview.appspot.com/11150008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@165041 0039d316-1c4b-4281-b951-d872f2087c98
* [Chromoting] Add a username policy, and implement it for the Linux Me2Me host.simonmorris@chromium.org2012-10-301-5/+9
| | | | | | | | | BUG=158080 Review URL: https://chromiumcodereview.appspot.com/11341032 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@165036 0039d316-1c4b-4281-b951-d872f2087c98
* Gracefully handle starting the Chromoting service whilst already running.lambroslambrou@chromium.org2012-10-201-4/+4
| | | | | | | | | | | | This is to comply with Debian policy: http://www.debian.org/doc/debian-policy/ch-opersys.html#s-sysvinit and avoid an ugly "fail" message if the Debian package is upgraded from the command-line. Review URL: https://chromiumcodereview.appspot.com/11191071 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@163121 0039d316-1c4b-4281-b951-d872f2087c98
* Fix is-remoting-session scriptsergeyu@chromium.org2012-10-191-1/+1
| | | | | | | | | | | Previously is-remoting-session script didn't work correctly, which causes host to be restarted when it's updated. Problem was that it was checking wrong environment variable. Review URL: https://chromiumcodereview.appspot.com/11191070 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@162925 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-14 19:14:15 +0000