Menny wrote: > 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'm not sure if there is an efficient query-for-resource mechanism. > I can still create an Activity which have another pre-defined activity- > filter which I can query for. It doesn't necessarily have to be a filter on an activity, but, yes, that should be a time-efficient lookup method. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android Training in US: 8-12 February 2010: http://bignerdranch.com -- 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
