[App Shell] Add dev tools for debugging

apps/shell/app/shell_main_delegate.cc

 // Copyright 2013 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.
 
 #include "apps/shell/app/shell_main_delegate.h"
 
 #include "apps/shell/browser/shell_content_browser_client.h"
 #include "apps/shell/common/shell_content_client.h"
 #include "apps/shell/renderer/shell_content_renderer_client.h"
 #include "base/command_line.h"
@@ skipping 77 matching lines @@
          process_type == switches::kUtilityProcess;
 }
 
 void ShellMainDelegate::InitializeResourceBundle() {
   ui::ResourceBundle::InitSharedInstanceWithLocale("en-US", NULL);
 
   // The extensions system needs manifest data from the Chrome PAK file.
   // TODO(jamescook): app_shell needs its own manifest data file.
   base::FilePath resources_pack_path;
   PathService::Get(chrome::FILE_RESOURCES_PACK, &resources_pack_path);
+  base::FilePath pak_file, pak_dir;
+  PathService::Get(base::DIR_MODULE, &pak_dir);
+  pak_file = pak_dir.Append(FILE_PATH_LITERAL("content_shell.pak"));

[James Cook, 2014/02/10 20:31:23]

Why do we need content_shell's PAK file?  Isn't Chrome's sufficient?

If we need both pak files please comment in the source why we need both.

nit: I would put these lines below the AddDataPackFromPath line below.

[Haojian Wu, 2014/02/11 03:24:36]

Done.

Yes, we need content_shell.pak here.
We use content's DevTools rather than chrome's, so we need
shell_devtools_discovery_page.html in content.pak instead of
devtools_discovery_page.html in chrome resource pak file.

   ResourceBundle::GetSharedInstance().AddDataPackFromPath(
       resources_pack_path, ui::SCALE_FACTOR_NONE);
+  ResourceBundle::GetSharedInstance().AddDataPackFromPath(
+      pak_file, ui::SCALE_FACTOR_NONE);
 }
 
 }  // namespace apps