Thanks, Ya, I figured "application/emx*" would not match anything; but I was grasping at straws. The server side of things is not in my control. I have to deal with the .emx files being downloaded with empty mimetype - or give up the enterprise entirely. :/
Usining "mimetype=applcation/*" is the only thing so far that allows me to download these .emx files in the browser and then open them from the downloads screen. Why does the browsers' download screen not recognize the path based associations like the various file managers do? Is there a "scheme" I am missing for the browser? -Jack On Jun 5, 11:02 pm, Dianne Hackborn <[email protected]> wrote: > We generally don't do matching based on extension, but on MIME type. > Ideally you want your server to reporting a proper MIME type for your file. > > Also, the MIME type matches only handles '*' for type and subtype -- that > is, application/* or */*. Your 'application/emx*' will not match anything. > > > > > > On Sat, Jun 5, 2010 at 6:41 PM, jdeslip <[email protected]> wrote: > > I am writing an app that needs to be able to open (be associated in > > the browser download window for example) with a certain file type. > > The file type has .emx extension and is in an xml format (the top of > > the files have <?xml version='1.0' encoding="UTF-8"?> ). However, I > > can't for the life of me get my app associated with this filetype. I > > have tried the following in my Manifest: > > > <intent-filter> > > <action android:name="android.intent.action.VIEW"/> > > <category > > android:name="android.intent.category.DEFAULT" /> > > <category > > android:name="android.intent.category.BROWSABLE" /> > > <data android:mimeType="application/xml"/> > > <data android:mimeType="application/rss+xml"/> > > <data android:mimeType="application/emx+xml"/> > > <data android:mimeType="application/*xml"/> > > <data android:mimeType="text/xml"/> > > <data android:mimeType="application/emx"/> > > <data android:mimeType="application/emx*"/> > > <data android:mimeType="application/xml*"/> > > </intent-filter> > > > with no luck. I can get the filetype associated properly with my app > > if I do the following: > > > <intent-filter> > > <action android:name="android.intent.action.VIEW"/> > > <category > > android:name="android.intent.category.DEFAULT" /> > > <category > > android:name="android.intent.category.BROWSABLE" /> > > <data android:mimeType="application/*"/> > > </intent-filter> > > > but this also associates my app with every file format (which I > > obviously don't want though I see that snesnoid does this for > > example). Does anyone know how I can associate my app with this .emx > > file format alone? > > > -- > > 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]<android-developers%2Bunsubs > > [email protected]> > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en > > -- > Dianne Hackborn > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. -- 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
