> But i think that the Photoshop.com intent is designed with the idea > that another app queries the *content-provider* for images (not the > file-system) If your app is a file browser/manager and the user wants to open a file to edit instead of view means you only have the file in which to work. You have no idea what content provider supplies this particular image since you aren't working with a provider, merely files on the SD card itself. The mechanism Adobe has currently for just content providers is all well and good, but the additional one for file schemes would be nice too. =)
I wonder if a file browser should incorporate a file content provider specifically to handle such tasks. *ponders* On Mar 7, 7:33 pm, Streets Of Boston <[email protected]> wrote: > I agree that it should work on any (local) Uri, file: and content: > > But i think they somehow need to tie it to the MediaStore content- > provider. And this makes sense, because content-providers are the main > mechanism with which data is shared amongst the applications. > > This means, that if you have a file, you need to insert it into the > MediaStore's image content-provider. The insert returns you an ID > (Long value), which you then can use for Photoshop.com. > > But i think that the Photoshop.com intent is designed with the idea > that another app queries the *content-provider* for images (not the > file-system) > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
