gdata: Export PlatformFileInfo/Proto conversion functions

chrome/browser/chromeos/gdata/gdata_files.h

Index: chrome/browser/chromeos/gdata/gdata_files.h
diff --git a/chrome/browser/chromeos/gdata/gdata_files.h b/chrome/browser/chromeos/gdata/gdata_files.h
index 9f581391e401952e19a137fae1a2ad4a055d66a7..d3390aecf631db075f97a4e6164b512bab337c01 100644
--- a/chrome/browser/chromeos/gdata/gdata_files.h
+++ b/chrome/browser/chromeos/gdata/gdata_files.h
@@ -33,6 +33,7 @@ class GDataEntryProto;
 class GDataFileProto;
 class GDataDirectoryProto;
 class GDataRootDirectoryProto;
+class PlatformFileInfoProto;

[achuithb, 2012/04/30 23:51:33]

I'd make this the first declaration in this proto group since that's how it
appears in the proto file.

 
 // Directory content origin.
 enum ContentOrigin {
@@ -136,6 +137,16 @@ class GDataEntry {
   // de-duplication (see AddEntry() for details on de-duplication).
   virtual void SetFileNameFromTitle();
 
+  // Convert the proto representation to the platform file.

[achuithb, 2012/04/30 23:51:33]

Can we keep all the proto methods grouped together? So maybe move this up after
the declaration of FromProtoString? 

Let's also keep the style consistent (one comment for both functions, and no
newline between the declarations).

[satorux1, 2012/05/01 00:13:46]

Done.

+  static void ConvertProtoToPlatformFileInfo(
+      const PlatformFileInfoProto& proto,
+      base::PlatformFileInfo* file_info);
+
+  // Converts the platform file info to the proto representation.
+  static void ConvertPlatformFileInfoToProto(
+      const base::PlatformFileInfo& file_info,
+      PlatformFileInfoProto* proto);
+
  protected:
   // For access to SetParent from AddEntry.
   friend class GDataDirectory;