Implement media path filter

chrome/browser/intents/device_attached_intent_source.cc

Index: chrome/browser/intents/device_attached_intent_source.cc
diff --git a/chrome/browser/intents/device_attached_intent_source.cc b/chrome/browser/intents/device_attached_intent_source.cc
index d0259c2702934d81bf592d07d20bc47783f44ced..eb853a263edbb49dee5f6e4c520827777b2c184d 100644
--- a/chrome/browser/intents/device_attached_intent_source.cc
+++ b/chrome/browser/intents/device_attached_intent_source.cc
@@ -54,7 +54,7 @@ void DeviceAttachedIntentSource::OnMediaDeviceAttached(
   // TODO(kinuko, kmadhusu): Use a different file system type for MTP.
   const std::string filesystem_id =
       fileapi::IsolatedContext::GetInstance()->RegisterFileSystemForPath(
-          fileapi::kFileSystemTypeIsolated, device_path, &device_name);
+          fileapi::kFileSystemTypeLocalMedia, device_path, &device_name);

[kmadhusu, 2012/07/26 20:26:43]

This is a file system for attached device media. Can we call this as
kFileSystemTypeDeviceMedia?

[tzik, 2012/07/27 01:00:23]

Hmm. We might have two type of media device.
One is mounted device to which we can access like local filesystem (this case).
Another is the device that we need to use MTP or PTP.

How about using kFileSystemTypeMountedMedia?

[kmadhusu, 2012/07/27 01:22:42]

I thought kFileSystemTypeLocalMedia corresponds to local media galleries such as
"C:\MyPictures\" etc.  I guess you are considering mass storage devices (such as
usb, external hard drive) and local media galleries("C:\MyPictures\") as
"kFileSystemTypeLocalMedia" and mtp/ptp device galleries as
"kFileSystemTypeDeviceMedia". Is it correct? If so, we need a better name for
file system types.

[tzik, 2012/07/27 18:33:22]

Yes, I mean that exactly. As we chatted, s/LocalMedia/NativeMedia/ looks good.

 
   CHECK(!filesystem_id.empty());
   webkit_glue::WebIntentData intent(