So you suggest that I'll have a pre-define resource which will hold all the information I need (let's say it is an XML resource) for creating the external keyboard. This sounds OK. The only problem is how to query for packages which have this resource? I can still create an Activity which have another pre-defined activity- filter which I can query for. Is this a reasonable method? Or is there a clearer way (I mean, I create an activity just for query usages)?
Thanks, Menny On Feb 14, 12:44 am, Mark Murphy <mmur...@commonsware.com> wrote: > Menny wrote: > > I don't know what the other ContentProviders URI are. > > They can be anything, I want to release my keyboard service, and then > > release layouts as I need. > > This means that, somehow, the keyboard service needs to "know" which > > layout packages are installed on the device, and what are the URI of > > their content-providers. > > Another alternative is to still use Context.createPackageContext(), but > primarily as a bootstrap. The APK would publish its content URI in a > pre-determined resource (e.g., R.string.any_soft_keyboard_provider_uri), > which you would then use. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > Android Development Wiki:http://wiki.andmob.org -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
