Implement ManifestParser in content/.

content/public/common/manifest.h

+// Copyright 2014 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.
+
+#ifndef CONTENT_PUBLIC_COMMON_MANIFEST_H_
+#define CONTENT_PUBLIC_COMMON_MANIFEST_H_
+
+#include "base/strings/nullable_string16.h"
+#include "content/common/content_export.h"
+
+namespace content {
+
+// The Manifest structure is an internal representation of the Manifest file
+// described in the "Manifest for Web Application" document:
+// http://w3c.github.io/manifest/
+struct CONTENT_EXPORT Manifest {
+  Manifest();

[jochen (gone - plz use gerrit), 2014/09/12 11:55:18]

ctor should take paramters for name and short_name 

[mlamouri (slow - plz ping), 2014/09/12 12:05:19]

Why? Those members might or might not be present in the manifest. Requesting
them to be passed to the ctor would be quite a burden for the callers.
Especially when the Manifest structure will contain more fields like start_url,
icons, display, etc.

[jochen (gone - plz use gerrit), 2014/09/12 12:09:40]

currently, the parser always sets both fields, and that's how we do structs
anyways

[mlamouri (slow - plz ping), 2014/09/12 12:16:47]

What do you mean by "that's how we do structs"? Most of the struct in
content/public/common/ I found did not have ctors to initialize all members.

+  ~Manifest();
+
+  // Returns whether this Manifest had no attribute set. A newly created
+  // Manifest is always empty.
+  bool IsEmpty() const;
+
+  // Null if the parsing failed or the field was not present.
+  base::NullableString16 name;
+
+  // Null if the parsing failed or the field was not present.
+  base::NullableString16 short_name;
+};
+
+} // namespace content
+
+#endif // CONTENT_PUBLIC_COMMON_MANIFEST_H_