Add gdata content search to file_manager

chrome/browser/resources/file_manager/js/file_transfer_controller.js

Index: chrome/browser/resources/file_manager/js/file_transfer_controller.js
diff --git a/chrome/browser/resources/file_manager/js/file_transfer_controller.js b/chrome/browser/resources/file_manager/js/file_transfer_controller.js
index 0848fee7d019ca2384dac15df80bdc22660ae2c6..e0e739a7e9b388e5b05285492d00e3840a0acb35 100644
--- a/chrome/browser/resources/file_manager/js/file_transfer_controller.js
+++ b/chrome/browser/resources/file_manager/js/file_transfer_controller.js
@@ -400,6 +400,8 @@ FileTransferController.prototype = {
     if (this.directoryModel_.isPathReadOnly(destinationPath)) {
       return false;
     }
+    if (this.directoryModel_.isSearching())
+      return false;
 
     if (!dataTransfer.types || dataTransfer.types.indexOf('fs/tag') == -1)
       return false;  // Unsupported type of content.
@@ -481,7 +483,7 @@ FileTransferController.prototype = {
   },
 
   get currentDirectory() {
-    return this.directoryModel_.getCurrentDirEntry();
+    return this.directoryModel_.getSearchOrCurrentDirEntry();

[SeRya, 2012/05/15 06:17:01]

currentDirectory doesn't make sense for search results. It's mostly used to
check if files gonna be pasted into the same directory thy have being coped
from. We don't allow paste to search results.

Ideally we should only set sourceDir if all the coped files are from the same
directory. However it would require resolving each entry name before putting it
into the collection.

I suggest to not set sourceDir for search results or set it to empty string.

[tbarzic, 2012/05/16 03:50:04]

setting sourceDir to empty string would break copy operations from search dirs
(we have some checks that expect it to be set), so I'd rather leave this as it
is, and maybe 
make the changes you proposed in a follow up patch (I'd hate to make this patch
more complex unless I really need to)

   },
 
   get readonly() {