// Copyright (c) 2012 The Chromium Authors. All rights reserved. // Use of this source code is governed by a BSD-style license that can be // found in the LICENSE file. // The include directives are put into Javascript-style comments to prevent // parsing errors in non-flattened mode. The flattener still sees them. // Note that this makes the flattener to comment out the first line of the // included file but that's all right since any javascript file should start // with a copyright comment anyway. // If you add a new dependency, you should update build files by rerunning // gyp. Otherwise, you'll be bitten by a dependency issue like: // // 1) You add a new dependency to "whatever.js" // 2) You make changes in "whatever.js" // 3) Rebuild "resources.pak" and open Files.app // 4) You don't see the changes in "whatever.js". Why is that? // // Because the dependencies are computed at gyp time, the existing build // files don't know that "resources.pak" now has a dependency to // "whatever.js". You should rerun gyp to let the build files know. // // //metrics.js initiates load performance tracking // //so we want to parse it as early as possible. // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // (function() { // 'strict mode' is invoked for this scope. // // This script must be loaded before all other Files.app's scripts. // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // For accurate load performance tracking place main.js should be // // the last include to include. // // Global fileManager reference useful for poking at from the console. window.fileManager = fileManager; // Exports window.util = util; window.FileOperationManagerWrapper = FileOperationManagerWrapper; window.unload = unload; })();