Add script files of the separated Gallery.app.

chrome/browser/resources/file_manager/manifest.json

 {
   // chrome-extension://hhaomjibdihmijegdhdafkllkbggdgoj/
   "key": "MIGdMA0GCSqGSIb3DQEBAQUAA4GLADCBhwKBgQDlhpGghtnNJ7pluQN0RDwbUxwwi99oM35ZEaFYvxPLrf0fIEC18cfDdJi6u4aJ+UoSpgzK731L0P/k4LvK2Rz9kVKOy0+IvuRrWkT7lbrLfA1UEBh02OA1AAshjmyRg4IxCqgl8ia8XWq6HKegS1y1KXZYGgb4qp7Bh9VC4cIzswIBIw==",
   "manifest_version": 2,
   "name": "Files",
   "version": "3.0",
   "description": "File Manager",
   "incognito" : "split",
   "icons": {
     "16": "common/images/icon16.png",
@@ skipping 174 matching lines @@
     {
       "id": "open",
       "default_title": "__MSG_OPEN_ACTION__",
       "default_icon": "common/images/file_types/200/generic.png",
       "file_filters": []
     }
   ],
   // Required to import scripts in a web worker. Note, that in Apps v2, it is
   // enough that anything is passed to web_accessible_resources. If there is
   // at least any file, then all files are allowed. http://crbug.com/179127.
-  "web_accessible_resources": ["foreground/js/metadata/byte_reader.js"],
+  "web_accessible_resources": [
+    "background/js/*.js",
+    "common/js/*.js",
+    "foreground/js/metadata/*.js"

[yoshiki, 2014/04/23 07:08:39]

Could you move the follwoing file/directory into common/?
- foreground/js/metadata
- background/js/test_util.js

I think 'common' is better place.

[hirono, 2014/04/23 08:13:15]

Previously 'common' means the assets are shared by foreground and background.
I think ui/file_manager/common is the better place.
WDYT?

[yoshiki, 2014/04/24 03:49:40]

ui/file_manager/common can't be accessible by app. I think
ui/file_manager/file_manager/common/ is enough. Originally this directory has
been for the code used by both, but I think using for shared files among apps is
fine. But as for now, keeping the file place as they are (and considering about
this separately) is also ok.

And could you specify each script name, instead of using asterisk?

[hirono, 2014/04/24 05:11:15]

So let me keep the structure as it is. I'm also think of the structure like:
file_manager/js/foreground. The original reason why we put the foreground just
under the file_manager is we might have sub-components such as video_player
under the foreground directory.
https://codereview.chromium.org/39123003/#msg2

Maybe we can simplify the directory structure.

[yoshiki, 2014/04/24 10:09:19]

sgtm

+  ],
   "app": {
     "background": {
       "scripts": [
         "common/js/error_util.js",
         "chrome://resources/js/load_time_data.js",
         "chrome://resources/js/cr.js",
         "chrome://resources/js/cr/event_target.js",
         "chrome://resources/js/cr/ui/array_data_model.js",
         "common/js/async_util.js",
         "common/js/path_util.js",
         "common/js/progress_center_common.js",
         "common/js/util.js",
         "background/js/device_handler.js",
         "background/js/drive_sync_handler.js",
         "background/js/file_operation_handler.js",
         "background/js/file_operation_manager.js",
         "background/js/progress_center.js",
         "background/js/test_util.js",
         "background/js/volume_manager.js",
         "background/js/background.js"
       ]
     },
     // chrome-extension://pmfjbimdmchhbnneeidfognadeopoehp is the image loader extension.
     "content_security_policy": "default-src 'none'; script-src 'self' chrome://resources chrome-extension://pmfjbimdmchhbnneeidfognadeopoehp; style-src 'self' 'unsafe-inline' chrome://resources; frame-src 'self' about:; img-src 'self' chrome://resources chrome://theme data: https://docs.google.com https://*.googleusercontent.com chrome://extension-icon; media-src 'self' https://*.googleusercontent.com; connect-src https://drive.google.com; object-src 'self'"
   }
 }